In Roon what does you DAC report it can support ? Your DAC doesn’t mention Linux support on their blurb so I wonder if it’s dropping to standard USB Audio Class and not Audio Class 2 which is needed for above 96/24. Do you have Qobuz configured in Roon to allow up to 192/24 as there are a few settings levels? Even so it would normally resample them down to what it can play back and not skip. Does the Roon remote give any messages like loading slowly ?
Please accept our apologies for the delayed response.
Looking through diagnostics, there are a few possibilities.
There’s a distinct possibility you’re up against a known issue in which our MQA decoder erroneously recognizes some 192/24 files as MQA, often with terminal results for a downstream DAC or DAP. While the evidence isn’t definitive, there’s an uncanny resemblance to several other situations, for example: Certain Frank Sinatra Qobuz Tracks Won't Play in Roon (Ticket In) - #11
There’s evidence that you’re experiencing some common instability in your system that we anticipate being able to improve soon with upcoming regular releases.
Do you have any issues at all with 192/24 local files? You mentioned TIDAL content doesn’t trigger this.
A meager workaround is to play these files in ARC since there is no MQA unfold stage in that app’s playback engine.
Would you mind supplying tech support the following screenshots to help our incident investigation?
Your Device Setup for this endpoint in Roon → Settings → Audio
Your signal path, including the DAC you’re using here.
Unfortunately, there’s evidence in logs that you’re facing this issue linked below in my staff post from another thread. Some high-quality Qobuz tracks are erroneously triggering our MQA decoder, breaking playback. While we’d seen supply chain issues with files in the past, in this case, we’ve already worked with Qobuz to confirm there aren’t incorrect MQA tags contained in the source material. This is a Roon bug that we’re tracking and have prioritized to implement a fix.
There’s a ticket in with senior development, and I’ll be reporting progress in the other thread. Hopefully, this will be a quick surgical fix from here as we’ve already pinned down what’s breaking. Thank you for your patience in the meantime.
Long-awaited update on this issue: we have a fix in place that should be merged into the public version within one of the upcoming releases. We’ll post here as soon as we’ve confirmed it’s in a release. Thank you for your patience!