2024-06-02, 12:07 AM
(This post was last modified: 2024-06-02, 12:27 AM by balieu. Edited 4 times in total.)
This post has made it much clearer to me, how Jellyfin interpret the filename versioning syntax. Thanks.
As a supplement I have noticed, that if the version label section of the movie filename contains a year (a number that can be interpreted as a year), then the auto-grouping fails, and every movie version file is seen as a separate movie. It also triggers the generation of the <main filename equal to the parent folder name>.nfo file, in addition to the movie.nfo file.
This was seen in Jellyfin v10.9.3 (Web Client).
So if you can't get Jellyfin to auto-group movie versions, then this may be the reason.
As a supplement I have noticed, that if the version label section of the movie filename contains a year (a number that can be interpreted as a year), then the auto-grouping fails, and every movie version file is seen as a separate movie. It also triggers the generation of the <main filename equal to the parent folder name>.nfo file, in addition to the movie.nfo file.
This was seen in Jellyfin v10.9.3 (Web Client).
So if you can't get Jellyfin to auto-group movie versions, then this may be the reason.