Server Version#: 1.28.0.5999
Player Version#: Multiple
I have a large music library that I recently moved from one location to another due to a NAS upgrade. When I updated the library in plex to see the new location, all of the loudness and waveform data that appears when using apps like Plexamp have disappeared. Now, when I play things in Plexamp, it looks like a brand new song that has not gone through loudness and sonic analysis. Tried having plex re-analyze everything but beyond that not sure what I can do to fix it.
In my experience any media move from the one location to another, plex will re analyse the media for changes.
For video media’s this forces stuff like deep analysis & intro detection to be redone. I’d imagine it’s the same for audio analysis (loudness & sonic) for music media.
If you have them set as a scheduled task then you’ll need to let the server finish the rework during maintenance. You could increase the scheduled maintenance time to help move the work along.
Same issue here. And when I can get it to initiate a loudness scan it doesn’t actually scan the files or generate loudness data. It shows that it’s doing it in the activity menu and in the logs, but it goes extremely unrealistically fast - like 5 albums per second. It’s like it can tell it needs to do loudness analysis for those files but then just loads them and moves on without actually doing it.
Plex dance fixes the issue if I do it on an individual item, but I really don’t want to do that with the whole library, especially given how long it took to do the sonic analysis.
If a plex dance works and if you want to do a whole library redone I would suggest disabling loudness at the library level, leave it a day or two so library maintenance kicks in and removes it all from the db and then enable it again. That should force the plex system to re generate loudness from scratch. Unless someone else has a better suggestion I’d give that a go.
Keep in mind that the loudness analysis as such cannot be triggered by hand. (i.e. “Analyze” does not perform the loudness analysis. It will only mark the album for analysis during the next maintenance period.)
It will only be performed during the nightly server maintenance or when adding an album “as new” (which explains why it works when performing the Plex dance).
Thanks for following up on this. What I’m referring to is indeed the nightly server maintenance. This can’t be manually triggered, but it can be encouraged by adjusting the maintenance start and end times (move them to a setting that doesn’t include “right now,” save, and then move them to a setting that includes "right now).
Would you be willing to look at the logs I uploaded? It’s scanning through the library and showing “Generating loudness data” in the top right menu. But it scans through the albums extremely fast - around 5 per second, and when it’s done there’s not loudness data added.
Thanks for the suggestion. What specific settings would need to be changed for it to actually remove the loudness data from the database during the maintenance cycle?
I would restart your plex server after the change. That hopefully will remove the loudness from your plex db once maintenance kicks in. I’ve never tested this myself for loudness but have for intro detection and it did remove it so I’m hoping it does for this also. Good luck.
I seem to have managed to get it unstuck using the command line interface for the scanner. The command that worked was --analyze-loudness --force --section x (where x is the # identifier of the library I wanted to scan).
It’s only just started, but it does seem to be working. The albums it says in the logs that it updated are indeed updated. I’ll verify here when it finishes scanning whether it completed the scan and updated the whole library.
To me this really seems like something that should be possible in the GUI.
Edit: Well, it’s taken a few days of running constantly on my underpowered little NAS, but it’s made it all the way through in alphabetical order up to the W’s and should be done within the next few hours. Glad to have found a workaround for this, but I hope the developers consider adding a way to force the scanner to re-analyze loudness using the GUI.
I have the same problem after moving my music to a different location. Unfortunately If I do it with the command line the scanner crashes immediately.
I tried to disable loudness analyzation as @anon5074910 suggested which worked in removing the data (albums I added after the move were analyzed). Enabling this afterwards again started the analyzing but didn’t save it in the end.
