Nucleus rev A experiencing track skipping and playback errors (ref#UY07TW)

Select your Nucleus model from the list below

· Nucleus Rev A

I'm having trouble with my Nucleus hardware

· Other

Select the option that fits best

· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices

Describe the issue

Nucleus rev A turns off and on fine and Roon on android phone or I pad instructs the nucleus ok but then skips tracks and comes back with message too. Many errors failed to play. The nucleus has run fine for years. I have unplugged all power supplies and internet connections but to no avail. Any ideas please. Bill

Good day @billcaunce !

Thanks for sharing your problem here.

Can you please provide us with the time stamp (exact time and date) of when the problem happened last time, and we’ll look precisely for it in the analytics report.

Thanks!

Regards.

The last time i tried to run roon was this morning, 12/12/2025 New Zealand time at about 8.30am

Hey @billcaunce,

Thanks for the follow-up! We were able to review a fresh diagnostic report from your Nuclues and saw that Roon reads the Tidal file and immediately marks it corrupt.

Are you only seeing this with streaming service content? We’re seeing:

Warn: [zoneplayer] couldn't play URL ... corrupt media
Warn: Track Stopped Due to Bad Media
Warn: Corrupt Media Detected

If you play the same track using the Tidal app directly, do you have any issues?

If you head to Roon Settings > Services > Tidal - what are your playback quality settings set to?

Lastly, lets see if clearing your Tidal Cache may help:

  • Stop Roon Server from running in the Web UI
  • Find and open your RoonServer database
  • Navigate to RoonServer/Cache
  • Move the contents of the /Cache folder elsewhere, like your desktop
  • Try restarting Roon Server via the WebUI and verify if the issue still occurs

Thank you!

Hi @billcaunce,

I also recommend changing the DNS server assigned in your router to a known, reliable service. You should be able to perform this change in the router settings page under a tab labelled "DNS” or similar.

We recommend assigning Cloudflare (1.1.1.1) as the DNS service.

Let us know if this helps.

We’re going to allow this thread to auto-close due to inactivity at this time. If you require additional assistance, you can re-open the thread by simply creating a new support requestand referencing this thread URL.