Sonic analysis appears to be looking for temp directory that doesn't exist

Server Version#:4.70.0
Player Version#:
I am encountering an error where the analysis creates the temporary .wav files for this particular album. Then a process kicks off looking for a folder that does not appear to exist. The Plex Media Server process just hangs and killing it will restart the analysis where it gets stuck again.

Plex Media Server.log (4.1 MB)
Plex Media Scanner Analysis.log (17.2 KB)

The log files you posted don’t appear to contain any clue for this non-existing folder.

Nov 22, 2021 11:28:30.558 [1912] DEBUG - [MusicAnalysis/JobRunner] Job running: set “FFMPEG_EXTERNAL_LIBS=\\?\F:\Plex\Plex\ Media\ Server\Codecs\be22e26-4019-windows-x86\” & “C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe” “Plex Music Analyzer” C:\Windows\TEMP\music-analysis-411ced2d-b433-4314-82e4-07f1d1779b3b “C:\Program Files (x86)\Plex\Plex Media Server\Resources\Music.tflite” labels index.txt
Nov 22, 2021 11:28:30.572 [1912] DEBUG - [MusicAnalysis/JobRunner] Jobs: Starting child process with pid 13480

C:\Windows\TEMP\music-analysis-411ced2d-b433-4314-82e4-07f1d1779b3b did not exist at the time of this run. From self diagnosing the logs, the scan would appear to get to this point then hang up, assuming because it either was trying to create this directory and couldn’t, or was looking for it and it didn’t exist.

AFAIR, the transcoder is normally trying to create the temporary WAV files in the general TEMP folder of the user. Which is usually inside the C:\Users\... folder structure.
That it is looking inside of C:\Windows\TEMP\ instead, means to me that something about the basic runtime environment is different on your server.
Is it possible that you are running Plex as a system service or have started it with “Run as Administrator”?

I have it running as a windows service.

So do I. But the sonic analysis is working for me.

Do you have any other software running on the server which is watching and “cleaning” temporary folders etc. ?

Nothing that stands out to me. I have a defragment tool that runs, but i don’t believe that would delete the directory.

I did have some temp folders out there from previous sonic runs that either crashed or hung up. Days and weeks old. Looking up older threads, it was said those were safe to delete and I had done so on the folders from days prior to this run.

Were these also inside of c:\Windows\Temp ?

yes. Scan kicked off again this morning. Previous scan attempts had similar naming convention as well.

That means to me that the files are indeed at the place where Plex is expecting them.
Maybe disable your 3rd-party anti virus to prevent it from interfering?

Is their an override to set the temp path for media analysis?

I would prefer to run it out to a RAM drive like I do for Transcodes and PhotoTranscoder.

For the time being I have removed the album in question from my library and sonic scan runs and completes without issue.

That’s a bad idea, because Plex will use 50% of your CPU cores at once for analysis. So if you have 8 cores, Plex will use them to analyse 4 albums concurrently.
Now imagine that these 4 albums are all multi-disc releases. Your RAM drive will be out of memory pretty quickly and the analysis will fail.

In general, it is my opinion to give the RAM to the OS, which will put it automatically to good use for file caching. Then use a fast conventional hard drive for temporary storage.

The developers would like to have a copy of this album for analysis.

You might wanna try again with a fresh rip of this album.

Some of us are running on larger servers (128 cores, 1TB RAM) with SSD cache accelerated disk arrays. If we could define the path, as previously stated to a RAM drive then can speed the process up and reduce writes on our SSD drives.

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