For some reason, the metadata for my entire music collection is not reading properly. The year metadata, as well as album art is not loading at all… I’m quite meticulous about my tagging, so this is a pretty big problem for me.
I’m using a Synology NAS and have corrected the permissions so Plex can source from my drives.
What am I doing wrong? Any help would be appreciated.
I have no idea if this is the same thing or not, hence why I posted. This is my first time on the forums, so apologies if this is already covered elsewhere.
Sorry if I came off pointing this at you. This was more to the Dev’s basically saying “Oh another post about this” about an item that has not been fixed yet.
I hope your logs show them something so they can get this solved. I am in the same boat on my Nvidia shield. I don’t have all day to click the button and actually have cover art there… I mean it’s NICE that I don’t have to go out and search for it… but sucks that I have to do it to begin with.
Hey, no worries mate. I just to be clear that I did some research before posting here. I work in customer service so I know how it goes.
I have spent thousands of hours tagging all my music and am currently at around 150,000 songs, all of which are expertly tagged. I don’t have the time and patience to add all the years and artwork by hand on Plex, a second time.
I really hope they fix this soon. Do you know if there is any temporary solution/workaroundI could use to make it display? Would reinstalling from scratch work?
How much music did you give it to index at the time your logs were captured?
It appears to get through the A’s ok and then slugs down when it gets into the B’s.
This appear to be the case as you’re seeing it?
This tells me the database is getting beat up pretty hard (fragmented). An ARMv7 can’t get through all the database indirection links (caused by the fragmentation) to complete the query before the timer fires and flags Fragmentation.
Aug 09, 2018 15:13:57.740 [0x42b3f000] DEBUG - HTTP requesting GET http://127.0.0.1:32400/library/changestamp
Aug 09, 2018 15:13:58.714 [0x44142400] WARN - SLOW QUERY: It took 250.000000 ms to retrieve 13 items.
Aug 09, 2018 15:14:01.486 [0x42b3f000] DEBUG - HTTP 200 response from GET http://127.0.0.1:32400/library/changestamp
I’m syncing data over from my computer onto my NAS, so I’d imagine that may be causing the fragmentation. Is there a way to fix this? For the record, the “A” artists aren’t even being added to my library at all, and it starts on "B’ for some reason.
mp3 tags ( including year and artwork) are being retrieved for me fine. made a copy an album and edited the tags on the copy. Shows up like I edited the tags. ChuckPA may be onto something
I have kind of the same setup… as in Nvidia shield to a NAS Device. At this point, if it is skipping items and we just run the process again and have it pick up the Local Art it is missing?
You have 120,000 total pieces of music ? How much of that (total count if possible) falls under “B” ?
As for order, B was enountered first. That’s all.
Not to hijack, but to make sure for myself in the future. I’ve just started migrating a large collection of movies to a NAS, with 4TB of music to follow. For the movies, rather than copying them straight to the movie folder for plex to deal with, I’ve dumped them to a non-plex DOWNLOAD folder, and then move them over in smaller chunks of 10-20 movies to insure that plex is gathering metadata/I’ve named files with the correct conventions.
Doing this with music would be safer I suspect? So as not to overload PLEX’s metadata search or whatever the process it does when scanning libraries?
Just to follow up, I organized my artists like you said (and added a single letter at a time) and it’s still doing the same thing, and missing metadata.
I wonder if this has something to do with my HDDs updating and data being synced as parity between the two drives, additionally. I will attempt to defragment it once the data finishes moving.
You might be running out of CPU plain-and-simple. Moving data and generating parity is a load.
If you’re running rsync or similar client, that’s a notable load unto itself.
When all is quiescent, create a new library section containing just the “A” directory and watch what happens.