Description
I use Infuse's Library Mode with a Jellyfin server and InfuseSync enabled.
When a generated 1080p version is added to an existing 2160p Jellyfin movie,
InfuseSync's incremental sync adds the new file to Infuse's “Other” category.
The version relationship is also partially recognised: when I navigate to the
main movie entry, “Select Version” appears and both versions are available.
However, the 1080p version remains duplicated as a standalone “Other” item in
the Library Mode index.
When InfuseSync is disabled and Library Mode performs its normal Jellyfin scan,
the same files are detected correctly without the duplicate “Other” entry.
Environment
- Jellyfin: 10.11.11
- InfuseSync: 1.5.2
- Infuse: 8.4.8
- Infuse connection mode: Library Mode
- Device: iPhone 17 Pro
- Operating system: iOS 26.5.2
- Jellyfin library type: Movies
- Firecore diagnostic code:
A1SA6
This issue and diagnostic code have also been submitted to the main Infuse
support team by email.
Reproduction steps
- Start with an existing 2160p movie in Jellyfin.
- Confirm that Jellyfin identifies it correctly as a movie.
- Generate or copy a 1080p version into the same movie directory.
- Run a Jellyfin library refresh.
- Confirm that Jellyfin groups the 2160p and 1080p files as versions of the
same movie.
- Allow Infuse to perform an incremental Library Mode sync with InfuseSync
enabled.
- Open the Infuse library.
- Navigate to the main movie entry and confirm that “Select Version” is
available.
- Check the “Other” category in Infuse.
Actual result
The main movie has a working “Select Version” option, but the newly generated
1080p version also appears as a separate item under “Other”.
This results in the secondary version being represented twice:
- Correctly as a selectable version of the main movie.
- Incorrectly as standalone “Other” media.
Expected result
The existing movie should be updated to contain both the 2160p and 1080p media
sources. The generated 1080p file should not also appear as a standalone item
under “Other”.
Control test
- Disable InfuseSync.
- Refresh/rescan the Jellyfin connection in Infuse Library Mode.
- Infuse detects the same files correctly as versions of one movie, without
creating the additional “Other” entry.
This suggests the Jellyfin library structure and filenames are valid, and that
the duplicate “Other” entry is specific to the InfuseSync incremental update
path.
Example layout
Replace this section with an actual affected movie if required:
Movies/
└── Example Movie (2025)/
├── Example Movie (2025) - 2160p.mkv
└── Example Movie (2025) - 1080p.mkv
Jellyfin displays these as a single movie with two media sources.
Possible cause
This is a hypothesis based on the observed behaviour.
Jellyfin represents an alternate video version using Video.PrimaryVersionId.
InfuseSync may be returning both:
- The primary movie update containing the grouped media sources.
- The changed alternate-version item as a separate standalone video.
That would explain why “Select Version” works while the alternate also appears
under “Other”.
Potential areas to inspect:
LibrarySyncManager.ItemUpdated
InfuseSyncService.GetUserItems
- Handling of
Video.PrimaryVersionId
- Deduplication or canonicalisation of primary and alternate-version updates
An alternate video with PrimaryVersionId may need to be resolved to its
primary movie before the incremental update is stored or returned. The
standalone alternate DTO should not be returned separately when its primary
movie already contains it as a media source.
Diagnostics
Firecore diagnostic code: A1SA6
The diagnostic was generated around the time the issue was reproduced and has
already been provided to the main Infuse support team by email.
Description
I use Infuse's Library Mode with a Jellyfin server and InfuseSync enabled.
When a generated 1080p version is added to an existing 2160p Jellyfin movie,
InfuseSync's incremental sync adds the new file to Infuse's “Other” category.
The version relationship is also partially recognised: when I navigate to the
main movie entry, “Select Version” appears and both versions are available.
However, the 1080p version remains duplicated as a standalone “Other” item in
the Library Mode index.
When InfuseSync is disabled and Library Mode performs its normal Jellyfin scan,
the same files are detected correctly without the duplicate “Other” entry.
Environment
A1SA6This issue and diagnostic code have also been submitted to the main Infuse
support team by email.
Reproduction steps
same movie.
enabled.
available.
Actual result
The main movie has a working “Select Version” option, but the newly generated
1080p version also appears as a separate item under “Other”.
This results in the secondary version being represented twice:
Expected result
The existing movie should be updated to contain both the 2160p and 1080p media
sources. The generated 1080p file should not also appear as a standalone item
under “Other”.
Control test
creating the additional “Other” entry.
This suggests the Jellyfin library structure and filenames are valid, and that
the duplicate “Other” entry is specific to the InfuseSync incremental update
path.
Example layout
Replace this section with an actual affected movie if required:
Movies/
└── Example Movie (2025)/
├── Example Movie (2025) - 2160p.mkv
└── Example Movie (2025) - 1080p.mkv
Jellyfin displays these as a single movie with two media sources.
Possible cause
This is a hypothesis based on the observed behaviour.
Jellyfin represents an alternate video version using
Video.PrimaryVersionId.InfuseSync may be returning both:
That would explain why “Select Version” works while the alternate also appears
under “Other”.
Potential areas to inspect:
LibrarySyncManager.ItemUpdatedInfuseSyncService.GetUserItemsVideo.PrimaryVersionIdAn alternate video with
PrimaryVersionIdmay need to be resolved to itsprimary movie before the incremental update is stored or returned. The
standalone alternate DTO should not be returned separately when its primary
movie already contains it as a media source.
Diagnostics
Firecore diagnostic code:
A1SA6The diagnostic was generated around the time the issue was reproduced and has
already been provided to the main Infuse support team by email.