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?
· No but I can get that later on when I return home
What are the make and model of the affected audio device(s) and the connection type?
· Qutest DAC connected via USB to my NAS
Describe the issue
When I stream from Qobuz in better than CD quality (or even sometimes in CD quality), the music will stop playing and will go to the next track. Roon has already suggested I simplify my network configuration; my question is - how do I bind the Room service to a network port so that network traffic only goes through that device?
Describe your network setup
I have 2 subnets tied to 2 network ports and 3 VPN clients that restrict traffic to their own subnets
Hi @Jason_Adriaanse,
Thanks for writing in to ask about this issue.
Unfortunately the only way to do this is to have only the network interface you want to use active when you start up Roon. After Roon starts and locks to that network interface you can turn the others back on and use them normally. Please let us know if you have any further questions about this!
I jest setup another endpoint running roon bridge, connected the Qutest DAC to that and started playing a hi-res file from Qobuz. I get the same skipping error.
I managed to setup up a container and run the roon server in that. This has simplified my network setup, only one subnet is used and I can manage the resources more efficiently.
Qobuz is still skipping to the next track, it just did it.
The Chinese time now is 14.25 on the 4th Feb if you guys want to take a look.
This used to work perfectly so something has changed.
Sorry to hear your issues persist. Unfortunately, we’re not able to support Roon running in a docker environment at this time, nor anything within a VPN.
Roon will only function across a single subnet as well. All of this said, we were able to review a fresh diagnostic report from your server, and see playback failures due to poor network bandwidth, for example:
Warn: [Worker (4)] [Qutest] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
Warn: [Broker:Transport] [zone Qutest] Track Stopped Due to Slow Media
If you can, I’d test out simplifying your network setup as much as possible, with a direct ethernet connection from your server directly to your router. It may also help to test out changing the DNS server you’re using as well - we have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let me know if it helps?
In order to continue providing you support, we’ll need you to disable any VPNs and move your server out of a docker environment. Otherwise, we can move your thread over to the Tinkering section, where others who use similar setups may be able to offer additional insight.
I have 2 subnets 192.168.22.0 and 192.168.23.0 connected with ethernet cable to 2 routers from the 2 ethernet ports at the back of my NAS. Both these subnets have DNS 1.1.1.1 set. The 22 subnet is the one that goes directly to my ISPs router so I am trying to get roon server running on that … without much luck, it is using the 23 subnet
So as a solution I have moved over to the roon server running in the docker container which has only one subnet (the 22) set up and lo and behold it is working fine, Qobuz hi-res does not skip at all.
I am still trying to find out why the 23 router is causing an issue, it is running an OpenWRT and it is not stressed at all.
For the moment I am happy, things are working as they should be.
I think you might want to move this thread to the tinkering section
Ok, I think I have finally solved the problem, I now have running roon server running natively on the NAS, not in a container.
As mentioned above, I have 2 subnets 192.168.22.0 and 192.168.23.0. Those subnets are running on 2 ethernet ports, enp5s0 and enp6s0. Originally 22 was connected to enp6s0 and 23 was connected to enp5s0, I have swapped them round so that 22 connects to enp5s0 and 23 connects to enp6s0 and everything seems to be fine.