Massive latency in Roon Small Green Computer i5

Core Machine (Operating system/System info/Roon build number)
Small Green Computer Sonic Transporter i5 with 4TB SSD music storage, version 2.8. Roon version 1.7

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Eero network with 3 eero pros.
Roon Core is hardwired to true central router (the one connected to the modem) through an English Electric Ethernet switch.

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Network player is MSB Discrete DAC with Ethernet renderer, also plugged into the English Electric router.

Description Of Issue
Hi guys, I am not sure what is going on, but small green computer thinks this is an Eero router issue.

When using Roon, very very often (like every 5-10 minutes) when I click on an artist or playlist (generally in Tidal or Qobuz because I usually stream) the loading screen just stays for 30-60 seconds and I get an error page.

Reloading sometimes solves the problem, other times I have to restart Roon Core. Additionally, when I am playing a song, and I select another song to play immediately, the current song will stop and the next song will not start.

It has gotten so bad that I am using my bluesound and blueOS instead of Roon.

I don’t understand how I could be having problems like this running one end point on a dedicated overbuilt server that is all hardwired into my network, which also is on gigabit Verizon fios. Why am I paying for Roon and $1500 dedicated servers which do nothing but run Roon Core when it doesn’t even work?

Please let me know if there is some sort of issue that I can sort out. I have updated everything, restarted everything countless times, and checked all of my cables etc…

Posting in support would be best so I’ll move it there.
I agree sounds like a network issue.
Is the eero your network modem/router or a separate one?

Eero is the router only. There is a modem from Verizon Fios that provides internet into the router.

I also use a Mesh (Orbi) router with my SGC i5. At the time the support from Netgear was terrible as I had continuous issues with dropouts. I took took SGC suggestion of placing a Trident switch after the Orbi unit and plugging my i5 and Upsampler into that switch rather than the Orbi. Voila, no more dropouts. I later added their opticalmodule and have been rock solid since.

I had a similar experience with a SGC sonicTransporter as Core connected directly to an Orbi router. I inserted a TrendNet unmanaged switch between them, problem solved.

Hi @James_Elliott,

Does this issue impact multiple Cores on the same network or are the issue specific to the SonicTransporter? I would try to temporarily host the Roon Core on another PC to see if we can narrow this down:

  • Create a Backup of your current database
  • Open Roon on the other PC you wish to try as the Core
  • Roon Settings -> General
  • Disconnect
  • On the “Choose your Core” screen, press “Use this PC”
  • If asked to Unauthorize, you can go ahead and do so. You are limited to one active Roon Core at a time but you are free to switch between them as often as you’d like.
  • Verify if the same behavior occurs on the different PC

So this was a problem when I ran core on my iMac. I bought a dedicated core thinking that it would solve the problem, and it has not…

There is a switch between the core and the router as well.

Problem is the same on my 1 year old i7 iMac. Unfortunately it feels like a network or software issue.

Hi @James_Elliott,

Thank you for testing the iMac further, can you please confirm if the issue is the same if you bypass the switch and connect directly to the router, via Ethernet or WiFi?

Is this a managed or un-managed switch?

Managed Switches

Managed switches can be very robust, but they are often designed for professional installation, so in many cases the out-of-box configuration is not right. If your switch has a “flow control” setting, please make sure that it is enabled. Also, make sure that the switch is not performing any sort of throttling that might impact communication between cores, storage, remotes, and/or audio endpoints. Finally, ensure that the switch is configured to pass multicast and broadcast traffic. If in doubt about any of this, try temporarily replacing your managed switch with a “dumb” switch to see if things improve.