Post-update streaming issues with high-res Qobuz tracks on GMKtek G10 N97 (ref#7QROJM)

Support
1

What best describes your playback issue?

· Music doesn't start when I press "Play"

What type of Zone is affected by this problem?

· *Network Zones* are affected.

Is the affected network Zone connected with Ethernet or WiFi?

· Ethernet

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?

· *Only streaming* music is affected.

Please select the streaming service(s) with which you're encountering playback problems.

· Qobuz

Have you tried logging out and back in again to your streaming service in Roon Settings?

· Logging out and back in had no impact, the issue remains

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

· Two days ago

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

· GMKtek N97, G10 Ryzen NUC

Describe the issue

I'm using the GMKtek G10 N97 Ryzen NUC as my Roon Rock Core. Worked perfect before the update. Installed the latest update (2.65, build 1653) and now I can't stream anything above 44kHz. Local music plays fine, up to DSD512. I've logged out and back into Qobuz, stopped, restarted, and rebooted the NUC with no success.

Describe your network setup

AT&T Router > Ruckus ICX7150 switch > NUC / ICX7150 > transport

2

Have you checked in settings: Qobuz what your streaming preferences are set to?

It might have reset somehow to only 44.1 max.

1 Like
3

Hi @Everett_Spain,

Thanks for the update. Since logging out and back into Qobuz did not change anything, the next thing we want to rule out is the Qobuz streaming preference inside Roon.

Please check Settings > Services > Qobuz and confirm whether the streaming quality is still set above 44.1 kHz. If it has been reset, that would explain why high-resolution Qobuz playback stopped after the update, while local files on the GMKtek G10 N97 continue to play normally.

You can also try to clear out the Qobuz cache:

  • Stop Roon Server from running in the Web UI
  • Find and open your RoonServer database
  • Navigate to RoonServer/Cache
  • Move the contents of the /Cache folder elsewhere, like your desktop
  • Try restarting Roon Server via the WebUI and verify if the issue still occurs

Please let us know what you find there, and we’ll go from there.

1 Like
4

  1. Verified the streaming quality in Qobuz was set to Hi-Res 24-bit / up to 192kHz (was already set)

  2. Stopped Roon Server

  3. Under Library (Mac) I found a Roon and RoonServer folder. Both had items in Cache so I removed them into a folder on my desktop.

  4. Started the Roon Server

    Weird result - I can still stream any 44kHz file, won’t play 48kHz streams, plays 88kHz, and nothing above that - 96 & 192kHz steams will not play.

5

I have and still no luck

6

Hey @Everett_Spain,

Thanks for the updates! From a fresh Roon Server diagnostic report, we see a recurring pattern throughout every session is the RAATServer at 192.168.1.112:9200 losing its connection and failing to reconnect on the first several attempts:

Warn: [rnet/RnetJsonClient] failed to connect Connection refused
Trace: [raatserver] client connection failed. Retrying in 500ms/750ms/1125ms...

This happens at least a dozen times across the logs, always recovering eventually, but it’s a symptom of instability between the NUC and the RAATServer endpoint.

We’re also seeing Qobuz tracks failing with:

Warn: [qobuz/media] could not get playback info for 202:0:38739329:
Result[Status=NotAvailable, ErrorText=No streaming URL returned]

And more recently, in the newest build 1653 session (April 30), Roon is flagging multiple Qobuz streams as having insufficient download bandwidth for the file’s minimum requirement:

Warn: FTMSI-B-OE qo/2AEF39E4: poor connection kbps:1514.0 (min:3110.0)
Warn: FTMSI-B-OE qo/294B4C86: poor connection kbps:2844.0 (min:3503.0)
Warn: FTMSI-B-OE qo/D40DBBAD: poor connection kbps:1532.0 (min:3296.0)
Warn: FTMSI-B-OE qo/9061C6CF: poor connection kbps:1815.0 (min:3584.0)

These are hi-res files (96kHz FLAC typically requires ~2,000–4,000 kbps from Qobuz; 192kHz needs ~6,000–9,000 kbps). The NUC is getting 800–2,800 kbps on these, well below minimums. Importantly, one warning even shows a 192kHz stream needing 7,090 kbps but only getting 6,711 kbps.

Several 96kHz streams start, buffer to 34%, then stop prematurely, not because the endpoint fails, but because the buffer never fully fills or the download speed can’t keep up with playback demand. This matches the bandwidth warning pattern.

One telling entry shows a 192kHz stream starting with the NUC itself downloading it at a reported poor connection kbps:1939.0 (min:2853.0)

For a next step in troubleshooting, play a 96kHz Qobuz track directly via the Qobuz desktop app on a separate machine on the same network. Does it play? This isolates whether the issue is Qobuz delivery to your ISP generally, or specific to Roon’s streaming path on the NUC.

7

WOW…really appreciate this feedback but I’m wondering if your findings were a result of me having the NUC disconnected from the network and me installing Roon Server on my Mac to rule out the NUC as the issue? The entire chain; with the NUC, has been running smooth a few days so I’d be really interested in the results of you checking my network traffic

1 Like
8

.112 is my iPad which I use as a remote for playback. Hopefully what you were seeing was a result of me reverse engineering my network to track down the issue, so over the past few days I’ve had Roon server running on multiple devices, trying multiple endpoints, network switches, cables, etc. I think its all pretty stable now and there shouldn’t be any bottlenecks or throttling anywhere.

9

Hey @Everett_Spain,

Thanks for the updates and additional information! That could certainly be the case. A fresh diagnostic report from your Roon Server didn’t show any poor connections or Qobuz failures, so if things are running smoothly now, I think it’s time to sit back and enjoy the tunes! :musical_notes::drum:

That said, if you run into any additional hiccups or questions, we’re here to help. :+1:

10

Sweet. Really appreciate the help.

1 Like
11

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