It’s discussed here. In particular, the following quote explains the reasons for minimal buffering:
Audio devices must own the audio clock. Many other protocols get this wrong, including AirPlay. It’s not possible for two clocks to agree perfectly. Letting the DAC control the pace of streaming removes the need for a clock-drift-compensation mechanism that is bound to increase cost, decrease sound quality, or both.
Tight playback synchronization suitable for multi-room listening. There’s a careful line to walk here. If we demand ultra-tight (1-10us) sync, it becomes impossible to implement the system on existing/unspecialized/heterogeneous hardware platforms. We shoot to be within 1ms (and under ideal circumstances often much better), which is more than adequate for multi-room listening.
Although I see people on this thread getting trolled if they disagree with the original post and say Qobuz/Roon are working fine for them, I’ll risk the wrath and say the same. It is useful to know that some users’ systems are problem-free. That could help determine the source of the problem (meaning, the issue may be with gear, network setup, lack of patience, RTFM, etc.)
With my wired Roon ROCK and everything else Wi-Fi, I’ve never had an issue with Qobuz on Roon, and I’ve had the combination for almost two years. As with any networked product with thousands of potential hardware combinations, your experience may vary.
One of the challenges with Roon is that it is a complex environment and not comparable to casting/streaming Tidal/Qobuz/ Spotify to your speaker.
Some people want to vent and some proclaim everything is perfect and that is rarely case with something as complex as Roon.
I have very few problems in my environment and yet I was really frustrated when Roon released the new last version that broke Sonos for a lot of users. Even though I told them it was broken in the beta they could not replicate it and released it and I see the Meridian thread that is the same story.
A month without reliable music and I finally understood how everyone else felt when their Qobuz or Tidal fails all the time.
It has given me a slightly different perspective on Music services and networking.
I totally dig that there are users with no issues. There always will be. Also, I understand that there is a decent amount of complexity involved. I do digital products for 20 years on three continents for major enterprises and disrupting startups. Of course, there is complexity. But if you can’t provide the advertised services, you can’t charge the full price. Then Roon has to sell it as an experimental feature or beta version.
Also, they can’t play the “It’s not us, it’s your network” card all the time and close tickets with no solution.
There are too many issues that point to a bad implementation on the Roon side than to external network issues.
Also, there has to be a warning and communication that a standard internet/network config may fail with Roon.
Try your setup hard wired and then report back (if the core isn’t hardwired already that is). Also try the endpoints hardwired. I’ll bet anything it’s a wifi router issue - possibly even between your core and remotes. So even if you have to drape cables everywhere to test, at least you’ll be able to say if it’s the wifi router or not. Restart everything from where the internet comes in forward. I’m another that has never had any issues with Qobuz over four years (nor Tidal one I briefly had a sub). I have everything except a few endpoints (Sonos etc) hard cabled, and use separate modem, router, and main switch.
I know that it’s not what you (OP) wants to hear, but it really does sound like a network issue. Roon, by its very design, is a network-demanding piece of software. Doing as @Charles_Peterson suggests is a good way of isolating where the problems might lie.
I understand that you want Roon to work “out of the box”, but sometimes it doesn’t. And I’m afraid that the only way to get it to work is often to look closely at your network set up. Your network doesn’t need to complex or sophisticated, it just needs to be stable. I run a very basic network set up: TP Link router to Windows 10 PC and then hard wired to endpoints.
Georg don’t take it that I was saying anything besides Roon can be a complicated beast and they strongly recommend Ethernet. Roon is not transparent enough about these requirements and hide behind the best practices guides, when a user logs a ticket.
There should be a warning sign on the door saying here be dragon’s, but for those that can make it work there can be musical Nirvana at the end of the journey. Many don’t make the end due to issues with reliable networking, and for people that don’t make it there is always Tidal connect which works brilliantly (and apologies to the Qobuz users).
I’ve been using Roon with different network configurations, due to house and gear changes, for more than 5 years. First with local files only, then also with Qobuz when they launched in the US. I’ve observed two main LAN network issues that have caused trouble over that time:
Multicast/IGMP snooping: Roon relies on multicast for device discovery. IGMP snooping is a heuristic that some routers and switches use to recognize multicast groups and restrict multicast traffic to stay within those groups. Like any such heuristic that breaks the OSI layer model, its implementation in particular gear may not match the behavior of particular network uses, in particular Roon’s. I’ve found that turning off IGMP snooping in managed switches, when using them, got rid of problems with devices failing to find the Roon Core.
Bursty flooding of WiFi connections: Even a good WiFi router can drop packets when a connection through it is able to flood the channel. Applications like photo backup from phones can easily do that when talking over WiFi to a very high capacity WAN link. Roon RAAT does not buffer by design, so packet drops break streaming, with track stops and skips as a result. The only solution I know for this is to wire all Roon endpoints as well as the Roon core.
Also if you read my initial post, how should it be a network problem if albums disappear from your library. or how does a network issue makes sense that I can’t delete an album from my library sometimes, or Qobuz albums show wrong album cover art?
Far be it from me to want to stick my hand anywhere near this potential hornets’ nest, but:
when you moved the NUC, is it possible that it ended up in a different network segment, thus potentially rendering it invisible to the Mac looking for it? (I have made that mistake myself in the past)
can you browse to the NUC’s IP address from any other machine?
alternatively, can you run a network sniffer app on any other computer that will show you all devices it can see on your network and their respective IP addresses? And if it sees your Nuc, does the IP address still match with it says in your first post? Can you ping the IP address from your Mac?
Assuming it also refuses to boot if you put it back in its previous place, you may have a hardware issue with the Nucleus and should probably contact your dealer if it stays dead (leave it unplugged for a few minutes and then plug it back in and try to boot it up, to be sure). Such hardware failures are rare but like with any computer, failure rate is not zero. Putting myself in your shoes and knowing my own temper, I fully appreciate your frustration level at this point.