Plex reads the nfo files for better matching. It seeks for the pattern of a IMDb ID. As your log above shows, it found the IMDb ID tt0092675 in the same folder as the movie file.
If you look up this ID, you get to - ‘Bloodsport (1988)’
So, general rule: if you put a .nfo file into the same folder as the movie,
make sure it contains the correct IMDb ID or none at all.
You can use this mechanism in cases where a movie is hard to match right (happens sometimes when there are several movies of similar title in the same year or when movie titles start with a number).
@OttoKerner duly noted, I currently have rsync running like a crazy dutchhund through my sorted folders to retrieve and eliminate .nfo files for all sorted movies… I will deal with those hard to recognise movies when they present themselves…
One movie in particular that comes to mind is “The Girl with the Dragon Tattoo”… Thanks @OttoKerner and @ChuckPa for following up on this… Appreciate the input
@GoingGaGa said:
FileBot is nice for Windoze yes… Haven’t had the time to do for Ubuntu and to be honest I rather enjoy going through every single movie I have and renaming and sorting it out, makes you pick up a lot of olden goldies…
As for the NFO files, I haven’t completed testing yet with updated NFO but can’t see why Plex would be reading local files if nowhere Local Media has been selected…
NFO files are a historical thing coming from YAMJ and sorting for Mede8er (Still love my Mede8er, just hate the manual work for it), so yes NFO’s are there in about 4000 folders or so… Will just keep an eye out for it if anything gets picked up wrongly again, but I would love to hear from Plex on why it read those files to begin with…
