Things were working fine for a day or two, but now I’m experiencing the same dropouts again! It’s happened today on both systems, using 3 different remotes (Win11 laptop, Win11 desktop, iPhone, all running the early access apps), two different DACs and two different streamers. This leads me to believe the problem lies in the Nucleus. Sitting at my desktop I’ve had at least 5 disconnects in the past hour. It happens whether I’m streaming from Tidal or accessing music on the local storage (SSD on the Nucleus). Since Roon has been running just fine for years with much of the same gear I’m running now, and I’ve made no changes to my setup for several months, it seems to me that you folks have royally screwed up the Roon software with some recent update. If this issue can’t be resolved Roon will no longer be a viable option for me.
Hi @Michael_Teresko,
I understand you’ve been waiting a long time for a response and our sincere apologies for the lapse. To move forward with this case, we need to investigate RoonServer logs from the Nucleus One itself. The unit has so far not responded to our requests to upload logs automatically on startup. Unfortunately, the previous logset you provided included only Roon logs from a remote, which won’t contain information about audio transport and Zone-level failures that are key to understanding what’s happening.
Please use the same directions found here to navigate to the Nucleus One database. Make sure you are accessing the RoonServer folder within the Nucleus One - there appear to be two inactive RoonServer instances installed on PCs in this environment, so it’s crucial we see the Nucleus logs You can use thisFile Uploader to securely upload the logs folder within the Nucleus One’s database folder.
Reviewing this thread, we don’t have a sufficient picture of the network topology to ascertain if multicast forwarding is a vulnerability. Silent background updates to network firmware can adjust this delicate handling and interfere with RAAT device discovery or audio transport.
Are you using a mesh network? Do you have multiple routers or any managed switches? The more information you can provide, the more quickly we’ll be able to determine what’s wrong and whether it relates to any known Roon issues.
Thank you for your patience once again and we’ll await your response.
Logs are uploaded. I do not have a mesh network, only one router and 2 unmanaged switches.
Hey @Michael_Teresko,
Thanks for the update and for sending Nucleus logs over!
We can see a few issues occurring that are stopping playback, one example being:
Warn: [Red] [zoneplayer/raat] failed to sync sender clock to endpointHolo Audio Red (): Sooloos.Broker.Transport.ClockSyncResult
Warn: [Red] [zoneplayer/raat] failed to sync clocks with any endpoints..giving up
Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposedThis means the RAAT protocol could not synchronize the audio clock between your Nucleus and the endpoint (Holo Audio Red). When RAAT cannot achieve stable clock sync, it aborts playback immediately.
Other log sections show repeated accessTimeOut:True events in the file cache system. These indicate the Core is experiencing intermittent stalls fetching data, which often correlates with network jitter affecting RAAT too.
Could you check/test:
Check Roon → Settings → Audio → Device Setup (Holo Red)
Ensure:
- “Resync Delay” ≥ 100 ms
- “Clock Master Priority” left default
- “Exclusive Mode” = ON
Apologies if I’ve glazed over this - have you tested out using different USB cables and ports as well?
I’ve set the resync delay to 100 ms on both streaming devices. Clock Master Priority was set to default already. Exclusive Mode did not seem to be an option that I could see. There are no USB cables in use when using Roon. I do use a USB cable to connect between my desktop PC and the Soekris DAC which I use when I want to listen to audio direct from the computer. The streaming devices are ethernet wired through unmanaged switches to the router. The streamers use AES/EBU cable to connect to the DACs.
For whatever reason, I’ve not experienced any dropout issues for the past couple of days. The problem with the app crashing or getting very glitchy when I try to access settings is much improved also. Earlier today it was hanging up for a few seconds when I tried to make changes, but closing the app and a cold reboot cleared things up for now.
Hello @Michael_Teresko ,
Glad to hear that there has been an improvement in the behavior! Please, let us know how the system performs after further testing.
Hi @Michael_Teresko,
This thread will auto-close after another few days without any further activity from the OP, so we wanted to give you a ping to check how things performed with this system in the last week.
Please let us know the name of the track that dropped out (or an approximate timestamp) if you experienced any interruptions. We’ll keep account diagnostics enabled in the meantime so we can review logs if necessary. Thank you!
This topic was automatically closed after 2 days. New replies are no longer allowed.