Roon app slow and glitchy after modem & router upgrade (ref#0WBK6U)

What app are you having the slowness issue with?

· Roon

What kind of performance/speed issue are you experiencing?

· Other

Please try to reboot your Roon Server

· No, the issue is still the same even immediately after a reboot

Please try to reboot your networking gear (Router/Switches/etc.)

· No, the issue is still the same even after a reboot

Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?

· No, the issue is still the same

Does the issue happen on multiple Roon Remotes (controllers) or just one?

· Issue happens on multiple remotes

Router Domain Name System (DNS) change

· I don't know how to do this

What is the operating system of your Roon Server host machine?

· Nucleus

Which model Nucleus do you have?

· Nucleus One

Timestamp of issue occurrences

· Multiple times, daily, over past several months

Describe the issue

Roon app is slow and glitchy: long to load, sometimes does not load, asks to select audio zone, drops music once it does start. Running Nucleus for 3 years and am just now having these problems (past 4-6 weeks). Nucleus hardwired to router. No other problems on any other apps. The problem seems to have coincided with a modem & router upgrade. Tried rebooting all, tried static IP address, throttled and turned off audio analysis speed (Library Settings). this last one seemed to work for a day, then back to slow and glitchy.

Describe your network setup

Xfinity, ARRIS - SURFboard S33 32 x 8 DOCSIS 3.1 Multi-Gig Cable Modem with 2.5 Gbps, TP-Link Tri-Band BE9300 WiFi 7 Router (Archer BE550), TP-Link TL-SG105, 5 Port Gigabit Unmanaged Ethernet Switch, TP-Link Long Range Outdoor Access Point (EAP225-Outdoor) – AC1200 Dual Band

Hi @Scott_Spaulding,

Thank you for your post and for your patience in awaiting a response from the team.

We’ve examined diagnostic logging from the Nucleus. Fortunately, we don’t see obvious crashes or memory pressure, and the device doesn’t show any signs of database corruption.

There are problems with device discovery. In several cases, RAAT attempts to connect with endpoints that have either failed to initialize or have dropped off of the network after their initially discovery and pairing.

Usually, this is a sign of the network handling multicast traffic in a manner Roon doesn’t expect, or some new network traffic-shaping feature is interrupting the sustained TCP connections upon which Roon relies.

This network topology indicates RAAT traffic might have to pass several hops. Where specifically among the devices that you listed have you hardwired the Nucleus? What about your network endpoints (specifically, the Naim device is the one Roon keeps losing)?

Lastly, please share a screenshot of the Nucleus webUI page here.

Thank you and we’ll await your response.

Hi @Scott_Spaulding,

We’ve not seen a response to this thread this week, but we’ll need some of the details requested in the post above in order to proceed with next steps and suggestions. Keep in mind this thread will eventually auto-close without any new responses. We’ll watch for your response in the meantime. Thank you!

Thank for your reply. To your questions:

  1. The nucleus is wired to my router.

  2. Roon keeps losing connection when the app is accessing a WiFi-connected MuSo 2nd gen and also a wired ND5XS2.

  3. Screenshot of UI page attached.