Music will not play and skips tracks after completing update on 1/30/26 . On OS Version 2.1 (build 271) and Roon Version 2.58 (build 1608).
This occurs when I power off my DAC. After powering DAC on, Roon does not play music. In order for playback to return on Roon I must reboot my Nucleus One.
Gustard R30 DAC connected via USB to FiiO SR11 Streamer using Wifi on the same network as the Roon Nucleus One.
When powering on the DAC and playing tracks from the Roon app it just skips the tracks without any error message. The tracks show in the queue as skipped items and continues to skip every upcoming track until the stop button is selected in the Roon app. This is only resolved by restarting the Roon Nucleus One. Can reproduce issue at any given time by turning the DAC off.
Tested power cycling DAC, no change
Tested power cycling streamer, no change
Power cycling Roon Nucleus One, fixed issue but needs to be done everytime DAC is turned off
Therefore every time I turn on my stereo system I need to reboot my Roon Nucleus One. This was not occurring prior to the Roon update and couple power my stereo off/on without issue.
Does the issue happen with local library music, streaming service music, or both?
· *Both streaming and local* *library* music are affected.
Do you encounter any playback errors with the "System Output" Zone?
· The System Output has *no problem*, it's only my other Zone.
How is the affected Zone connected to your RoonServer machine?
· Cable (USB, HDMI, SPDIF, etc.)
Is your device connected directly to the Roon Server via cable or over the network, or is it chained through another device (such as a streamer, Roon Bridge, or Roon Remote)?
· It is connected through a different device (e.g Rasberry Pi)
Does the device play audio from another source when using the same connection?
· The device has no problems with another audio source
Have you checked that Roon is whitelisted in any firewalls?
· I've checked the firewall and the issue remains
If the device has multiple output options, do the other options work as expected?
· Only one output type is affected while the other output type works as expected
Is the device using the latest firmware as per the manufacturer?
· Firmware is up-to-date but the issue remains
Do you have an approximate timestamp of when the issue last occurred?
· The issue is current. It began about a week ago.
What are the make and model of the affected audio device(s) and the connection type?
· Luxman D-10X and NT-07 linked by USB (SoTM). NT-07 linked to network via switch and to server via USB. NUC linked to network via switch and to NT by USB.
Describe the issue
The Roon output from one of my three end points (Luxman D10X linked to a Luxman NT-07) has recently ceased to work unless and until I turn off my Roon server at the mains and reboot it. It then plays successfully until the next session.
All has worked fine for nigh on two years. I think that the difficulty began after the latest update was downloaded, but I am not certain about that. No files play through the Luxman via Roon, though other sources operate perfectly through it.
The server (a NUC) is connected via a network switch to the NT-07 and by a USB.
Describe your network setup
Sky router connected by LAN to switch (SoTM) and by LAN to NUC and Luxman NT-07
Thank you for the detailed description — that helps a lot and clearly explains the behavior you’re seeing.
The one critical piece we’re still missing to move this forward is a timestamp.
Could you please reproduce the issue once more and then share:
The exact local date and time when you power the DAC back on and Roon starts skipping tracks
(for example: Feb 2 at 19:42 local time)
That timestamp allows us to pull the corresponding diagnostic snapshot from your Nucleus One and see exactly why playback enters the skip state after the DAC power cycle.
Once we have that, we can continue the investigation.
Based on your description and our diagnostic reports, it appears that your system is currently set up with two parallel connections: the Luxman NT-07 via Network (RAAT) and the DX-10 via a direct USB connection to the Roon Server.
To ensure the signal path is correct and avoid conflicts, could you please try the following test configuration?
Disconnect USB from Server: Unplug any USB cables connecting the DX-10 (or NT-07) directly to your Roon Server/Core.
Use Network Only: Ensure the NT-07 is connected to your network (Ethernet or Wi-Fi).
Transport to DAC: Connect the NT-07 directly to the DX-10 (using USB or digital coax/optical).
The chain should look like this:
Roon Server —(Network)—> NT-07 —(Digital Audio)—> DX-10
Please let us know if playback functions correctly with this specific chain.
Is the affected network Zone connected with Ethernet or WiFi?
· Ethernet
Does the issue affect all file formats?
· The issue affects *multiple/all* file formats.
Does the issue happen with local library music, streaming service music, or both?
· *Both streaming and local* *library* music are affected.
Do you encounter any playback errors with the "System Output" Zone?
· The System Output has *no problem*, it's only my other Zone.
How is the affected Zone connected to your RoonServer machine?
· Network - Ethernet
Which network audio protocol is the Zone using with Roon?
· RoonReady
Does the device show up at all in Roon Settings -> Audio?
· Yes, it shows up there, but it isn't Enabled
Does the "Enable" button unlock the Zone?
· I pressed Enable, but the Zone remains disabled
Does the device play audio from another source when using the same connection?
· The device has no problems with another audio source
Have you checked that Roon is whitelisted in any firewalls?
· I've checked the firewall and the issue remains
If the device has multiple output options, do the other options work as expected?
· Only one output type is affected while the other output type works as expected
Is the device using the latest firmware as per the manufacturer?
· Firmware is up-to-date but the issue remains
Do you have an approximate timestamp of when the issue last occurred?
· Starting about a month or two ago
What are the make and model of the affected audio device(s) and the connection type?
· Roon Core: Mac mini; Endpoint: Lumin U2; via Roon Ready
Describe the issue
Dear Roon Support Team, I am reaching out to report a persistent playback failure involving my Lumin U2 streamer.
[The Problem] When attempting to play music through the Lumin U2 via Roon Ready, the system fails to initiate playback.
[Diagnostic Steps Taken] I have performed several tests to isolate the issue:
Lumin App Success: Playing music directly via the Lumin native app works perfectly, ruling out hardware or basic network failure. Other Endpoints: Roon playback works flawlessly on my other streaming amplifiers within the same ethernet network. This confirms that the issue is isolated strictly to the interaction between Roon and the Lumin U2.
[System Details] Roon Core: Mac mini M1 Endpoint: Lumin U2 Connection: Ethernet
[Community Cases] I have noticed similar cases documented on the Roon Community forum recently, which suggest a potential compatibility bug:
I would appreciate it if the technical team could investigate this handshake issue. I can provide logs if necessary to help your team diagnose the root cause. I look forward to your guidance on the next steps.
Describe your network setup
Ethernet router connecting both Roon core (Mac mini M1) and Streamer (Lumin U2)
We have enabled he diagnosic mode for your account and requested the logs from your server.
For some reason it is not reaching our servers, even after I tried re-enabling diagnostics on your account. I also ran a quick test and I was able to submit a similar report from my setup here, so something else is going on.
So we can move forward, I was hoping for now you could use the directions found here and send them to our Logs Uploader Service and let us know after, thanks!
Thanks for sharing your observations and for performing those tests.
We have reviewed the diagnostic reports from your Roon Server. We see a mix of activity: the Lumin endpoint failed to connect a few times immediately after Roon Server startup, but we also see instances where it played successfully.
To help us investigate this more precisely, could you please note the exact local time the next time this issue occurs?
Having a specific timestamp will allow us to focus on the relevant section of the logs to understand why the connection is failing intermittently.
I have removed the USB cable previously linking the server with the NT-07. The chain is now exactly as you describe. But still playback can only be obtained after rebooting the server. Playback works until I change the function of the DX-10 in any way (for example, either by using the CD transport or by switching to the TV input).
This issue started following the last software download, I think. The other endpoints on the Roon setup in other rooms continue to work with no issues.
As an alternative to Roon I have used the Luxman streaming software which is quite unaffected by changes to the function of the DX-10.
I very much appreciate your help to solve this puzzle.
Update
I’ve confirmed the issue isn’t triggered by AirPlay as previously suspected. It happens also when the system has been idle for a few hours. Even if I only use Roon, the problem recurs after a period of inactivity.
I would like to provide an additional observation that might help your engineering team pinpoint the root cause more accurately.
I’ve discovered that the playback failure consistently occurs after the Lumin has been used as an AirPlay endpoint (e.g., streaming audio from an Apple TV). When I attempt to switch back to Roon, the RAAT connection seems unable to re-establish properly, resulting in the playback errors I mentioned.
While the hardware functions fine with its native app, it appears there is a handshake priority or session-handling issue when Roon tries to “reclaim” the device from a previous AirPlay session.
I am sharing this to help you determine if there is a specific command or “keep-alive” signal within the Roon RAAT protocol that could be optimized to ensure a smoother transition between inputs on the Lumin.
We’ve analyzed the logs around 01:23 AM, and they confirm a specific RAAT handshake failure.
In the logs, we see Roon attempting to initialize the stream, waiting for a response, and then timing out with the error:
Failed to prepare LUMIN U2 in 15000ms. Giving up.
This indicates that while Roon can “see” the Lumin on the network, the return traffic required to confirm playback readiness is being blocked or dropped. This is almost always caused by one of three things.
Please perform the following steps in order:
Refresh macOS Network Permissions (Critical for M1/Sequoia)
Even if Roon seems to have permissions, macOS can sometimes silently drop “handshake” packets after an update.
Go to System Settings > Privacy & Security > Local Network.
Find Roon (and RoonServer).
Toggle the switch OFF, wait 5 seconds, and toggle it back ON.
Reboot your Mac mini.
Disable IGMP Snooping
This is a very common cause for Lumin/Roon connection drops.
Please log into your router or managed switch administration page.
Look for a setting called IGMP Snooping and set it to Disabled (OFF).
If this feature is enabled, it can aggressively filter the multicast traffic that Roon and Lumin use to communicate.
Simplify the Network Path
If you have any network switches sitting between the Mac mini and the Lumin U2:
Test: Could you temporarily bypass the switch and connect the Lumin directly to the main router (or the same upstream device as the Core)?
This will help us rule out a specific port or configuration on the switch causing the packet loss.
Please let us know the results after trying these steps.
Thanks for sharing the additional details! It sounds like you’re dealing with a classic “handshake” failure. Since your Luxman D-10X is a high-end DAC/Transport, it likely drops the USB connection entirely when you switch to CD or TV to prevent interference. Roon (running on your NUC) is losing track of that connection and, for some reason, isn’t “knocking on the door” again until the entire server reboots.
Let’s see if the below help:
Adjust the "Resync Delay"
When you switch back to the USB input on the D-10X, the NT-07 needs a moment to realize the DAC is back online. Roon might be trying to send data before the handshake is complete.
In Roon, go to Settings > Audio.
Find the Luxman NT-07/D-10X zone and click the Gear Icon > Device Setup.
Look for Resync Delay. Try setting this to 500ms or 1s (1000ms). This forces Roon to wait a beat after you hit play, giving the USB bus time to stabilize.
If possible, check the web interface or the Luxman app for the NT-07.
Look for any setting labeled "USB Keep Alive" or "Power Management." If the NT-07 thinks the D-10X is gone, it might be shutting down its own USB port.
Thank you for the detailed analysis. I have performed all the suggested steps, but unfortunately, the issue persists. Here is the updated status of my setup:
Step 1 (macOS Permissions): I have refreshed the Local Network permissions for both Roon and RoonServer as instructed and rebooted my Mac mini.
Step 2 (IGMP Snooping): I have confirmed that IGMP Snooping is already Disabled on my router settings.
Step 3 (Network Path): I have simplified the path by connecting both the Mac mini (Roon Core) and the Lumin U2 directly to the same router, bypassing any additional switches.
New Observations & Critical Comparison: The issue seems to recur after the system has been idle. I can play music successfully for a session, but the failure returns after a few hours of inactivity.
Failure Instance: I experienced the playback failure again at 13:49 – 13:51 (Local Time), Feb 4. This occurs during standard Roon Ready playback and is not limited to AirPlay.
Comparative Success: Immediately after the failure, from 13:52 – 13:55 (Local Time), Feb 4, I used the same Roon Core to play music to another streaming amplifier in my house. It worked perfectly without any issues.
This confirms that the Roon Core and the core network are functioning correctly, and the problem is specifically isolated to the Roon-Lumin U2 handshake.
Could you please re-examine the logs around these new timestamps (especially the contrast between 13:51 failure and 13:52 success) to identify why the Lumin U2 is failing to respond?
· Roon Core on a 2019 "dedicated" Mac Mini Roon server with macOS Sequoia 15. After last Roon update 2.58 Roon Core will not start properly . Says "waiting for Roon Core or try another Roon Core". Have to restart the Mac mini several times to get Roon up and go. After Roon Core seems to work music would not play, just skipping through files without any sound. Then I have to try restarting the Mac Mini server again.
Tell us about your home network
· Modell: DG2200TN (Norwegian Telenor Model) No future problems with my network. Mac Mini (Roon Core) connected direct to router with cable. Speed Network: 130 Mbps
Since you’re running macOS, the behavior you’re seeing is consistent with the newer, stricter Local Network permission controls in the recent macOS releases.
Please try the following steps:
Open macOS System Settings → Privacy & Security → Local Network
Make sure Roon and Roon Server are both enabled
Even if they are already enabled, please toggle them off and back on
Fully quit Roon Server from the macOS menu bar / task bar
Reboot your Mac
After reboot, launch Roon again and check if the devices is avaliable again.
Once these permissions are refreshed and the system restarted, your audio devices should reappear.
Please let us know if the issue persists after these steps, and we’ll continue from there.