When I want to add my Indie Rock Compilation Albums of about 100+ tracks to Plex Music, the loudness generation fails with the console message “Task did not finish in allotted time, Killing”.
When I tail the Plex Media Scanner Log I can watch the scanner working through the album track by track successfully. But as it’s an Atom CPU on a NAS (Synology, Docker) it’s too slow for the timeout and the ffmpeg scanner processes get killed before the last track.
Because loudness is saved and stored per album item in Plex, none of the tracks get loudness information. And next time a loudness call is scheduled it begins with that compilations again.
So with lots of big compilation albums this is blocking loudness generation entirely because there is no progress. It works through all the albums, does not save anything and never gets to all the other, shorter albums in the queue.
Can this be resolved by Plex by increasing the timeout or can the timeout be tweaked by users?
The Sonic Analysis BTW works perfectly on those Albums alas its slower but seems to have a lower timeout configured.
I have tried with a native install without docker on synology DSM and only adding one compilation with 100+ tracks. Exactly the same behavior.
Time for planned task is set from 23h to 22h. This is not causing the problem.
Server Version#: 1.32.4.7164
Player Version#: Latest Plexamp Version
If it is any consolation, I have a compilation album that contains 2008 tracks (100 tracks per disc) and to my knowledge all of the tracks in that compilation album have loudness data attached now.
The timeout message appears to be accurate in that the butler does not have enough time to complete the task in a single session.
Make sure you have Plex Settings > Library > ‘Analyze audio tracks for loudness’ set to as a scheduled task and when media is added
This will allow the butler to complete the task during scheduled maintenance. This may take several days or several weeks to complete depending on what tasks are performed during maintenance, but eventually the process will complete.
To check a track for loudness data, use Get Info and then on the right hand side of the pane, look for the loudness values.
By reading the logs I can clearly confirm that it analyses the same albums over and over again. The Scanner does not continue on the track it was killed by the Butler as this process works on an album basis.
I think this has to do with my NAS Atom CPU (Synology DS412+) being just a tad to slow with loudness analysis and the timeout set by Plex programmers just a tad too short for that.
Would be great to see that increased. Sure, you wouldn’t want a stale process to run forever but just a few minutes more would suffice. On most albums it stops around track 95.
I have almost the same processor in my DS1813+, so I am aware of it’s under performance and I do not like being limited to DSM 7.1 now, but you are limited to DSM 6.2.4, which is probably even more frustrating for you.
I believe the only thing required here is a little patience. As I have shown, the process will complete, it is a simply a matter of when and NOT IF it will complete, but I do share your frustration to some degree.
Overall Plex is pretty well balanced when it comes to metering out resources, even on our slightly under powered NAS and I am sure you would not want to effect any other area of operation, simply to extend this process.
I would really love to know if there is a way to see which item the butler works on right now
(loudness analysis is stuck on a file in a 500 track compilation).
And it would be so nice to have a page somewhere like the alerts where I could see all the tasks the butler still has to do, like loudness, sonic analysis, thumbnail creation, intros and outros etc.
Maybe even with a option to disable features for library items
