Why do you think a manual search would work in this case? We still don’t have information from IMDB for TV movies. Keep in mind that the Manual search is not a Google search. If we don’t get the info from IMDB, we can’t match it.
new (and old) scanner, good luck with /data/media/movies/[REC]² (2009)/[REC]² (2009) [Bluray-1080p x264 DTS 5.1].mkv
and any of the [rec] movies
I did not get an uninterrupted scan, but new scanner took about an hour to scan almost 7k movies.
that doesn’t include matching them.
almost all of them have and picked up the local art/nfo (poster.jpg folder.jpg filename.nfo)
not matched yet, but imported as from nfo
Name it without the brackets?
sure I could do that or manually fix/match, but that sort of defeats the purpose of naming it the proper movie name.
is it finally posssible to not get douzens of double and triple genre’s with this new scanner/agent?
really annoying to have multiple languages or spellings for the same genre.
second annoying thing with agents is to have 2 versions of a movie, because one was matched with TVDB, the other one with plex-agent … (why not always have a IMDB as central-ID ?)
third annoying thing with agents is to not have control of what database is default for posters and what database is default for genre’s
thats the most important things missing with scanner/agent system, if you really like to enhance that system
Ohh this is a good example
I’ll see if we can get this fixed quickly.
I do think that the genre’s come with the move metadata and add to the list any that aren’t already in the database.
This is going to be interesting because if they remove the [ ] to ignore data…
there is going to be a lot of renaming …
perhaps just need to check if the [ is at the beginning of the filename or not.
of course, that wouldn’t help movies that have [ ] somewhere else in the title
You should not need to rename your files. We can be smart about parsing these files ![]()
Well, it surprises me that you are in the “TV movie” recording business and cannot match TV movies in such a way.
I don’t have any insights in your legal situation with IMDB, but my movie library contains hundreds of German TV movies (if not thousands) and matching them is a horror.
WHAT YOU CAN DO - since stacking of agents is possible, you could deliver the IMDB number if such a number is provided via manual search, so that other agents can use these to match the movie.
At the moment, you are not doing this with the “old” agent.
What’s funny is, Plex has no problem identifying TV movies if their IMDB ID is contained in an NFO file 
BTW, IMDB has a tendency to change movie names every once in a while. The above [Rec]² example is a good one, because IMDB has since changed the official name to [Rec] 2. They’re also highly inconsistent with their naming in general. I find myself (driven by my OCD, of course
)going back and changing names all the time, just so they match IMDB at that time.
The plans are that when the new agent is official it shouldn’t change your current library when it is updated. If you’re really worried though, you should keep a backup of your DB. Personally, I just use tinyMediaManager with NFO files to manage things so that Plex can’t change things on me.
During the short Plex outage I was blocked from authenticating for this forum or this post would have arrived about 2 hours earlier. It seems that the new scanner did not process any of the movies that I added during the outage. I was able to access the Plex web-page locally at that time using http://127.0.0.1:32400, and even then was not able to “match” the movies with the updated scanner. However, the old library matched automatically during the downtime with the previous scanner. Now that everything is back up and running properly, I was able to manually match each of the new movies.
Currently running the 1.19.5.2889 build
after scanning in my movies into a new test library, it scanned but never seemed to start any actual matching (not sure if that was due to API issues).
I just tried a refresh metadata on the entire test library and I get a bunch of this in the logs…
Jun 02, 2020 19:37:13.529 [0x7f9105fff700] DEBUG - Jobs: Starting child process with pid 3970198
Jun 02, 2020 19:37:13.561 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: Found 1 provider matches for 'Always (1989)'.
Jun 02, 2020 19:37:13.561 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: Found a search result 'Always'
Jun 02, 2020 19:37:13.561 [0x7f90aeffd700] DEBUG - * Score: -1 (Always)
Jun 02, 2020 19:37:13.561 [0x7f90aeffd700] DEBUG - Refreshing metadata for 'Always' (agent: tv.plex.agents.movie)
Jun 02, 2020 19:37:13.561 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: adding id 1148829 to refresh queue (0 items in queue)
Jun 02, 2020 19:37:13.563 [0x7f90aeffd700] DEBUG - Matching 'Always Be My Maybe' (ID 1148830) with agent tv.plex.agents.movie
Jun 02, 2020 19:37:13.566 [0x7f91537fe700] DEBUG - Notification of new metadata for local://1148829 [id=1148829] (success=0) for 1 items.
Jun 02, 2020 19:37:13.568 [0x7f91537fe700] WARN - Error refreshing metadata for local://1148829
Jun 02, 2020 19:37:13.569 [0x7f91537fe700] DEBUG - LongRunningJobManager: scheduling job for item 1148829, 2698 pending.
Jun 02, 2020 19:37:14.116 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: Found 1 provider matches for 'Always Be My Maybe (2019)'.
Jun 02, 2020 19:37:14.116 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: Found a search result 'Always Be My Maybe'
Jun 02, 2020 19:37:14.116 [0x7f90aeffd700] DEBUG - * Score: -1 (Always Be My Maybe)
Jun 02, 2020 19:37:14.116 [0x7f90aeffd700] DEBUG - Refreshing metadata for 'Always Be My Maybe' (agent: tv.plex.agents.movie)
Jun 02, 2020 19:37:14.116 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: adding id 1148830 to refresh queue (0 items in queue)
Jun 02, 2020 19:37:14.117 [0x7f90aeffd700] DEBUG - Matching 'Always Outnumbered' (ID 1148831) with agent tv.plex.agents.movie
Jun 02, 2020 19:37:14.120 [0x7f91537fe700] DEBUG - Notification of new metadata for local://1148830 [id=1148830] (success=0) for 1 items.
Jun 02, 2020 19:37:14.122 [0x7f91537fe700] WARN - Error refreshing metadata for local://1148830
Jun 02, 2020 19:37:14.123 [0x7f91537fe700] DEBUG - LongRunningJobManager: scheduling job for item 1148830, 2699 pending.
Jun 02, 2020 19:37:14.783 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: Found 1 provider matches for 'Always Outnumbered (1998)'.
Jun 02, 2020 19:37:14.783 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: Found a search result 'Always Outnumbered'
Jun 02, 2020 19:37:14.783 [0x7f90aeffd700] DEBUG - * Score: -1 (Always Outnumbered)
Jun 02, 2020 19:37:14.783 [0x7f90aeffd700] DEBUG - Refreshing metadata for 'Always Outnumbered' (agent: tv.plex.agents.movie)
Jun 02, 2020 19:37:14.783 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: adding id 1148831 to refresh queue (0 items in queue)
Jun 02, 2020 19:37:14.784 [0x7f90aeffd700] DEBUG - Matching 'Always Shine' (ID 1148832) with agent tv.plex.agents.movie
Jun 02, 2020 19:37:14.787 [0x7f91537fe700] DEBUG - Notification of new metadata for local://1148831 [id=1148831] (success=0) for 1 items.
Jun 02, 2020 19:37:14.788 [0x7f91537fe700] WARN - Error refreshing metadata for local://1148831
Jun 02, 2020 19:37:14.789 [0x7f91537fe700] DEBUG - LongRunningJobManager: scheduling job for item 1148831, 2700 pending.
Jun 02, 2020 19:37:15.116 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: Found 1 provider matches for 'Always Shine (2016)'.
Jun 02, 2020 19:37:15.116 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: Found a search result 'Always Shine'
Jun 02, 2020 19:37:15.117 [0x7f90aeffd700] DEBUG - * Score: -1 (Always Shine)
Jun 02, 2020 19:37:15.117 [0x7f90aeffd700] DEBUG - Refreshing metadata for 'Always Shine' (agent: tv.plex.agents.movie)
Jun 02, 2020 19:37:15.117 [0x7f90aeffd700] DEBUG - MetadataAgent [tv.plex.agents.movie]: adding id 1148832 to refresh queue (0 items in queue)
Jun 02, 2020 19:37:15.117 [0x7f90aeffd700] DEBUG - Matching 'Always Watching a Marble Hornets Story' (ID 1148833) with agent tv.plex.agents.movie
Jun 02, 2020 19:37:15.121 [0x7f91537fe700] DEBUG - Notification of new metadata for local://1148832 [id=1148832] (success=0) for 1 items.
Jun 02, 2020 19:37:15.123 [0x7f91537fe700] WARN - Error refreshing metadata for local://1148832
The current / old one is being replaced with this one, which is much improved and has more capabilities, along with significant performance improvements
In an ideal world, people would follow the naming conventions we specify in our support documents (which would offer the best chance of success). The new scanner is working to be smarter, and work with a larger variety of file name patterns than the current one does, although we still highly recommend following our naming guidelines.
As we’ve said, it’s working to improve how we match, regardless of file names, but the best possible experience will always be with files that follow the suggested conventions. As for how you want to structure your files, that’s totally up to you. This thread is specifically about feedback on the new agent, so if you have some constructive feedback that’s on topic, we’re more than happy to hear it. 
The new scanner and agent should be better at parsing filenames than the current python-based one. We are working to improve matching, scoring, and other magic so we match to the correct movie. if you have some examples of your filename structure that does not match correctly with the new preview scanner we would love to see them.
If you’ve edited metadata inside Plex (including posters/art) then those fields are “locked” and we won’t overwrite them when we add the ability to upgrade agents.
