In late September 2015, I got a message from a user on the forums who was having trouble with episode number 264. After adding file-based logging, the logs revealed that VideoFiles.CleanNames removes 264 from filenames.
Some research showed that, in August 2014, the Plex maintainers added the string ‘264’ to the list of format strings in VideoFiles. VideoFiles.CleanNames removes format strings and considers 264 a format string (x264, H264). The Plex maintainers say that the official scanner isn’t broken, so they aren’t changing CleanNames.
The official scanner isn’t broken because, even though the regexes suggest it should support 3-digit episode numbers, the “.602.” case noted earlier ensures three-digit numbers never hit the regexes. Scanner developers should note that the official regexes are misleading and that Plex can change the behavior of functions like CleanNames as they see fit. See my post for scanner developers for more detail.
To resolve this issue, I made my own version of VideoFiles.py, named BABS_VFAllow264.py, which is part of this distribution. The BABS log now starts with the BABS version number and the output of a test function call–and BABS will fail if the test function isn’t there. This failure appears in the Plex Media Scanner.log file.
Scanner developers who want to use BABS_VFAllow264.py are welcome to do so. See the details in my post for scanner developers.
Users I recommend backing up a copy of your old BABS.py file before installing this version, just in case something is packaged wrong or has issues on your system. Please let me know if you find any problems.
