![]() |
Some tracks in music not correctly sorted - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +---- Forum: Media Scanning & Identification (https://forum.jellyfin.org/f-media-scanning-identification) +---- Thread: Some tracks in music not correctly sorted (/t-some-tracks-in-music-not-correctly-sorted) |
Some tracks in music not correctly sorted - alike - 2025-08-24 Hi there all my fellow jellyfin fans and developers! Thanks for bringing this wonderful piece of software to my life! I really love you all, even if its not perfect ![]() Sometimes, escpecially in large box-sets, track list is a mess. When files are like this: 0101-artist-song.flac 0102-artist-song.flac All the way to lets say: 1014-artist-song.flac And the metadata inside each file is tracknumber for each CD. In this filename's case 0101-artist-song.flac it will be #1 While 1014-artist-song.flac the tracknumber will be #14. The logic is that the track is number 14 on disc 10. But jellyfin does this out of it: ![]() Renaming or changing files metadata is out of the questions for a reason I am afraid. I did try to change the type of metadata reader, but the result is the same. For some reason the cover picture haven't shown on this album yet(even if it is shown from the metadata reader or provider), but that is perhaps another issue? Or could be the cover picture comes after a while, that is also something I've seen many times earlier. The cover picture is not the main issue here but the track sorting. But is there a way to make Jellyfin Server understand this logic? Or other logics similar to this but not exactly the same? I can find more examples if needed. RE: Some tracks in music not correctly sorted - alike - 2025-08-24 This seems to be a client issue! I just see on my nvidia shield that the order of tracks was right. And came back and checked that on jellyfin web client and latest feishin, issue is still persistent. What's going on? |