Plex Server:
Synology DS1815+
Linux DSM 6.2.2.24922-0
Version#: 1.15.8.1163-005053bb5
Player Versions:
Plex Web for Chrome Windows - 3.100.1
Plex Web for Chrome Windows - 3.95.2
Plex for iOS - 5.15.1
Plex for Samsung - 3.98.1
Plex for Roku - 6.3.9.5772-1dfcf58b1-Plex
I am having the same problem with hundreds of albums…
If the automatic matching agent incorrectly matches an item to the wrong “version” of an album from it’s online search (i.e., a remastered release as opposed to the ORIGINAL studio release), that metadata info it creates the record in Plex with, seems to be permanently attached to that album record even if you attempt to “Fix Match” to a different search result. This is getting increasingly frustrating as the list of albums requiring additional manual tag editing within Plex is getting tedious.
I have tried enabling as well as disabling the Local Metadata options and neither way seems to have any effect.
I remember reading somewhere about a similar issue from several years ago that mentioned a single character in a line of code somewhere that could be reversed from “<” to “>” so that the agent looked at the oldest release date instead of the newest release date. The error meant that if the album was matched incorrectly to an instance that had a release date newer than the correct one, it would never correct itself, because it would keep trying to update it to the newer, incorrect instance.
Does this sound familiar to anyone??? I would have thought an error this significant would have been corrected long ago…??? I will try to find a link to that thread…
Anyone have any suggestions???
