A simple search for “unmatched” in this forum will show many closed-after-90-days topics with no resolution. This has been going on for years now.
I have two primary use cases that depend on this working as I expect:
Unmatched = true should give a strict inverse of the results for Unmatched = false. Currently, it gives the same results. How can a movie be both matched and unmatched?
A filter for unmatched = true should include movies that Plex mistakenly matched to something and then was told by me, “No, you’re wrong.” Based on the output of ExportTools, I believe this is because the “MetaDB” link isn’t cleared when you tell Plex to “unmatch” the movie.
While I’m wishing, I’d also like to see the filter logic to be inverted. The filter should be called “Matched”, with unmatched movies found by “Matched = false” to avoid a confusing double-negative.
This has been annoyance to me also. Like you my posts reporting this got ignored and threads auto closed but let’s hope as a ninja has commented it might finally get some attention.
Wouldn’t a new filter called AutoMatched make more sense? Once successfully corrected, the movie is indeed matched. Or do you mean the case when one unmatches a movie and it remains unmatched?
Plex has an over-reliance on Internet databases. Not all movies can be successfully matched against them. When I tell Plex it’s wrong, it might be a prelude to a manual match, but in my library, a “no, you’re wrong, Plex” judgement is almost always the end of the matter.
One of the reasons I want this feature to work sensibly is to check for mismatched movies. Currently I must run ExportTools on the library and then play spreadsheet/SQL games on the resulting data set to seek out mismatches. It would be a lot easier to just get a list of movies Plex thinks are correctly matched and scan for cover art that cannot possibly be a correct match.
