Persistent Qobuz Integration Issues (ref#VJK6L3)

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

· Persistent Qobuz Integration Issues; Bitrate Downsampling, Missing Hi-Res Versions, and Greyed-Out Tracks

I am a long-standing Roon subscriber running a Roon Nucleus One as Core, with a Qobuz Studio subscription. I am experiencing three persistent and related issues with Qobuz integration that I want documented and escalated appropriately.

ISSUE 1: BITRATE DOWNSAMPLING — ROON DELIVERING LOWER RESOLUTION THAN QOBUZ NATIVE
Specific example: Pink Floyd, The Dark Side of the Moon is available on Qobuz at 24-bit/192kHz. When accessed directly through the Qobuz application, it streams and plays at 24/192 as expected. When accessed through Roon, the same album plays at 24/96, a full halving of the sample rate with no DSP or processing active in my signal path that would account for this.
This is not an isolated incident. I am observing a consistent pattern where Roon delivers a lower-resolution version of files that Qobuz itself serves at full resolution. There is no rate limiting, downsampling, or format conversion enabled in my Roon settings that would explain this behavior.

ISSUE 2: HI-RES VERSIONS UNAVAILABLE OR NOT SURFACED IN ROON
In addition to bitrate mismatches on albums I can find, I am also encountering albums and tracks that are listed at high resolution in the Qobuz application but appear in Roon at CD quality (16/44.1) or not at all in hi-res form. Roon appears to be surfacing a lower-resolution version as the default without offering the hi-res alternative.

ISSUE 3: TRACKS GREYED OUT OR SKIPPED IN ROON BUT AVAILABLE ON QOBUZ DIRECTLY
Certain tracks and songs that are fully available and playable in the Qobuz application are greyed out in Roon and cannot be played, or are silently skipped over during playback without explanation. These tracks are not unavailable on Qobuz , they play without issue when accessed natively through the Qobuz app. This appears to be a Roon-side failure to correctly resolve track availability from the Qobuz catalog.

I am aware this is a documented class of issue in your community forums, there are multiple active and recent threads referencing all three problems.

What I am asking for specifically:
1. Confirmation of whether these are known active bugs under remediation, or expected behavior with a configuration resolution.
2. If a configuration fix exists on my end, precise instructions to implement it.
3. If these are known integration issues between Roon and Qobuz’s API, a timeline or status update on resolution.
My system: Roon Nucleus One · Qobuz Studio subscription · Roon version (current build) · Audiobyte SuperHub as Roon Ready endpoint.

I would appreciate a substantive response rather than a referral back to the community forum.
Thank you.

Tell us about your home network

· Netgear over 2gig conne tio

Hello @campuschief,

Welcome to the community, and thank you for the highly detailed and clearly formatted report. I completely understand your need for a substantive, direct answer regarding these integration behaviors, and I can certainly provide that for you.

Here is the exact breakdown of what is happening, addressing your specific points.

Issues 1 & 2: Bitrate Mismatches and Hi-Res Versions

To answer your first question directly: Roon is not downsampling your audio. Roon will never downsample a track unless you explicitly configure it to do so via the DSP engine.

Regarding your specific example (Pink Floyd - The Dark Side of the Moon): we have tested this exact album on our end. While you may have your Qobuz streaming settings set to allow “up to 24-bit/192kHz”, Qobuz is currently serving this specific release at a maximum native resolution of 24/96.

If you open the native Qobuz desktop application, start playing this album, and look at the actual playback indicator in the bottom right corner (next to the volume slider), you will see that it is actually outputting at 24-Bit 96 kHz, not 192kHz.

Roon is simply mirroring reality. It accurately reports and plays the maximum resolution file that Qobuz’s servers are handing to the API for that specific album version. Labels frequently update, replace, or consolidate their catalogs on Qobuz, which is why a 192kHz version you remember seeing might now be replaced by a 96kHz version. Roon has no control over the files Qobuz chooses to host.

Issue 3: Tracks Greyed Out or Skipped

Unlike the bitrate behavior, tracks being fully playable in Qobuz but greyed out or skipped in Roon is a failure state that requires direct investigation. This typically happens due to cloud metadata syncing delays, regional licensing discrepancies passed uniquely through the API, or a stalled authentication token between your Nucleus One and Qobuz.

Next Steps:

  1. Navigate to Settings > Services in Roon, log out of Qobuz, and log back in. This forces a fresh token sync and often clears up “greyed out” track issues immediately.
  2. If the tracks remain unavailable or continue to skip after logging back in, please reply here with 2 to 3 specific examples (Artist - Album - Track title).
  3. Attempt to play those specific tracks, and note the exact local date and time of the attempt.

Once you provide those examples and timestamps, we can pinpoint the exact errors in your Nucleus logs and find out why Qobuz is failing to deliver those specific streams to your Roon environment.