Any chance it’s been mismatched as a duplicate of another movie?
You can filter for duplicates in Plex web in the library view. It’s been years since I had to do look for a mis-match that way, but I think you split the title that shows a duplicate that shouldn’t be, and then use Fix Match to correct the wrong one.
I had that movie in a library that used TMDB, it was matched properly even though the file was named simply 9.mp4 It was inside a folder properly named with the year 9 (2009), though
Coincidently, I re-ripped and added the same movie to a new library this week using the new and improved Movie scanner, with a folder and file name of 9 (2009) and it matched correctly right away.
Using a file/folder name like 9 (2009) {imdb-tt0472033} is supposed to work with the newer movie scanner and agent, but doesn’t necessarily work with the older, legacy agents. In fact, it might add extra confusion when they look for a match.
We don’t know what scanner and agent is being used (I’m sure it’s in the logs, but I can’t read them) I’m no expert, but it sounds more like the movie has been mis-matched, or matched as a duplicate to me.
The movie is not listed under “Duplicates” or “UnMatched” which is what intrigues me. I’ve gone over various permutations of naming conventions as per PLEX documentation, checked the file permissions, cleared metadata.
The movie in itself is not important. I’m trying to understand the underlying mechanism’s at play when the server processes the video files. Why this particular file is being overlooked is proving to be frustrating, but at the same time extremely interesting.
I tested the text file rename approach once, as a suggested way to skip recording an episode in a TV series (e.g. make Plex think you have an episode you don’t.) In my testing Plex won’t pick up the file if it is zero bytes, but if you put anything at all in the text file Plex would find and list it.
