2024-11-26, 04:00 PM
(This post was last modified: 2024-11-26, 04:17 PM by Oleg Kosarev. Edited 3 times in total.)
(2024-11-26, 01:53 PM)TheDreadPirate Wrote: Where in the code do you see this? Can you provide a github link?
I can't find the exact link in the sources right now, but it's clearly visible in this commit where the new parameters I mentioned earlier are passed. Here's the link:
Commit on GitHub.
This concerns custom separators and the whitelist of separators. In the context of the question, are we going to study the source code, or just rely on the fact that Jellyfin made changes without mentioning them in the changelogs? As mentioned in their GitHub releases here, all releases list the changes, and if we search for separators or related topics, we can't find any specific mentions...
Also, I’ll repeat that the checkboxes seem to work, and the semicolon separator works as well, but then the question arises — why introduce additional separator parameters if the standard ones can also be used? The list of questions is only growing.
For example, I have a media library of 17,500 songs, and about 17,000 of them use one separator. The remaining 500 had to be changed to a semicolon. So, what should I do if the hard drive on the server crashes? Do I really have to change the separator for all 17,000 songs?
I also noticed that even if an old separator (like \\) is set in the custom separators, which used to work fine, it is ignored. If I change it to a semicolon, everything starts working. This only adds to the confusion with the settings.
Additionally, everything is in the same file, namely jellyfin/MediaBrowser.Providers/MediaInfo/AudioFileProber.cs. On line 450, in the function GetFirstMusicBrainzId, there is a clear check for useCustomTagDelimiters. If it's not empty, that value is used. Otherwise, the default separator for the field is used. You can see this in the code here.
You can continue exploring the code further, but this does not change the fact that the old separators that worked in version 10.9.3 no longer work.
I kindly ask the developers to provide more information on this issue so users can properly configure and use separators without running into additional problems.