Playback was interrupted because a track failed to load (ref#93HG8G)

What best describes your playback issue?

· The queue is skipping tracks

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Both streaming and local* *library* music are affected.

Do you encounter any playback errors with the "System Output" Zone?

· The System Output has the same problem as my other Zone.

Do you have a complex network setup?

· Both the device and RoonServer are connecting to a *single router*

Please try rebooting your router.

· No, I'm still having trouble

Do you have an approximate timestamp of when the issue last occurred?

· I downloaded the update that became available last week on Friday April 3. When I turned my DAC back on the morning of April 4, nothing would play. Nothing in my system changed except for the update. Another update has become available this evening April 6, but I have not downloaded it in case that would prevent diagnosis of the problem.

What are the make and model of the affected audio device(s) and the connection type?

· See above

Describe the issue

The Roon update that came last week (between April 1 and April 4) has made it impossible to play anything. AI reports that many Roon users are having this issue. Nothing changed in my setup after that update, but when I turned on my DAC the next day, nothing would play - instead I get "Playback was interrupted because a track failed to load" and "too many failures, stopping playback." This affects both tracks loaded onto my Roon Nucleus and tracks streamed via Qobuz

Audio components for streaming and CD play - hardwired:
• Netgear DOCSIS 3.1 Gigabit Cable Modem
• Netgear R8000 Nighthawk X6 AC3200 Tri-band Gigabit Router
• Roon Nucleus 2-T-2 purchased December 2020 from Roon
• Benchmark DAC3L
• Benchmark AHB2 amplifier
• PSB Image T6 tower speaker pair
• SVSound SB4000 subwoofer
• Panasonic DP-UB9000 DVD/CD player
(Also have for TV but not used for audio streaming/CD play
• Yamaha RX-A6A AV Receiver
• LG OLED65 B6P flatscreen TV
• Various PSB surround speakers)
[NOTE: neither single selected tracks or multiple selected tracks will play over this setup. And I cannot test whether tracks will play over Signal Path, because tracks are skipped too quickly for that to be available)

Audio components for streaming - on network via Wifi
* Roon Nucleus is also connected to network and Windows 11 PC via Wifi
* Audioengine HD3 speakers connected to PC
[NOTE: Roon usuallyl will not play any tracks using the Audioengine HD3 zone, but if multiple tracks are selected for play once in a while it will skip one track but play the second track. Weird.)

Audio system connections for streaming (and playing CDs)
• Cat 8 Ethernet from modem to router
• Cat 8 Ethernet from router to Roon Nucleus
• USB cable from USB out on Roon Nucleus to USB in on Benchmark DAC
• Optical digital cable from digital out on DVD/CD player to optical digital input D1 on DAC
• XLR cables from L/R XLR outs of DAC to L/R XLR ins of AHB2 amplifier
• Two RCA cables from L/R outs of DAC to L/R ins of my subwoofer
• Two SVS speaker cables (I supply) from channel 1 and channel 2 outs of AHB2 amplifier to PSB front floor tower speakers L and R

Describe your network setup

See above

Hi @David_Taylor,

Thank you for your patience awaiting a response and we’re sorry to hear you’re affected by these issues.

The latest Roon release was a hotfix. It contained a patch for an ongoing issue with the Qobuz API’s main content delivery network (Akamai). This ongoing issue prevents the Qobuz API from actually delivering data when Roon has started playback on certain Qobuz tracks. This only affects some of the Qobuz catalog, so not all tracks fail. Before the hotfix, failing Qobuz tracks were loading interminably, stuck at 0:00. Roon build 1646, the hotfix, included a chance that prevented these tracks from interminably loading. This means when a Qobuz track fails to actually deliver data during playback, it will show the error you’re receiving.

Looking through logs, we see a large number of these failures with Qobuz tracks. In each case we examined, dating back to April 4, all of these tracks were failing for the reason mentioned above. Most of these tracks seem to be from the same few Qobuz albums, so it makes sense that they’d all be affected.

The Qobuz team is working closely with Roon to resolve this problem. We will post updates here as they become available from our developers:

You mentioned local library tracks are also failing, but we haven’t seen an example in logs. Can you please share the name of a local library track that failed for us to pinpoint the event? It likely has a separate underlying cause from the Qobuz failures.

Zooming out: most of these failures are with a Zone named Benchmark DAC. Please ensure this Zone has USB 2.0 enabled, since this has caused issues in previous threads.

We’ll watch for your reply. Thank you!

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