InfuseSync duplicates alternate Jellyfin movie versions in “Other”

General
1

Hi,

I’m seeing an issue with alternate movie versions when using Infuse Library Mode with InfuseSync.

Setup

  • Jellyfin: 10.11.11
  • InfuseSync: 1.5.2
  • Infuse: 8.4.8
  • Device: iPhone 17 Pro
  • Operating system: iOS 26.5.2
  • Jellyfin library type: Movies
  • Connection mode: Library Mode

Problem

I start with an existing 2160p movie and then generate or add a 1080p version in the same movie directory.

After refreshing the Jellyfin library, Jellyfin correctly groups the two files as versions of the same movie.

Following an incremental sync with InfuseSync enabled, Infuse partially handles this correctly: the main movie displays Select Version, and both versions are available. However, the newly added 1080p version also appears as a separate standalone item under Other.

The secondary version is therefore represented twice:

  1. Correctly as a selectable version of the main movie.
  2. Incorrectly as a standalone item under Other.

Control test

I uninstalled InfuseSync and allowed Infuse Library Mode to perform its normal Jellyfin scan.

The same files were then detected correctly as versions of one movie, without the duplicate Other entry.

This suggests that the Jellyfin grouping and filenames are valid and that the problem is specific to InfuseSync’s incremental update path.

Diagnostics

I submitted an Infuse diagnostic report with the reference:

A1SA6

GitHub issue

I have also opened a technical report in the InfuseSync repository, including full reproduction steps and a possible cause:

InfuseSync issue #35

The current hypothesis is that Jellyfin reports the changed alternate video separately using PrimaryVersionId. InfuseSync may return both the refreshed primary movie and the alternate-version item during the incremental update, causing Infuse to index the alternate under Other.

For now, I have left InfuseSync uninstalled because normal Library Mode scanning works correctly.

Could the Firecore team confirm whether this can be reproduced and whether the fix belongs in InfuseSync or in Infuse’s handling of the incremental response?

I would also be happy to test a modified plugin build if helpful.

Thanks.