I have the “Tidal loading slowly” problem. This is an issue, I have every few months. After resetting network, wifi and other stuff randomly, the issue goes away. Now it is back :frowning: I am not an IT guy. I am into ROON because it makes listening to music easy and interesting (when it works). I have a 1000 Mbit internet connection, that works fine. All my other devices work flawlessly when running tidal directly from Tidal (Bluesound, Eversolo, Sonos). But through Roon… Not so. I am actually getting to a point, where i have had enough. This is not a new issue. It has been in the community for long time, different writers. Always, it seems, there is no solutions. The topic gets closed after inactivity. I was so stupid to buy a lifetime subscription. I feel you should actually get this problem solved. After all, it is not cheap stuff (ROON). My system consists of a 1000 Mbit internet connection, A Intel Nuc i5 16 Gb RAM, Google Nest Pro Wifi, Eversolo DMP A6 Master edition. I also have a couple of Bluesound and Sonos endpoints. What should I do?
This is an issue, I have every few months. After resetting network, wifi and other stuff randomly, the issue goes away. Now it is back
The above information, seems very detailed and probably it is your best effort in being transparent.
My problem with all of this, is that I am not an IT guy. I am into ROON because it makes listening to music easy and interesting (when it works). I have a 1000 Mbit internet connection, that works fine. All my other devices work flawlessly when running tidal directly from Tidal (Bluesound, Eversolo, Sonos). But through Roon… Not so.
I am actually getting to a point, where i have had enough. This is not a new issue. It has been in the community for long time. Always, it seems, there is no solutions. The topic gets closed after inactivity.
I was so stupid to buy a lifetime subscription. I feel you should actually get this problem solved. After all, it is not cheap stuff (ROON).
My system consists of a 1000 Mbit internet connection, A Intel Nuc i5 16 Gb RAM, Google Nest Pro Wifi, Eversolo DMP A6 Master edition. I also have a couple of Bluesound and Sonos endpoints.
What should I do?
You are by far from stupid buying a lifetime subscription
I notice you mention a NUC, i5 with 16gb ram. Are you running Roon Rock? If not, are you running Roon Server on Windows
I also see you have the Google Nest Pro WiFi network.
Do you have your internet service providers box before this?
Is it acting as your main router?
Is your Google Nest Pro in access point mode?
Are you connecting to your NUC with an ethernet cable?
Do you just have the Google Nest Pro on its own or with the extender node?
Your incoming internet speed is not the issue here, but if you could confirm how your network is setup it could highlight a possible cause.
My setup is, which may help
ISP box in modem mode
Google WiFi primary node acting as router
This connects to a 24 port switch
My other Google WiFi nodes connect to this (wired backhaul)
My Roon Rock box connects to my switch
All my Roon endpoints are on WiFi
Roon Labs is constantly working on improving the situation for its customers. If you run into an issue then opening a support request, as you did, is the right course of action.
Thx also for your questions which I will try to answer one by one:
I am running Roon Rock.
My Google Nest Wifi is connected to my ISP’s box.
I have 2 additional Google Nest Pro nodes.
Is it running in Access point mode? I dont know where to look
The NUK is connected with an ethernet cable to a passive switch connected to the Google nest pro main router.
All endpoints running wifi.
Sure would be nice, someone can see if there is a connection to the issue. On the other hand, the issue is not permanent. So the setup can work…
If your primary nodes WiFi can reach your endpoints on WiFi, I’d temporarily turn off the extender nodes.
Roon transmits a PCM stream which is a constant data stream. It needs a solid/robust network. Having multiple WiFi hops can and does cause issues with Roon.
If we temporarily simplify your network to a single WiFi transmitter and see what happens.
Hi Menzies,
Thx for your effort. You are really helping out in a way, that non IT people (like me) can understand. Everything looks the way you have shown. The setting for WPA3 is on though. Dont know if that could be a problem.
I will try turning the two nodes of tomorrow in the morning. It is rather late here (Denmark).
Thanks again! I really apreciate your effort to help!
Just an update. This morning it works fine again. Didnt do anything. The nodes are still on in the mesh network. Ergo I dont have a reference if I turn them off. These periodical problems are sooo soooooo frustrating. Given that this problem has been a topic in the community several times, I wish that Roon would offer some guideline to solving it. It is hard to comprehend that it is not linked to the way Roon works, since the endpoints work fine directly with Tidal, just not with Roon periodically.
Thanks in advance to Roon, if they would share some insight.
A hardwired ethernet connection to the internet on your RoonServer machine is the most reliable way to avoid upstream network hiccups with Tidal/Qobuz/KKBOX servers.
Hi Connor,
I have my Roon ROCK hardwired to my primary internet router. The hicups as you call them only occur on my endpoints, when streaming through Roon. When I go into my Bluesound or Eversolo app and play Tidal music, it works fine. It is only through Roon.
I think it could be some kind of trouble connected with mesh networks. I have had the same issue on a Amplifi mesh setup. Now I have a Google Nest Pro. It worked fine for a period, now it is intermittently back again. Lately I disconnected the mesh point closest to the Eversolo streamer. It seems to work better. But I need mesh points! Again: It is only via Roon I have the issue!
Outside of that, I suggest you enable multicast forwarding and IGMP snooping settings on any of the mesh nodes. Try to place the nodes strategically to avoid WiFi passing across known sources of EM interference. Roon’s high-fidelity, lossless protocols have a habit of sniffing out any packet loss that has been lingering in the intranet.
