· Unable to identify the last few remaining files that are causing the background audio analysis to hang indefinitely.
How can we help?
· I'm having trouble adding music to my library. The audio analysis is stuck processing the last 5 files, but the logs either do not show which files are problematic, or the log's naming convention is such that I cannot easily identify the offending files. Is it possible that you could enable an additional logging feature which creates a digest of the audio analysis? It would be very helpful to have a chronological log of precisely what the scanner is processing at every stage.
Hi Ian I had this problem when moving between servers after a restore last week.
After a reboot or a restart of the Roon service this tends to go away.
It is something I have seen after every restore, alongside analysis of tracks that have already been analysed being done again
Rebooting RoonServer is a strong first suggestion to stabilize conditions.
What do you see under Settings → Library → Skipped files? Please share a screenshot here.
We’ve taken a closer look at diagnostic logging and identified a pattern. Audio analysis completes and the API matches the waveform, but the request to the analysis server then times out.
In other cases, the files are skipped during import. An example we found was this file: (09) [KOOP (H)] Drum Rhythm a (H).flac.
I recommend verifying that no stateful firewall or unreliable DNS server assigned in the router is preventing successful requests to the analysis server.
There is nothing under settings that references skipped files. I just have the analysis indicator spinning at 0/5 remaining files.
I use Cloudflare public DNS which shouldn’t pose any problems.
All I really want is to be able to parse my logs more effectively so I can figure out what my server is choking on. Is there a way to filter the logs to show only the results of the analysis engine? Where do you find the log of the most recent library scan?
Additionally, and FYI, the desktop app does this responsive viewport thing where it hides crucial settings based on the window size. So while accessing my server via remote desktop on mobile, I still couldn’t see all the options available under Settings > Library (pictured below).
Finally, as far as network calls, after filtering the server logs, all the reported endpoints responded with 200, and cached 304 codes, so I’m fairly certain neither DNS or Firewall are an issue.
Can you please try to reboot your Roon Server a few times, verify that the analyzing is still happening and then reboot again after? Please repeat this process 3-5 times so that a new log file is generated on each restart, so that we can look for commonalities in the logs. Once you have rebooted please let us know here so that we can enable and check diagnostics for your account. Thanks!
I took your advice and restarted the RoonServer a dozen times. Within that timeframe, I had the audio analysis jump around from scanning 0/5 files, 0/4 files, 10/12 files and 1/2 files. I deleted all the logs and restarted the RoonServer about 4 more times for a fresh set of logs. for whatever reason the analysis icon has stopped spinning now.
Aside from a few problem tracks which were “not found in AudioAnalysis Service”, I couldn’t determine why the process was hanging nor on which files it was seemingly stuck scanning.
Eg.
Debug: [easyhttp] [20] GET to https://api.roonlabs.net/audioanalysis/1/analysis/d4929cb27ca4053c1fc9e94a6bc5aaab38df2938?format=json&getSpectrogram=False&hexContentHash=True& returned after 241 ms, status code: 404
09/12 17:06:50 Trace: [analysis] Track Blues Company - Songs With No Words - The Hideaway/Peter Gunn Theme was not found in AudioAnalysis Service, continuing with analysis...
09/12 17:06:50 Trace: [analysis] analyzing trackid=10335538 url=P:\Music\Blues Company\Songs with No Words (2022)\10. The Hideaway _ Peter Gunn Theme (Live).mp3
Feel free to close this issue, thanks for your help!.
Thanks for the advice. I was hoping that the hung analysis was why the waveform progress bar wasn’t appearing on some of my displays, but now that it has stopped analyzing, I see it wasn’t the underlying issue after all.
Glad to hear that it is all working now as expected.
The analysis process is not quite as solid as one would like, but it gets there usually within a reboot or two.
