Influencing Default Selection of Multiple Versions of a Movie

[visualblind]

🏠 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:

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

1. Am I misunderstanding something?
   
2. Could this possibly be a bug?
   
3. Or maybe this is by design but just not documented with the detail it needs? 
   
4. 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.

[TheDreadPirate]

I vaguely recall, in another forum post, that having the vertical resolution in the version name triggered some other sort behavior. I'll try to find it, but I recall that not having the vertical resolution should result in the order you're looking for. IMO, since they're both the same resolution class, having the vertical resolution is not necessary?

[theguymadmax]

The documentation has been updated from the following:

1. "Movie versions are presented in an alphabetically sorted list. An exception applies to resolution names, which are sorted in descending order from highest to lowest resolution. A version name qualifies as a resolution name when ending with either a p or an i."  

To this:
2. "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." 

However, a few pull requests (12621 12626) have since been merged which have reverted the behavior to the original sorting method described in #1.

In your example, 1[Remastered 1080p H264] is the default selection. Make sure you scan and replace all metadata for the item.
   

If resolution is not a factor in sorting, simply remove it from the filename.