2024-12-16, 09:51 AM
(This post was last modified: 2024-12-16, 10:41 AM by visualblind. Edited 7 times in total.)
š Environment: Jellyfin 10.10.3 on Docker
Ā I apologize for posting yet another question about multiple versions, however I wasn't able to find a hard answer to my question with the search function.
I suspect a change has been made in the 10.9.x version (or the tail end of 10.8.x) which removes any ability of the admin from influencing the default selected version of a multiple version movie.
For example, in the past If I wanted to have the Remastered version selected by default below, I would simply make sure that its name came first alphabetically like this:
š Movies
|--š Star Wars A New Hope (1977)
Ā Ā |-- Star Wars A New Hope (1977) - 2[Original 1080p H264].mp4
Ā Ā `-- Star Wars A New Hope (1977) - 1[Remastered 1080p H264].mp4
In case you didn't notice what I did, I placed the number 1 before the bracketed name of the multiple version movie name, and placed a 2 in the same position of the movie I do not want selected by default.
š Specs:
Star Wars A New Hope (1977) - 1[Remastered 1080p H264].mp4 = 1920x804, 2.4Ā GiB,Ā 2730 kb/s bitrate
Star Wars A New Hope (1977) - 2[Original 1080p H264].mp4 = 1920x1080,Ā 3.5Ā GiB,Ā 4165 kb/s bitrate
The Jellyfin docsĀ Multiple Versions of a MovieĀ states:
Going by their documentation, since these two movies have an identical resolution width (1920), then the secondary factor in the default selected version should beĀ the filename alphabetical order.
And since:
Star Wars A New Hope (1977) - 1[Remastered 1080p H264].mp4
Comes before:
Star Wars A New Hope (1977) - 2[Original 1080p H264].mp4
We should expect the Remastered version to be selected by default
Almost regardless, I believeĀ that most media server users will have a preferenceĀ as to which version is selected as the default and should be able to override any passive default selection that Jellyfin chooses.
š
It would be great if we could either revert to the 10.8.x logic or add a new feature where filenames ending with one of these strings:
filename_default.ext
filename-default.ext
filename.default.ext
can be used as a user enforced default selection.
Ā I apologize for posting yet another question about multiple versions, however I wasn't able to find a hard answer to my question with the search function.
I suspect a change has been made in the 10.9.x version (or the tail end of 10.8.x) which removes any ability of the admin from influencing the default selected version of a multiple version movie.
For example, in the past If I wanted to have the Remastered version selected by default below, I would simply make sure that its name came first alphabetically like this:
š Movies
|--š Star Wars A New Hope (1977)
Ā Ā |-- Star Wars A New Hope (1977) - 2[Original 1080p H264].mp4
Ā Ā `-- Star Wars A New Hope (1977) - 1[Remastered 1080p H264].mp4
In case you didn't notice what I did, I placed the number 1 before the bracketed name of the multiple version movie name, and placed a 2 in the same position of the movie I do not want selected by default.
š Specs:
Star Wars A New Hope (1977) - 1[Remastered 1080p H264].mp4 = 1920x804, 2.4Ā GiB,Ā 2730 kb/s bitrate
Star Wars A New Hope (1977) - 2[Original 1080p H264].mp4 = 1920x1080,Ā 3.5Ā GiB,Ā 4165 kb/s bitrate
The Jellyfin docsĀ Multiple Versions of a MovieĀ states:
Quote:Movie versions are sorted by the width of the resolution in a descending order. The resolution from the media info is used. Multiple items with the same resolution will be sorted alphabetically.
Going by their documentation, since these two movies have an identical resolution width (1920), then the secondary factor in the default selected version should beĀ the filename alphabetical order.
And since:
Star Wars A New Hope (1977) - 1[Remastered 1080p H264].mp4
Comes before:
Star Wars A New Hope (1977) - 2[Original 1080p H264].mp4
We should expect the Remastered version to be selected by default
- Am I misunderstanding something?
- Could this possibly be a bug?
- Or maybe this is by design but just not documented with the detail it needs?Ā
- Could be more reasons I'm unaware of
Almost regardless, I believeĀ that most media server users will have a preferenceĀ as to which version is selected as the default and should be able to override any passive default selection that Jellyfin chooses.
š
It would be great if we could either revert to the 10.8.x logic or add a new feature where filenames ending with one of these strings:
filename_default.ext
filename-default.ext
filename.default.ext
can be used as a user enforced default selection.