Same issue here. Albums added as late as 6 days ago are fine, but I added a few albums today (all new artists in my library) and I experienced same issue as you guys (i.e. not pulling all metadata).
1 Like
Same problem here… no new albums have any metadata, however, if I “Fix Match” I see that the Agent is still able to pull covers, years, etc. Strangely, even though the year shows in “Fix Match”, it doesn’t update on the album when I Submit.
Another oddity - I recently upgraded a few albums from MP3 to FLAC and some of the albums that were upgraded in quality had their metadata refreshed despite the fact that completely new albums don’t pull any metadata (I delete all “Moods” from my albums so it’s very obvious when an album adds them back).
However, completely new albums that I add to Plex will not pull Moods or any other metadata. I’m not even getting a Genre added to my new albums.
2 Likes
EDIT - OK! Somebody just merged this post into this thread so at least there’s a mod who’s aware of it now. We’ll see if there’s any response from the dev team now.
Dear Devs,
We know you’re busy, but can somebody at least comment on the issue with music metadata that’s currently plaguing the world?
We’re not asking for a perfect fix delivered in ten minutes. We’d just like to know that somebody has actually heard about this back at Plex HQ and is at least planning on taking a look.
The metadata import has been broken since at least 1.22.1.4271. It’s a significant headache as it makes adding new titles a real PITA in terms of library management. I’ve already got a backlog of 40+ albums that will need manual correcting once the problem is patched. The issue is just going to get worse and worse.
Any little blurb about it would help calm a lot of nerves that a fix will eventually be coming. Just a sign of life from over at the dev team would be great.
Thanks!
Server Version#: 1.22.1.4275
Player Version#:1.30.1.2115-81e1fc3f and others
1 Like
afaik this is fixed in an upcoming version 1.23 which I believe is getting released early next week
6 Likes
I spoke to some Plex devs regarding this. The issue is a know regression. It has been fixed, however, the new code is not released yet. Should be soon.
Thanks! @BigWheel. Good timing!
3 Likes
YES!
Thank you very much BigWheel.
A little communication is all it takes to keep the customers happy.
3 Likes
Thanks @BigWheel for the heads up.
1 Like
Great news! Thanks a lot.
1 Like
What do you say thank you for? So that you can take care of everything by yourself and beg for answers? Or that even the simplest things don’t work? We don’t have a Plex Pass but a Problem Pass. Lifetime.
@manuele_gmx_at It’s not like this topic has been a problem for years. I think their response has been fairly quick, and I wanted to thank them for that.
2 Likes
This has been an issue for ages. All unmatched tracks are automatically listed as Popular Tracks, like Bonus Tracks from a release that’s not on MB.
@solitaryreign I had never noticed. Maybe this will get fixed as well.
@manuele_gmx_at no need to be aggressive. This particular issue was raised a few days ago and should be addressed by next release. I think that owes a thank you.
2 Likes
I agree with thi3rrym that there’s no need to be rude. The dev team can be slow to address particular issues but I understand what it’s like to run a small-mid sized startup trying to deal with a rat’s nest of complex technical issues. I own a company that deals with the same problem and can sympathize. In general I’m rather impressed by, although sometimes perplexed by, the work the dev team does.
Where I do have to offer criticism, though, is with support communication. If BigWheel or someone else with a fancy “Plex Employee” banner had popped in to the thread at the very beginning it would have avoided a lot of customer angst. Just a simple “Issue noted and passed to the devs.” in the first ten posts would have gone a long way to keeping everybody happy. The problem isn’t that bugs aren’t fixed, it’s that there’s no communication back to the customer that their concerns are being addressed. It’s the feeling of being ignored that pisses people off - hence my post calling out the team for more com on this issue.
Again, I sympathize because I deal with the same issues in my own company. In the age of Amazon Prime everybody expects delivery in ten minutes. If we don’t fire back a reply to a support request the second it comes in the customer starts to go nuts.
Plex really needs to step up its game in this area to match the world’s current demand for instant gratification. Hopefully they’ll take $1-2M of the $50M they just got and put it straight into better customer support.
So yes, thanks to BigWheel for getting back on this. Hopefully they’ll give him and his peers more resources to work with so that they can do it for every thread.
4 Likes
You can see the actual error in the music agents log file:
2021-04-17 08:08:10,446 (80b643000) : DEBUG (networking:143) - Requesting 'http://127.0.0.1:32400/metadata/agents/music/library/metadata/5d07c58e403c640290a9a8a5?includeAlternates=1&includeChildren=1'
2021-04-17 08:08:10,823 (80b643000) : CRITICAL (agentkit:1095) - Exception in the update function of agent named 'Plex Music', called with guid 'plex://album/5d07c58e403c640290a9a8a5' (most recent call last):
File "/usr/local/share/plexmediaserver-plexpass/Resources/Plug-ins-a97b03fad/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/api/agentkit.py", line 1093, in _update
agent.update(obj, media, lang, **kwargs)
File "/usr/local/share/plexmediaserver-plexpass/Resources/Plug-ins-a97b03fad/PlexMusic.bundle/Contents/Code/__init__.py", line 137, in update
res = XML.ElementFromURL(url)
File "/usr/local/share/plexmediaserver-plexpass/Resources/Plug-ins-a97b03fad/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/api/parsekit.py", line 344, in ElementFromURL
method=method,
File "/usr/local/share/plexmediaserver-plexpass/Resources/Plug-ins-a97b03fad/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/api/networkkit.py", line 67, in _http_request
req = self._core.networking.http_request(url, *args, **kwargs)
File "/usr/local/share/plexmediaserver-plexpass/Resources/Plug-ins-a97b03fad/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 346, in http_request
return HTTPRequest(self._core, url, data, h, url_cache, encoding, errors, timeout, immediate, sleep, opener, follow_redirects, method)
File "/usr/local/share/plexmediaserver-plexpass/Resources/Plug-ins-a97b03fad/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 118, in __init__
self.load()
File "/usr/local/share/plexmediaserver-plexpass/Resources/Plug-ins-a97b03fad/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 160, in load
self._data = self._core.data.archiving.gzip_decompress(f.read())
File "/usr/local/share/plexmediaserver-plexpass/Resources/Python/lib/python2.7/socket.py", line 355, in read
data = self._sock.recv(rbufsize)
File "/usr/local/share/plexmediaserver-plexpass/Resources/Python/lib/python2.7/httplib.py", line 583, in read
return self._read_chunked(amt)
File "/usr/local/share/plexmediaserver-plexpass/Resources/Python/lib/python2.7/httplib.py", line 637, in _read_chunked
raise IncompleteRead(''.join(value))
IncompleteRead: IncompleteRead(0 bytes read)
If you attempt to open the URL it is requesting, you get a 401 Unauthorized error. I’ve been trying to fix this bug since I installed the new version, thinking it was something I did when I moved my metadata folder to a different drive.
2 Likes
A little heads up: just installed PMS 1.22.3.4392, and fixed match for new artists. The issue seems to still be here.
Let’s wait for version 1.23 like @BigWheel mentioned.
1 Like
Just fyi, I found out that 1.23 is not going to get released this week as there are some issues unrelated to the fix for the music metadata issue that need to get addressed. I’m hoping next week but will let y’all know if things change.
6 Likes
Thanks for the update!
Yes, thank you very much BigWheel.
Thanks for the update! I suppose I’ve never tried this, but is there a way to roll back to a previous version of the server before music metadata went south?
