What kind of performance/speed issue are you experiencing?
· Can't connect to search or search takes a long time to complete
Please try to reboot your Roon Server
· Yes, rebooting helps, but the issue returns after some time
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?
· I only have one Roon remote to test with
Please try to restart your Roon Remote (controller) app
· No, the issue is still the same even after a restart
What is the operating system of your Roon Remote (controller)?
· Windows
Reinstall Windows/MacOS Roon Remote App
· No, I am still having the issue even after reinstalling
Router Domain Name System (DNS) change
· I was able to change my router's DNS servers but it did not help
What is the operating system of your Roon Server host machine?
· Prebuilt Branded Roon Server (SonicTransporter, Innous, Merging...)
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Hi @Nathan_Freedenberg, thank you for the timestamp. We pulled the logs and went through them.
Roon Server itself did not crash. It last started on August 30 at 5:40 PM and has been running continuously ever since, straight through the time you reported. There are no restarts anywhere in the logs, and at 12:29 PM the server was idle and healthy.
What the server saw at that moment is your Windows machine at 192.168.86.57 going quiet:
Two separate connections to two separate processes on that PC, both gone within the same second, and five reconnection attempts over the next minute all refused. From the server side we cannot tell the difference between the application closing and the machine dropping off the network, so we need your help narrowing that down.
When it happens, what do you actually see on the Windows PC?
Does the Roon window disappear entirely, so the app is gone from the taskbar and you have to launch it again?
Does the window stay open but go blank or show “Waiting for your Roon Server”?
Or does the whole PC become unresponsive, sleep, or reboot?
Those three point in completely different directions, so please describe it as precisely as you can.
Two things that would help us either way. Please open Event Viewer on that machine, go to Windows Logs, then Application, and check for an Application Error or .NET Runtime entry around 12:29 PM on September 6. If Roon crashed, Windows will have recorded it.
We do see something on the server side that would make browsing and search feel slow on a regular schedule, and we will come back to that once we know what is happening on the Windows machine.
When the player “crashes,” the sound stops. The “song” is playing; I see the thingie showing the song is playing moving in the Roon desktop app, yet there is no sound. To continue, I need to reboot the Roon Server on the Sonic Transporter i5. This happens about every 4 hours or so. I pretty much only use Roon to play local files off my NAS.
Hi @Nathan_Freedenberg, that description was the missing piece. We went back through the logs looking for it specifically and found it.
It is not a crash. From 30 August:
08/30 11:01:16 Failed to prepare Bluesound NODE 2 in 15000ms. Giving up
08/30 11:01:16 failed to setup any endpoints..giving up
08/30 11:01:16 Track Stopped Due to Error
08/30 11:01:16 [zone Gnat-Node] _Advance (Track)
Roon asks the NODE 2 to get ready, waits fifteen seconds, gets no answer, marks the track failed and moves to the next one. That repeats five times over about eighty seconds. The queue keeps advancing and the display keeps moving, and no audio is ever sent, because the NODE never got ready. Four episodes in your logs: 12 July, 18 July, 16 August and 30 August.
The NODE’s network path looks like the cause. Across 2,161 round trip measurements the typical figure is 2.4 ms, but the worst is 189 ms and the top one percent are above 38 ms. There are also 51 occasions where Roon could not reach it at all, reporting “no route to host”. Those spikes do not happen on a wired connection.
Please tell us how the NODE 2 is connected, and please put it on an Ethernet cable and leave it that way for a few days. If it has been on Wi-Fi, that alone is the most likely fix. Let us know if it happens again, and roughly when.
Circling back on this, were you able to try the Ethernet connection we asked about for the Bluesound NODE 2 and see whether the playback stops are still happening? If it is still on Wi-Fi, please move it to a wired connection and leave it there for a few days, since that network path looked like the likeliest cause; our Networking Best Practices guide may help while you check the setup. When you have a moment, let us know how it behaves and roughly when the next event occurs.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
If you can’t hardwire the NODE 2, another option is to use a mesh network and run Ethernet from a mesh satellite to the unit, which should give it a bit more stability. Let us know if you go down that path and if that changes its behavior.
This thread will close shortly for housekeeping without any OP response so we wanted to provide a clear path forward:
First off, you can always create a topic thread in the general Roon Software Discussion category, where it won’t be subject to a topic timer and will remain open for public comment. Soliciting the help of other users with this network topology should give you a pretty technically precise menu of options.
Secondly, you can continue to troubleshoot with our support team by reopening the thread at the link several posts above. We can provide next steps that will isolate a cause and a long-term solution that doesn’t involve you omitting or removing any of your audio endpoints. The software should accommodate your setup, full stop.