2024-05-18, 04:01 PM
Hello everybody,
first of all I want to say that I’m unsure if the following is bug or a miss configuration/interpretation on my site.
OS: Ubuntu 22.04 LTS
Jellyfin Version: 10.9.2
Installation method: nativ (installation over Jellyfin apt repo)
Used documentation: https://jellyfin.org/docs/general/server...of-a-movie
I recently update Jellyfin (server and web) from 10.8.13 to 10.9.2.
The update run mostly smoothly (thanks to all the hard work of the Jellyfin contributors) but now the order of different versions of the same movie is different than in 10.8.13.
Let me explain further:
I’m using the function for different versions of the same movie in the first place for different quality’s.
For example the same movie in 1080p and in 2160p.
The naming scheme I am using is the following: [Movie Name] - UHD (2160p) and [Movie Name] - FHD (1080p)
For example:
Back in 10.8.13 (and to my understanding of the mention documentation) the versions were order as followed:
First: FHD (1080p)
Second: UHD (2160p)
I’m aspecting this behaviour because in the documentation stands, that the order is alphabetical and only after resolution if the name ends with “p” or “i” and my naming scheme ands with “)”.
But now with version 10.9.2 the order is switched and is beginning with „UHD (2160p)“.
I also tested it with the names „UHD 2160“ and „UHD“ but without differences.
Because of this order change the default version is no longer the 1080p variant.
Unfortunately, this means that if such films are to be played back externally, the small 1080p version is not used by default, but the 2160p version.
However, as Jellyfin has set a bandwidth limit of 10Mbit for external access, this version must now always be downsampled to 1080p first, which means (unnecessary) computing effort.
Have any of you observed similar behaviour or can you tell me whether I have set something wrong or misunderstood something?
It seems to me that the new version now always sorts by resolution first.
I have just found the following commit, which seems to be related to this.
In principle, it reverses this merge request.
However, this merge request also contains documentation changes, which may no longer be valid?
I am also unsure whether the "server ordering of media sources" can then be configured on the server side?
Many thanks and best regards
Xameon
first of all I want to say that I’m unsure if the following is bug or a miss configuration/interpretation on my site.
OS: Ubuntu 22.04 LTS
Jellyfin Version: 10.9.2
Installation method: nativ (installation over Jellyfin apt repo)
Used documentation: https://jellyfin.org/docs/general/server...of-a-movie
I recently update Jellyfin (server and web) from 10.8.13 to 10.9.2.
The update run mostly smoothly (thanks to all the hard work of the Jellyfin contributors) but now the order of different versions of the same movie is different than in 10.8.13.
Let me explain further:
I’m using the function for different versions of the same movie in the first place for different quality’s.
For example the same movie in 1080p and in 2160p.
The naming scheme I am using is the following: [Movie Name] - UHD (2160p) and [Movie Name] - FHD (1080p)
For example:
Code:
'Ex Machina (2015) - FHD (1080p).mkv'
'Ex Machina (2015) - UHD (2160p).mkv'Back in 10.8.13 (and to my understanding of the mention documentation) the versions were order as followed:
First: FHD (1080p)
Second: UHD (2160p)
I’m aspecting this behaviour because in the documentation stands, that the order is alphabetical and only after resolution if the name ends with “p” or “i” and my naming scheme ands with “)”.
But now with version 10.9.2 the order is switched and is beginning with „UHD (2160p)“.
I also tested it with the names „UHD 2160“ and „UHD“ but without differences.
Because of this order change the default version is no longer the 1080p variant.
Unfortunately, this means that if such films are to be played back externally, the small 1080p version is not used by default, but the 2160p version.
However, as Jellyfin has set a bandwidth limit of 10Mbit for external access, this version must now always be downsampled to 1080p first, which means (unnecessary) computing effort.
Have any of you observed similar behaviour or can you tell me whether I have set something wrong or misunderstood something?
It seems to me that the new version now always sorts by resolution first.
I have just found the following commit, which seems to be related to this.
In principle, it reverses this merge request.
However, this merge request also contains documentation changes, which may no longer be valid?
I am also unsure whether the "server ordering of media sources" can then be configured on the server side?
Many thanks and best regards
Xameon