Of course. It will start after all other Scheduled Tasks are done, during the nightly server maintenance. https://support.plex.tv/articles/201553286-scheduled-tasks/
For me it didn’t do that.
Also, why did it indicate that it’s scanning x number of albums as soon as the scheduled tasks would start, when it’s actually not scanning yet?
(The problem is solved for me now. All my albums have been analysed, but it would not work with only the scheduled tasks)
Depending on your CPU and RAM architecture, would encourage running continuously for sometime and not on a schedule to really get a feel of how well things are going.
Is the number supposed to drop or change? Mine now has said processing 4377 for 5 days with no change.
It should count down, yours is stuck. Look for a transcoder process that is stuck on one file, that’s what happened to me. If that isn’t your problem I am not sure what to do.
I do have a transcoder process running when no one is currently transcoding. Should I end the process?
If you have the same problem I had, then the transcoder is stuck on one file. If you kill the process, it will skip that file and keep going… but it will go back to that file later, and get stuck again.
So, you want to find out what file it is chewing on, so you can fix it. If you are running Windows you can see the transcoder command line with Process Explorer. If you are on Linux, I guess it would be something like ps -ax|grep trans
Other people have reported analysis getting stuck for other non-transcoder reasons. So make sure the transcoder is actually stuck on one file before you kill it.
Before you do, inspect the process to see which file/album it is processing.
Remove this album temporarily for the next analysis cycle.
Check the folder organization of the offending album.
If applicable, change folder organization and filenames it to conform better to the Plex rules. https://support.plex.tv/articles/200265296-adding-music-media-from-folders/
(There was a case where a user had double subfolders per disc in a multi-disc album. Once he corrected this, the analysis went successfully.)
If you have the original source for the album, rip it again with up-to-date software.
If you are working with a historically-grown mp3 collection, use software like
http://mp3diags.sourceforge.net/ to check for and repair invalid files.
I would like to see an update to this feature where once it scans like 100 albums, it does what it needs to do to finish up and allow the user to use the feature on those 100 albums. This waiting around until the whole thing has completed to do the final clean up or whatever it’s doing is just not right. If something like this takes more then 1 full day, there needs to be a fix for this to get this feature working right away.
Also, heard some talk about an update where it would skip bad songs. I would assume we would need this as well at some point. It would suck after days and days of waiting and because of one bad song, we can’t move on.
2 Likes
Like most things that are “good” they take time. While sonic analysis does take a lot of time, I have found it works quite well, at least for me.
I do wonder though if it “is not used until all done”. I would think this is not the case as the app you use would likely seek the sonic analyzed files as a preference. But I could be wrong…
That is the case – sonic features are only available after the scan is complete.
This feature looks really cool. Unfortunately it will take another 35 days approximately before I can witness it first hand :-/ CPU is on 60% 24/7 probably doing its best to process the data. Is there any way to look at intermediate results?
Unfortunately not. It would not be satisfactory anyway.
Had my 3-4 days of continuous scans done, so far so good, I echo that sentiment.
22 days ago I was 3892 albums. I changed my setting to run as a scheduled task about 10-12 hours a day in the over night when I’m not using my server. As of right now I’m at 2896 albums left.
So another few months I guess… yeash.
I am looking at 2 months at my current rate of 15 albums per hour. I have done simple tests to get that number but that’s about the norm for my QNAP Nas. I know the NAS is only using 50% or I am thinking 2 cores? it would be nice to bump it up to 3 or even 4… for what I am doing and then just run it at night or something… right now it’s running 24/7. I think the number of cores should be an option at some point…(unless I am missing something)
My QNAP NAS finished my 3000 albums in 4 days, a lot faster than expected. Really love the feature as well. It’s generally good at picking similarly sounding albums/tracks.
1 Like
I have a qnap as well. Monitoring the cpu, it seems to ping pong around 50%-95% which is why I set it to only run certain hours. I may let it go 24/7 again in the hopes it finishes up in a month.
Here’s one more data point for the curious:
CPU: i3-7100
OS: Linux
Sonic Analysis rate: 60 albums/hr
I did this by checking timestamps at 60% and 70% completion per the logs. SA has been running 100% smoothly so far, likely because I already replaced a couple of problematic files when I did this before on a different server install.
This server has been spending some time on video thumbnails too, hard to say how much… but if you’re around an album per minute on this CPU you are probably performing reasonably.
Hi , i seem to have a dud file , could some one explain how i can easily identify this file so SA can resume , Thanx
