Core Machine (Operating system/System info/Roon build number)
Windows PC (i5 8GB RAM, gigabit nic) Windows Server 2019 + latest updated version of Roon
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Realtek on board gigabit nic, no Wifi all ethernet hard wired.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Connected to the Windows core machine - SOTM SMS200 neo which connects to an Aqua Audio Formula DAC.
Connected to an office system for remote music playback - NuForce DAC80 via USB
Description Of Issue
With either zone Qobuz will not play any music. The song playback duration bar bounces back and forth with no playback. Occasionally it will state a comment about slow response. Once it played a song when I lowered the max resolution to Redbook (16/44.1). It’s also important to note that I have no problems streaming Tidal even at high resolution to either zone.
Hello @Steven_Bonamo and thanks for the information! Have you tried signing out and back into Qobuz via Roon to see if that helps? Also, from your post I take it this issue is constant? Lastly, are you able to upload a video of the bar bouncing back and forth? Thanks!
Cant play Qobuz in Roon or my Mosaic app from dCS so something must be wrong at Qobuz.
In my case something was wrong with my endpoint a reboot fixed it.
Yes, the issue is constant, the most it played was when lowered to MP3 quality I go 1 song to play. Also, yes I signed in and out several times no change. Also I should have mentioned that the Qobuz app has no issues, woks fine. In terms of an end point, the issue occurs when playing local where no remote end point is used. Again, no issue with Tidal.
Also, seems I can’t upload a video, file format not permitted only pics. is there another way?
Hello @Steven_Bonamo, and thanks for trying to get the video up! If you still have the recording, you could upload it to YouTube and drop a link here!
Any idea or recommended troubleshooting tips? From what I’ve read and what I’ve troubleshot, there seems to be bug(s) with Qobuz integration with Roon. Again, Tidal works perfectly so there is no bandwidth problem, no connectivity problem with DNS servers, etc. Frustrating that I’m paying for a service that I can’t even use via Roon.
Hello @Steven_Bonamo, I do have some items for you to try:
- I’d still like to show a video of the playback bouncing back and forth, did you get a chance to upload a copy of this?
- Do you have a screenshot of the loading slowly error you’re seeing?
- Can you grab a screenshot of a speed test from https://www.speedtest.net/ next time this issue occurs?
- Have you tried playing to the system output of your Windows core? Do you have the same issue there?
The loading slowly error no longer occurs and only happened 1-2x. Speed test attached, ~100Mbps down / ~10Mbps up plenty of bandwidth.
The bouncing back and firth is as simple as stated, the song playback duration window has a blue light bouncing from left to right, surely I can’t be the only person to have experienced this visual which is part of Roon’s program? Also, I have tried playing to the system playing Roon’s core and on my local machine. I’ve tried playing from several devices, a notebook and my desktop, same result. Also, as a reminder, Tidal streams high res MQA instantly upon picking any track.
I spent the last several hours combing through Roon log files and others who had the exact same issue as I did - can’t play Qobuz but can play Tidal via ROON, high res or not, local or remote core. Net is - Qobuz via ROON does not play well with IPv6. I see others had the same problem and several resolved the same way - disable IPv6. Also, while others disabled IPv6 at the router it is not necessary. As long as IPv6 is disabled (allowing IPv4 only) at the core no issues occur. For others who subscribe to ROON and Qobuz with streaming issues I highly recommend you broadcast this as a first step rather than asking for spurious information, might save a ton of customers’ time and frustration.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.