As title says, a large number of recordings from Qobuz that are in fact 192 kHz, and shown as 192 kHz in Qobuz, are shown as 96 kHz in Roon albeit they play as 192 kHz. A couple of recent examples:
Boris Giltburg latest Rachmaninov recording from Feb 13 2026
Olga Pashchenko’s latest Mozart recording from Feb 2026
Roberta Flack “With Her Songs” from Feb 2026
Etc Etc
Thank you for highlighting this. I can confirm I have come across a handful of Qobuz albums where for a 192kHz version Roon Remote showed 96kHz.
Same issue here
Bump…same here!
Same issue here …
Nobody cares ?
This is Roon. I have over there years posted several requests and reports of faults, but never received any reaction from Roon whatsoever. I think they simply rely on the community fixing everything, although that is of course not possible (like this issue which is a technical flaw in Roon).
Roon staff only reads the supportthread not the subcategorisch
This subject probably has to do with some settings in Roon or an endpoint.
Use the support link and don’t use a subcategori and If possible a screenshot from the signalpath.
If they show as one resolution in the info but the signal path shows another resolution when playing, then the signal path is always right. The info is just metadata text that can be wrong.
This is probably an issue with the metadata Roon gets from Qobuz or something like that.
Open a proper support topic
I am experiencing the same issue. It is present with all files in Qobuz’s various 192kHz playlists:
Same problem here with all the “Lucio Battisti” 192K album:
Please people!
@Nicola_Lodeserto @Anil_Panigrahi
Open your own support request as has been highlighted by others here already like @Suedkiez .
Just tacking onto the end of this thread is NOT going to get you any traction at all!
Thank you for your cooperation.
I did. It’s here:
Chill out.
I don’t track down exactly what every user posts but do see the me too posts in threads that end up being of no help to the poster at all.
If I was any more chilled I would be horizontal 
I appreciate your dedication. Unfortunately, this appears to be a Qobuz issue, so we’ll have to wait for an update from them.
Enjoy the music,
AP
I’m sorry, I understood that the various reports were being collected in a single thread, but evidently I misunderstood. Feel free to delete my posts if you deem it appropriate.
A single thread for this kind of issue will probably be fine, but this here is not a proper Support > Get Help tech case and would not get official attention, so all the “nobody cares?” posts were misplaced. @Anil_Panigrahi created a proper case and got a reply (and some action by Roon, though they can’t do much) within a few hours.
Hi everyone,
Thank you for bringing these cases to our attention. Individual examples are useful for demonstrating the scale of the problem to Qobuz, with whom we are working to resolve this format data pollution problem affecting their catalog API. We take great pride in data integrity and don’t like seeing an otherwise high-quality source deliver problematic source format metadata.
It’s correct that Roon, ultimately, has no control over the timeline to resolution here. Some of these errors are no doubt trickling in from distributor sources and require further correction upstream of Qobuz itself. Roon’s Signal Path will always be transparent to the format delivered, by we don’t have a mechanism by which to call out the attached metadata for displaying an inaccurate sample rate. This isn’t an excuse, merely an explanation.
Qobuz is aware of the problem, but there’s obviously a need to provide some sort of forum space on the Roon side where users can continue to disseminate reports.
We will allow this thread to function in that role and mark it “ticket-in” accordingly. We’re not going to merge it into the previous thread tracking this case, since that provides a clear explanation to newcomers as to the state of the issue.
Please bring any new issues with Qobuz format discrepancies here. If you’d like a status update as to the timeline to resolution, please engage Qobuz directly here, who can provide a more accurate answer: https://www.qobuz.com/us-en/help/contact/
Thank you for your patience.