Tracks on Wiener Philharmonika album skip during Roon playback, play fine on Qobuz (ref#Y2XDA3)

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Streaming tracks greyed out or unavailable

Tell us what's going on

· Some tracks on the Wiener Philharmonika Summer Night Concert 2026 album will not play and skip to next track through ROON but will play through Qobuz direct without any issues.

Tell us about your home network

· Sky Fiber Router

Hi @btm.band, welcome to the community.

Some tracks failing in Roon while the same album plays in Qobuz points us toward a playback or streaming-side issue rather than the album itself. To get a clearer picture, a few things would help:

  • What is your Roon Server running on, and how is it connected to your Sky Fiber Router, wired Ethernet or WiFi?
  • When a track skips, does it happen on the same songs every time, or does it vary?
  • Can you share a timestamp for one failed playback attempt, along with the track name?
For the timestamp, we’ll enable diagnostics on your account first, then the next time it happens, please note the exact local date and time and post it here with the track that skipped. That will let us review the playback path around that moment.

If you can also tell us whether any switches, mesh nodes, or powerline adapters are in the path between the Roon Server and the playback device, that would help us narrow it down further, thanks!

Hi Noris Thanks for your prompt response. The album is now playing fine (19.30hrs Greenwich Meantime 21/7/26) However, when I had the problem it was the same tracks that weren’t playing/skipping (Tracks 1, 10 & 11 on Wiener Orchestra Summer Concert 2026)

For your reference my system is SKY Fibre to house and House Router, approx. 15metres of Copper CAT5 to Music Room to TP LINK Switch, network cable to Windows 11 PC and USB Cable to Technics SU R1000.

I would welcome any advice on improvements if they are needed.

Best regards

Mark

Hey @btm.band,

Thanks for the detailed report and system description, that background was really helpful.

Good news first: I’ve been through your Roon Server logs and the issue was not with your network, PC, or Technics SU-R1000. It was a temporary problem on Qobuz’s end with three specific track files on that album.

The logs show the same three tracks failing every time, Leichte Kavallerie: Overture (track 1), Daphnis et Chloé: Suite No. 2 (track 10), and Tico-Tico no fubá (track 11), while every other track on the album played perfectly.

Each failure occurred at the exact moment Roon requested the file from Qobuz’s servers, before the audio reached your equipment. When a genuine network, cabling, or USB fault is involved, the failures land on random tracks; seeing the same three fail while their neighbours play flawlessly is the signature of a server-side content glitch.

Qobuz has since re-provisioned those files, which is why the album now plays through without issue.

On your setup specifically, the logs are very healthy. Your buffers stayed at 100% throughout, and Roon’s upsampling to DSD256 ran comfortably in real time, so your SKY fibre → CAT5 → TP-Link switch → PC → Technics chain is coping well with hi-res streaming. There’s nothing you need to change.

If you ever hit a track that won’t play again, the quickest check is to try that same track in the Qobuz desktop or mobile app. If it also fails there, it’s confirmed to be on Qobuz’s side and worth reporting to them directly, there’s nothing to fix locally.

Within Roon, skipping past the track and back, or removing and re-adding it to the queue, will pull a fresh copy from Qobuz.

Do let us know if anything similar crops up. :raising_hands:

Hi @btm.band,

You are possibly also experiencing a known issue between Qobuz and Akamai, the content delivery network serving the Qobuz API for certain regions.

Some tracks deliver 0-byte streams instead of the expected data; this won’t affect Qobuz itself, since it doesn’t rely on the Qobuz API and instead uses their own native architecture. The issue only affects app that rely on the Qobuz API (like Roon). Our team is in direct contact with Qobuz, who is working with Akamai to resolve this.

You can track updates here as our team receives them from Qobuz:

Thank you for your patience.