2025-03-31, 01:23 PM
(2025-03-31, 12:53 AM)TheDreadPirate Wrote: Plex is Plex, and Jellyfin is Jellyfin. A lot of aspects of Jellyfin's scanner are inherited from Emby when we forked. Not many have been brave enough to attempt to fix the scanner.
I've stated how I think you could ensure consistent identification. We also have documentation here.
https://jellyfin.org/docs/general/server/media/movies/
https://jellyfin.org/docs/general/server/media/shows/
If that is too much of an administrative burden, well......I highly doubt the Jellyfin scanner is going to be changed anytime soon. If the devs knew how to improve it they would have done so already. But my cursory glance has determined that the way the devs have described it to me, "a nightmare piece of code", is an apt description.
Excuse me, but I read online that a few years ago it was possible to manually modify the regular expressions (regex) for content identification. Is this information correct or inaccurate?
If it were correct, I wonder why this functionality was removed. Perhaps it could have solved my problem, and I believe it might be useful for many other users as well.
I understand that taking existing code and reworking it is complex. This is probably one of those cases where certain parts would need to be completely rewritten to create a more robust and high-performing system - potentially even superior to the famous Plex.
Unfortunately, Jellyfin is the newcomer to the market, and those who already have a media server with many imported contents might not consider it as an option, ending up choosing Emby or sticking with Plex. Currently, Jellyfin remains the best choice mainly for those starting from scratch. :-(
As far as you know, are they actively working on this? Or is it currently on hold, waiting for other higher-priority tasks to be completed?