Sonic Analysis - How does it work under the hood and what triggers it?

Server Version#: 1.30.1.6562
Player Version#: Built-in Web Player in Chrome (Version 109.0.5414.74 (Official Build) (64-bit)) browser.

First, Plex is awesome, thank you so much for continuing to iterate and improve on this product.

I have some Sonic Analysis questions i’m trying to better understand: I am curious how sonic analysis technically works. What triggers it? Why might it appear to keep retriggering? Is there a way to see overall % complete?

I’ve looked here:
https://www.plex.tv/blog/super-sonic-get-closer-to-your-music-in-plexamp/
& here…
https://support.plex.tv/articles/sonic-analysis-music/
, but can not understand that next level of detail that might be going on.

For a machine with old stuff…
CPU: Intel(R) Core™ i7-4900MQ CPU @ 2.80GHz
VIDEO: Intel(R) HD Graphics 4600 built-in + NVIDIA GeForce GT 740M
MEMORY: 8GB RAM
OS: Windows 10 Pro 22H2 19045.2486 (64-bit)

There are multiple libraries of various types (music library is large so I understand it should take time and the CPU will hurt)… the tracks were fully scanned and Sonic Analyzed to completion from my understanding. I believe this because it did not try to do analysis unless I added a new track, and then it would analyze the track and be done.

I have recently noticed the Activity bar circling regularly while looking in app.plex.tv and it has a big list of “Sonic Analysis” going on for Albums that never seems to end. :worried:

Our internet went out recently. Plex didn’t work and then there was the what will do chaos. lol. I enabled DLNA as a temporary fix, but the interface to navigate is no good that way. I decided, when the internet came back, I should have a backup solution in place for those occasions… enter playing around w/Jellyfin. (Sorry Plex world… I didn’t want to. :face_with_diagonal_mouth:)

Maybe the files in the folders being added causes it?
I think when I pointed Jellyfin to the music library, it started triggering Sonic Analysis on the music in Plex. I let both run in parallel for days. Then I shut Jellyfin when it seemed idle and let Plex keep Sonic analyzing for days. It crashed a few times and I restarted and it kept on. When it finally stopped analyzing, I ran Jellyfin again in parallel so they stay in sync and so I can jump back and forth to test things out. What I noticed is that a few days later Sonic Analysis was on high gear on Plex again. I killed Jellyfin and let Plex finish. I turned on Jellyfin and everything was ok for at least a week maybe. Then Sonic Analysis again. I have a feeling it may be Jellyfin doing something to trigger it, but i’m not sure. For example, if the .nfo file or the cover.jpg files are added in albums, does that trigger a potential change and re-sonic analysis? If so, that’s what this might just be… and it’s just taking forever for Jellyfin to finish adding that and then after for Plex to say, got it, reprocessed, we’re good. I’m not sure. Any thoughts, suggestions would be much appreciated.

Maybe I should set it to scheduled and let it keep churning away every night for however long it will need to take for both of them to be happy once and for all. I just worry that something might be retriggering it regularly and it will not actually ever end/stop doing sonic analysis.

It would be nice to see progress and to see overall % complete. Processing, Rebuilding Index, Scanning is all I see.

Thank you in advance.

I have seen Sonic Analysis choke on a file it did not like, which made it keep repeating that album. However, I have not seen that behavior in a long time, I think Plex improved error handling.

Still, I would try to identify the file it is working on and make sure it is OK.

You can do this by checking process details while SA is working. It will list the filename in the process info.

You can also do a quick check for some kinds of mangled music files if you look at your music library by file, and sort by length. I’ve had a handful of files which reported ridiculous durations, like 25 hours. Some of those files choked SA.

There are surely other things that can blow up SA, but bad files are the only problems I have had.

If your library is large, and if you have verified that SA does not seem to be getting stuck on a specific file, then I suspect that this is normal. It takes a long time.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.