The latest update to the new metadata agent worked initially and is still working fine on one of my servers but for whatever reason, it has unmatched a large portion of my library. And my only option is to manually match them. Changing back to legacy or to new agents doesn’t seem to work. Server restart didn’t work either. Everything is as up to date as I can get it, from what I can tell. Attaching logs from the server having issues
Have you upgraded your agents (in each section) to the new Agents and Scanner?
The old python-based ones, deprecated for a few years, have now been removed.
Migrate an Existing TV Library
Upgrading a library is super easy: just select the ellipsis menu icon for your library in the sidebar of the web app and select Manage Library > Upgrade Matching. At this point a scan will be triggered looking for new items but your existing shows will not be changed until you:
@ChuckPa
I believe they’re all using “Plex Movie” now. It prompted me to update and refresh all metadata, which I did. But I don’t see the “Upgrade Matching” option though.
It might have also been removed this update as well.
IIRC, in order to upgrade the matching, the python agent was needed for the hand-off.
Since it’s fully gone, you’ve tried Refresh All Metadata to no avail?
@ChuckPa
Yea I have. Refreshing all metadata, re-scanning, changing back to legacy, repeating the processing, then upgrading again and repeating the processes once more. It still didn’t want to auto match what it un-matched previously. And what was more interesting, when I sorted by “Unmatched” it didn’t show any results. I just had to go through and manually match all the ones that it un-matched.
@ChuckPa
Ah, no unfortunately I didn’t. If I see another movie unmatched, I’ll try that and see if it grabs it.
For the scan settings, I disabled those a LONG time ago because during transcodes it would pick up every movie as Madagascar for some reason. It’s probably fixed now but I have it set for every 2 hours, that way the media has time to finish transcoding before it scans so it’s not playing a partial file.
If you have your transcode directory in a place where PMS has active auto-detect – then YES, it will pick up the transcoding activity. Transcoder temp and where the media is located must be separate.
My server has a lot of memory so I use the ramdisk (/dev/shm)
Media is in /vol/media (RAID volume)
I have partial and auto enabled.
I never have false detections from media being played.
I would first check where you have things pointing to.
I suspect there’s unintended overlap
@ChuckPa
Using Handbrake, I’m assuming the temp file location is the same as the destination directory if I never changed it? Pretty basic setup with ZFS “/plex/movies” and I just transcode straight to the destination. Only time I had false detections was a while ago, like I mentioned, or if movies/shows have too similar of names.
Otherwise I’m still not sure why the media it had matched previously just decided to unmatch after the Agent Update.
This version of PMS (1.41.x completes it) finalizes the removal of Python agent code anywhere in PMS. It’s been phasing out for some time but was kept to give opportunity to transition. Now that is gone.
If you had media previous matched by the old agents (“Legacy”) then they would become unmatched.
The old python agent and scanner were more tolerant of bad naming.
The new agent (C++) is good but not as tolerant.
Can you show me how you have one or two of these non-matching named?
I use FileBot, with perfect naming format, and never miss any
@ChuckPa
This specific server did give me trouble when I set it up by automatically loading Local assets first, instead of preferring downloaded metadata when it did use the Legacy agent. So something must have caused an issue there during my troubleshooting. I did notice that it seemed to the prefer the “Title” metadata over the actual filename when it was ‘unmatched’.
I did go ahead and attach screenshots of my folder structure and naming schemes. I WISH I found FileBot sooner…I probably would have saved hours or days worth of renaming things manually. But yes, I use that now and it’s a magical program.
@ChuckPa
Right, the way I meant to say that was “When I set up the server initially, it had the option checked to ‘Prefer local metadata’ so I had a hard time getting that fixed after unchecking that option”. I always had Local Media Assets at the bottom of the list. But seeing as that’s now the legacy agent, it shouldn’t be an issue anymore I hope.