Roon thinks some of my audio files are corrupt, but not always

Roon Server Machine

sonicTransporter 2.8, Roon App on Android phone

Flac files on LaCie d2 4TB USB 3.0 connected by USB to sonicTransporter

Networking Gear & Setup Details

Currently router connected to dCS Network Bridge through ethernet, dual AES/EBU to dCS Scarletti DAC

Connected Audio Devices

Number of Tracks in Library

About 8,000 tracks

Description of Issue

This configuration has been functional for some time. I’d stopped using it for a while, and when starting up again, everything seemed to work. Then Roon started showing all of my files as corrupt, and wouldn’t play. I rebooted the sonicTransporter, and forced a rescan in the settings storage on the drive. That seemed to fix it, but sometime later it showed all of my files as corrupt again, and wouldn’t play. I repeated the previous step, and now it plays, but it shows a corrupt message besides some (no longer all) albums, but still plays them.

I checked the drive, and it seems healthy. The files that Roon sometimes thinks are corrupt haven’t changed.

I searched online and found posts about forcing Roon to reanalyze files through the app, but the answers don’t seem to apply anymore. Can you tell me how to force Roon to reanalyze all files with the current app? I understand that that’s not the same as forcing a rescan.

Thanks,
Daniel

I’ve had a similar experience during all the recent Build 1354 problems.
I selected a well-known & often played album and it wouldn’t play, or started skipping.
I tried playing it again from the beginning (after Roon had frozen & restarted itself again) and all the files were showing as corrupt.
One day later, they were all ok again & playable.
Very frustrating.

Just to follow up, I’ve been listening successfully to playlists for a couple of hours, and then I get “Playback was interrupted because of a corrupt audio file. Too many failures. Stopping playback.” I rebooted the roon server, and forced a rescan in System->Storage. Then roon will play again the supposedly corrupt files.

I don’t believe that these files are corrupt. They haven’t changed from when I added them to the USB drive. It seems to be a common issue on the forum, and if the issue is resolved it never seems to be because of corrupt files. There should be a FAQ on this, but I couldn’t find one.

I recall that I had this issue a number of years ago, and it went away when I forced Roon to reanalyze the files. But I don’t know how to do that anymore, I don’t see it as an option in the current app. Help would be appreciated.

Thanks,
Daniel

1 Like

Around the time of new update I lost Arc, then my controller. And certain songs in my library began to drop out and play with static. At first I thought it might be Qobuz. Any idea what could do this, how to confirm what specific files may be corrupted or how to fix them? Thanks.

While waiting for a response to my support ticket submitted on Dec 8, I tried deleting and reinstalling the roon server. I created a new playlist with about 94 tracks, and hit “play now”. Everything seemed to work, and I paused playing in the middle of a track. Sometime later I tried to resume playing, and I got the dreaded “Playback was interrupted because of a corrupt audio file. Too many failures. Stopping playback.” Now many tracks were displayed with a red corrupt label, whereas before there had been no red label.

I rebooted the roon server, and forced a rescan in System->Storage. Then roon plays the “corrupt” files again. Until …

You should try installing RoonServer on a different PC and see if you get the same issues. it could very well be a flaky hardware issue.

This does not sound like a hardware issue.

@Daniel_Parker2 You say in your original post you are running Sonicorbiter OS v2.8 but based on your email to me you are running 2.7. You need to update to the latest version of Sonicorbiter OS for Roon to work correctly. Follow the update instruction on the sonicorbiter.com FAQ.

If you are still having issues with Roon we have a detailed Roon troubleshooting section also on the sonicorbiter.com FAQ

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