Roon Core Machine
synology Nas FS3600
roon server, windows 10 on VM, 4 cores, 32 gb ram (assigned)
music database on same machine but not in the VM
the VM has its own 25Gb network port.
Networking Gear & Setup Details
div Unifi enterprise line switches and AP’s
unify next gen gateway pro
unifi USW-Pro-Aggregation
no vpn
Connected Audio Devices
roon players are some bluesound nodes, Araulic Aries G2.1 and a Sonnet. (and a pc)
Number of Tracks in Library
200.000+ tracks
Description of Issue
My background analysis got hung up and stayed for months on the same number to analyze
after some investigation i found that some of my mp3’s had a wrong bitrate reporting and / or wrong channel
for example:
04/10 23:54:39 Trace: [analysis] Track Pet Shop Boys - Please - Why Don’t We Live Together? was not found in AudioAnalysis Service, continuing with analysis…
04/10 23:54:39 Trace: [analysis] analyzing trackid=26251570 url=\10.0.3.3\music\MP3 artiest\P\Pet Shop Boys\Please\11 - Why Don’t We Live Together.mp3
04/10 23:54:39 Warn: [analysis] unsupported excn for trackid=26251570
According Roon this is a MP3 22Khz 320kbps 2 channels, length 37:58 min
According Tagscanner (my tagger) this is a MP3 22Khz 40kbps stereo length 4:44 min
Roon can’t play this track but tagscanner can play it (more media players can play it, and you can not hear sound quality different s with other tracks in the album. so the actual wave is correct.)
if i convert this track with Switch soundfile converter to a mp3 320kbps stereo the track becomes corrupt and i hear only clicks and beeps. if i open the track Adobe Audition and export to mp3 the file is good and Roon can analyze and play the track.
by the way all other tracks in this album are ripped to mp3 44.1Khz 320kbps joined stereo. i ripped them myself so the had all to be the same. i have this behavior in several albums where one track reports the wrong Khz, kbps and channel, so i think that something is corrupting the metadata.
If i see the number of posts on the background analysis is it perhaps an idea (and i don’t know if it is possible) that if the analyzer runs into an error that he analyzes the correct Khz, bitrate, channel. and write this in the metadata.
If Roon already writes in the metadata please verify that Roon is not the cause of this issues.
if you want to see this behavior your self i will hold a copy of this album for a short time so let me know if you want it. i know now the way to repair the rest of the files so for me this is no issue any more (i hope)
best regards
marco