Server Version#:1.24.0.4930
Player Version#:
This can’t be right. At this rate - it will take…
EIGHTY THREE DAYS to complete sonic scanning?
My Plex computer isn’t new - but it’s a 6 core processor with 16 GB of RAM. Fast enough that this shouldn’t take until Christmas.
What do I do? This CAN’T BE RIGHT.Plex Media Server Logs_2021-08-12_19-11-04.zip (7.3 MB)
Let it run over night to get a better feeling of the analysis pace.
The processing takes an awful amount of power but the result is absolutely worth it. Make sure to review the time windows of your server’s scheduled maintenance to give it enough time to work.
Delta updates when adding new media are subsequently much smoother.
I’m not even able to make it work…
Where are the logs for this particular feature?
You don’t “make it work”. You enable it and it’ll run during the scheduled maintenance. As ohmyjosh pointed out, one maintenance window / night might not be enough to finish the job (depending on the size of your library).
What you can influence is the start/end time of your scheduled maintenance windows:
Settings > [Server Name] > Scheduled Tasks > Time at which tasks start to run and Time at which tasks stop running
I understand that, I have modified the time to start and it’s not doing anything. Just scanning my libraries and optimizing the database, but Sonic Analysis is not running (and yes, I have Plex Server 1.24 and the Music Library has the option enabled)
Actually, it looks like you can start it by:
Setting the dropdown to “as a scheduled task and when media is added,” enabling the checkbox in the Library settings, and running “Scan Library Files.” That started it off for me. Though it’s probably best to stick with the task schedule.
Fair point… most users probably want to keep the scan during the “off hours” when their server isn’t used as it’ll average at 50% of your CPU capacity. That could be too much for many to play/transcode media in parallel.
@trotskylenin : scheduled maintenance tasks are queued and executed sequentially; so if your server has some other tasks it’ll first finish those.
@tom80H This is my second attempt… the first one, didn’t do anything even after finishing the rest of the maintenance tasks.
I’ve also tried what @beckfield says without success.
I’m waiting to this second attempt to finish scanning and optimizing the database to see if it works or not… but I’m not so positive about it 
I’ll let it keep running - I had it start by adding an album (and chose the Analyze when adding media option). My question is - maintenance will stop at 9 AM tomorrow… will this stop or keep going because I started it outside of maintenance window? Also - when it does stop, I assume it will pick up where it left off the next day?
Update - it has analyzed 10 albums in an hour and 12 minutes. This CAN’T be right.
From the blog announcement:
“The new sonic analysis can be a fairly taxing operation on your processor, and depending on the size of your library can take a number of hours or even days to complete once you enable it.”
Well it ended and it did nothing…
It’s taking literally TEN MINUTES to process each album. There’s no way this should take three months? Please help me.
That fast… mine is 0.7% and it’s taking almost 20 minutes per album hahaha.
Nevermind, at least it’s working.
@tom80H The reason it didn’t appeared in the web was because the web version of the server is not the same that the one in app.plex.tv
If I go to app.plex.tv I can see the progress:
Is it possible your laptop is throttling to maintain reasonable thermals?
Also: what power mode have you got applied in Windows? I haven’t got a Windows device handy, but IIRC the power menu provides options between performance, power saving, or balanced. Bumping to performance, and ensuring your fans are clear and the laptop is well ventilated might help.
FWIW, I ran sonic analysis on my library of 55,000 tracks at the time, and it took approximately a week of running 24/7. That’s on a quad core i5 Intel NUC, which is also a mobile processor like that in a laptop.
And finally, if I recall correctly the analysis processes by last in first. If you happened to add a few large albums recently (think compilations with lots of tracks etc), then they may be taking longer than a typical album will, and skewing your time estimate a bit.
It’s a Desktop PC not a laptop and power settings are on high performance.
Iirc, it took about a week or 2 for 250k+ tracks on an older dual Xeon 24 cores (12 in use by analysis).
ahh sorry I’m conflating a couple of threads here.
Definitely seems slower than it should be then. I looked at your logs and can’t see anything particularly suspect.
If I’m reading the logs correctly, (which I very well may not be, in which case I’m happy for someone who knows a little more to chime in), the time between tracks starting and ending their analysis looks to be about what I expect (around ~2 seconds):
Start:
Aug 12, 2021 18:48:36.307 [4916] DEBUG - [MusicAnalysis/JobRunner] Jobs: Starting child process with pid 8716
End:
Aug 12, 2021 18:48:38.095 [6512] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\Plex Transcoder.exe' exit code for process 8716 is 0 (success)
I will chime in and say analysis does seem unusually slow for me if 2 seconds per track is expected to be normal. I’m doing about one album every 10 minutes.
Not sure where to look in the logs.
