So, I have the PlexPass advanced music library turned on, I’ve asked it to analyze my entire library, and I’ve even asked it to specifically analyze certain songs and albums, and yet it never picks up any loudness data. Can I actually see the progress of the “analyzing” process somewhere?
Solution: My PMS process was bugged or outdated, and a forced upgrade to the latest version along with a manual execution of a library scan solved the issue.
I also have this problem, kinda. After some analysis runs with server 1.11.0.4633 all of my tracks before a particular album by an artist starting with B have loudness data (about 1/5 or 1/6 of my total library by albums), but all tracks after don’t. Manually analyzing specific tracks doesn’t fix this either. I’ve tailed the log during analysis and verified that the server scans my entire music collection without issue, but I don’t see any data about loudness gathering so it’s unclear to me where this is failing. It might be working fine but for some reason PlexAmp isn’t getting it?
The Plex Media Scanner Deep Analysis log-files should have data about what it’s doing. The job gets kicked off:
After you do a scan when you’ve added media (even if you cancel the scan right after it adds the new media).
Nightly scheduled tasks.
On the CLI running the --analyze-loudness command on an item or library.
We’re tracking a crash in this area, so if you can figure out a track which is causing it to crash, we’d greatly appreciate your help there, since it’s hard for us to fix just from the crash data alone.
Similar thing happened to me just now. Added 60k+ tracks and couple hours later getting high cpu from 3 processes -analyze loudness deep analysis, with nothing in my log except
Dec 30, 2017 10:02:59.078 [0x7fdd15525700] INFO - Plex Media Scanner v1.10.1.4602-f54242b6b - ubuntu PC x86_64 - build: linux-ubuntu-x86_64 - GMT -07:00
Dec 30, 2017 10:02:59.078 [0x7fdd15525700] INFO - Linux version: 4.4.0-104-generic (#127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017), language: en-US
Dec 30, 2017 10:02:59.078 [0x7fdd15525700] INFO - Processor AMD FX™-8350 Eight-Core Processor
Dec 30, 2017 10:02:59.078 [0x7fdd15525700] INFO - /usr/lib/plexmediaserver/Plex Media Scanner --analyze-loudness --force --item 60747 --log-file-suffix Deep Analysis
Dec 30, 2017 10:02:59.383 [0x7fdd0fb3f700] WARN - [FFMPEG] - Could not update timestamps for skipped samples.
Doing “systemctl restart plexmediaserver” seems to have stopped the deep analysis… for now atleast.
So, apparently my PMS had gotten stuck on version 1.9 and refused to auto-update. There was some value in the PLIST file I had to remove, and now I managed to get it up to 1.11. It seems that might have caused the initial inability to actually do a full library analysis. Either way, now I’m running it off CLI, and it seems to be chugging along great. Tested on a single track, and it now correctly shows loudness information in the progress bar in Plexamp.
Yep, worked fine. It finished its run during the night.
However, two other small bugs or quirks did show up.
When browsing my music library in Plex Web, I cannot start “Analyze” when clicking the menu-button on an artist entry. However, I can use multi-select, select only that artist, and then click the global menu-button and start “Analyze”. There’s no reason that option can’t be available directly on artist or album items without having to do a multi-select first.
When starting a targeted analysis like this, I can see the process spin up, run and finish, but the activity animation on the target never stops or goes away. It seemingly spins forever. Conversely, if I start an analysis, note the activity animation and then reload the page, the animation will disappear from the item, even if I can confirm the scanning process is still running. If this is the intended behavior, then I think a one-time “Media analysis started” popup that disappears after a few seconds (like when refreshing a library) is much more suitable. Otherwise it needs to be reconnected to the process that is started, so that a successful finish and running status can be fetched at all times.