![]() Plex cannot decide if you mean 1101 with season 11 episode 01 or season 1101 because someone said this season is now called 1101 (as some shows do by putting the year as the season name). It will use pattern matching and if a pattern matches it will take that. You, as a human being, probably know what is meant by that convention but a machine, unless it uses some AI stuff, probably won't since it operates completely differently than your brain. You can try to explain all sorts of things and naming conventions but that doesn't change that if you have X conventions, Plex needs to be able to detect X of them and that also accurately. It literally gets stated every time someone has an issue with their matching or files not being added to their library.Īnd here I am, using Plex for 10 years now with the sXXeXX naming convention which literally every media server like plex, Jellyfin and Emby expects you to follow and don't have any issues.ĭon't get me wrong here, I am not arguing with you here, if your naming convention worked before then that is fine BUT I have seen multiple iterations of updates that make the naming convention more restrictive and limit all the possibilities on the episode detection that people come up with.Īll I am saying is that following the proper convention as stated by plex will prevent future issues. You won't believe how often I read this "but it worked before" argument. Please go to the relevant subreddits and support forums, for example: Build help and build shares posts go in their respective megathreads No referral / affiliate links, personal voting / campaigning / funding, or selling posts Welcome to /r/Plex, a subreddit dedicated to Plex, the media server/client solution for enjoying your media! Plex Community Discord Rules Latest Regular Threads: No Stupid Q&A: Tool Tuesday: Build Help: Share Your Build: Submit Troubleshooting Post Files not showing up correctly? ![]()
0 Comments
Leave a Reply. |