Server Version#: 1.18.2.2015
Player Version#: Not relevant (hosted)
Hi,
I’m struggling a bit with the new Music agent. I have lots of local (Danish) and VA albums, which can’t be matched by the new Music agent/scanner. Which means, everytime i add a new album. There are like 107 albums which PMS is trying to match every time. Takes so long to match a single album because of this.
Is there any way to match or exclude these? so a new album/track doesn’t take like +10 mins to add.
I have tried to match these manually per album with Personal, last.fm etc. This doesn’t make any difference at all. This is becoming so annoying (wasn’t a problem before)
I know that I’ve repeated myself a 100 times, and the Ninjas and Devs have probably placed me on the ignore list. For Plex to re-scan the entire library and try to match the “UnMatched” albums each and every time new media is added is ridiculous, even when the new addition is available at MB, tagged with and matched with Picard (the official MusicBrainz tagging software)
The scanning for unmatched albums should occur during the regular maintenance schedule, not every time anything is added or changed within the library. TV and movie libraries do not scan the entire library, only the affected folders, so why is a music library excluded from this normal and expected behaviour?
The albums are matched with the GUID of “local” if not available at MB. They display properly, with all of the correct info for title, track, genre, artist etc from the embedded tags. They are instantly available and playable when they are added. But Plex keeps on scanning the library trying to match the albums that have been there forever.
Adding an album to MusicBrainz can be a lengthy process, particularly for compilation albums. Each track (recording) has to be associated with an existing MB track ID, each track artist has to be associated with an existing MB artist, each release associated with an existing MB release group, etc. Then, you have to wait for the new addition to be available with Plex, (at least a day, at best) not to mention the 7-day waiting period that could happen if MB doesn’t approve the new addition automatically.
And all I wanted to do was have my old compilation CD scanned and added to Plex.
Plex is now using the musicbrainz.org database to match your music.
(Which is then augmented with data from a few other sources. But the main database is musicbrainz.)
If there is a record in there, you get a match in Plex.
Which means, that we are of cause completely limited by MusicBrainz (or Plex’s implementation) .. and they don’t have new albums (or Plex match doesn’t work) and lacking foreign albums. We don’t have a option to pick and choose.
Trying to match in PlexWeb (hosted):
Matched … but Chrome DevConsole shows this, when clicking (probably because of “&” in title)
HTTP Status Code: 400 (Bad request)
<html><head><title>Bad Request</title></head><body><h1>400 Bad Request</h1></body></html>
Which will mean .. that the list of unmatched albums will get bigger and bigger, and there are no way to match / exclude (or as leelynds suggested - exclude these until maintenance schedule). Just perfect …
What do you mean by that? Musicbrainz is only limited by the users who are putting the data in. Plex is using the main database on musicbrainz.org.
In the worst case, newly entered data need 25 hours until they’re available in the Plex proxy server.
Secondly:
If we can’t match an album - PMS will keep trying to match it. If you try with the last-fm agent, it always shows, no match (too fast - like it isn’t working). The way i see it, we have no other options to make any match - we are locked to musicbrainz … or?
Both of your examples were just freshly entered into MB. Very likely they are not available in the Plex proxy yet.
Both album titles are even marked yellow, which AFAIK means this only a kind of “preliminary” record until confirmed by other users.
This is a bug in PlexWeb (or what every engine makes the request) … It makes a request, with an & in a string. This breaks the query string parameters. “Title” must be url encoded (actually every value - artist could also have an “&”).
Okay What I’m referring to is, that an artist or album with a & .. will return an error in PlexWeb (when trying to select an matched artist/album from the results). The reason. A “&” in a querystring (GET) will break the query string parameters (which is the reason for the 400 bad request error). Which means, you can’t match it (save).
The correct match is found, but clicking the title - gives and error in PlexWeb. Which means, you can’t “match” it (clicking the title in the result window)
and still, none of the responses by @OttoKerner , address the basic problem of unnecessary repetitive scanning, and places the blame on the user.
I have a small library of only about 2000 albums. About 350 are unmatched according to Plex. That’s down from the 400+ that were there a few weeks ago, because I’ve been adding those unmatched albums to the MB database. I make sure that any new additions do have an entry at MB, and if they don’t, I make the addition to their database, and wait till it’s been officially approved, before I add it to Plex.
Ignoring the fact that adding a perfectly match-able album to Plex sets off a relentless and useless attempt to match those 350 un-matched albums is at best, a huge oversight by Plex.
I am trying to be a good Plex-er, and maybe help some other users with unmatched albums, But does Plex actually expect me to spend hours or days adding info to MB, just to stop my apparent self-inflicted short coming of owning albums not yet added to the MB database?
I will not touch MB database/UI. That is not my job. This is after all a “premium” library … I don’t blame OttoKerner at all, he is just doing his job …
In cases where you cannot find the artist or album on MusicBrainz (or you found an entry, but it needs to be corrected or expanded), you can submit information yourself. This way, you help everyone else in the future, too!
MusicBrainz has a lot of information to help you out. To get started, we recommend reviewing these two articles:
I think that that is part of the whole matching and re-matching process / problem . If you watch the “Dashboard” in Plex Web, you can see a lot of activity happening whenever you add music. In particular, the network activity can spike up a lot, even when there is no one using the server.
Speculation, but I think MB accoustic ID’s are generated and sent to wherever, for the MB database, in hopes of finding a match if not available instantly.
Are you saying that this ‘Mess’ is ONLY happening to Plex Pass Holders?
I am not one, I am preferring local metadata (with LMA at the bottom of the stack), setting it up the same way I have for years with MP3Tag (the way Plex wants it) and not having one minute of frustration or unexpected difficulties.
I added 9 Albums from the same artist yesterday - the entire process was over in seconds with everything appearing exactly as expected almost instantly.
Starting with version 1.18.0, Plex Media Server introduces new and improved features for music libraries. There are no longer “basic” vs “premium” music libraries; there is just a single type of music library. Plex Pass subscribers will continue having access to premium music-related features (automatic lyrics, Sweet Fades, loudness leveling, visualizers, etc.) just like before.
Nope, not at all… I would imagine it’s happening to everyone who is upgrading from the old metadata scanner to the new one who has some improperly tagged files…
What I’m referring to is, that an artist or album with a & .. will return an error in PlexWeb (when trying to select an matched artist/album from the results). The reason. A “&” in a querystring (GET) will break the query string parameters (which is the reason for the 400 bad request error). Which means, you can’t match it (save).
… I don’t blame OttoKerner at all, he is just doing his job …