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!