To clarify, if you ever need to remove files from library and re-add them, there is a serious bug in the server which needs to be fixed. The maintenance tasks should find albums which need loudness analysis and perform the work without any such machinations.
Thanks for the reply. The next time I come across this issue, I’ll generate the logs while replicating the issue and upload them. I didn’t have debugging turned on this time around.
I’ve had this issue for the past few months after using Lidarr to reorganize the music files. Any new music files generate the loudness data correctly, but existing files have not. I have the settings set to “as a scheduled task and when media is added” in the library settings. I have the scheduled tasks time set to run from 1:00 to 0:00 which should allow it to run all day, it does for video previews when I have that enabled. I tried the steps of removing all the music files, running a scan library files, re-adding the music files, and running a scan again. Nothing changed at all. The only thing I can think of to resolve it is to remove the music library completely from Plex and re-add it. This is just not ideal as the library will have to spend hours/days generating sonic data, which is currently still working. Hopefully these logs help! Plex Media Server Logs_2022-09-14_11-13-00.zip (4.7 MB)
Yeah it is definitely working for any new albums I add to the library. But existing albums all have no loudness data. I have 2455 albums in the library, so if the logs say 2000 computed that night the majority of the library should have loudness data. It’s just not there. I can confirm this by using the “Get Info” option on newly imported songs in an albums and the data is there. It will also shows a volumes graph or whatever in Plexamp. But for about 70% (just a guess) of the library there is no loudness data in “Get Info” or in Plexamp. I wonder if there is some disconnect between the “Plex Media Scanner” computing loudness data, and whatever index that stores the loudness data that isn’t getting updated.
I am seeing similar behavior. Some older tracks that I imported have been there for months and sonic analysis has never kicked in. I look at the info for the files and it shows no gain information.
I am still experiencing this issue with version 1.29.2.6364. I have a particular 29-disc 249-song box set that my server refuses to scan for loudness. I tried reimporting the box set multiple times since I initially added it a month ago.
I noticed if my server is shut down, upon startup the activity monitor states loudness is being scanned for this box set. This occurred right before the attached logs. Also, the alerts page says, " The butler performed loudness analysis on 0 albums."
It means to analyze this, the server will decode all tracks at once to WAV format, then store these in the /tmp folder. Then it performs analysis on those WAV files.
If the storage volume which hosts the /tmp folder is running full during this, analysis will fail.
(Particularly important if you use Docker which doesn’t map the container’s /tmp to a folder on hard drive by default, but simply uses RAM instead.)
Your server logs are unfortunately quite useless, since you don’t seem to have activated “debug” logging.
Hopefully, these logs help with debugging enabled. I changed my loudness task to run on import and as a scheduled task. The box set was reimported and I saw the loudness scanning message in the activity monitor. This message stayed for about 5 hours, however, the loudness data did not generate.
Plex runs on a Synology NAS with plenty of space on the volume. I noticed multiple music analysis folders containing WAV files for this set under my tmp folder.
I found the fix for this. I need to move a few of the discs into my media folder at a time and wait the loudness scanning to complete. I am now up to disc 14 with loudness data.
Happy Listening!