If you add a new music library and set it to use Plex Music Scanner, it sets the language field to null. All items that are then scanned are given a null language and in Plex Media Server.log we find “Error response for update: 4 (Agent does not handle the given language).”. If you then go back into the library you can see language is unset, so you can then set it to none, however all items already scanned are now in the db with a language of null so can NEVER be re-scanned properly.
The only workaround when you add a new basic music library is to add it with a fake path, so it wont scan, then edit it and set the correct path and set the language to none, then on saving it should rescan and work. I verified this with a small test library.
Note: On initial creation of a new music library, if you set Scanner = Plex Music Scanner on Advanced tab, then return to the General tab, before saving it reverts to Scanner = Plex Music. I reported other issues around changing scanners on a music library when the new Plex Music library was added a few months ago. Needs some serious testing, as it;s easy to end up with a broken music library.
Well I’ve been going round and round with this for a month. I’m to the point where I just can’t use PLEX for audio at all. I’ll look into your work arounds.
This is indeed annoying, as the new “Plex Music” scanner is broken for compilations metadata and AcousticID analysis can’t be turned off (adding my music now takes days).
Reverting to the old “Plex Music Scanner” is the only remedy, even though for some reason that scanner doesn’t do embedded album art anymore.
But if that isn’t even possible because it defaults back (reintroducing the erroneous compilation metadata in the db) we’re screwed.
I’m temporarily not using music for now until either of the scanners are working correctly again.
