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 the same problem as my other Zone.
Do you have a complex network setup?
· Both the device and RoonServer are connecting to a *single router*
Please try rebooting your router.
· No, I'm still having trouble
What are the make and model of the affected audio device(s) and the connection type?
· Apple MacBook Pro (M1pro MacOS 15.01) connected to a SMSL DAC (raw-mda1) via usb
Describe the issue
I suspect a problem with Roon client (2.0 build 1470) running on Apple Silicon (M1 Pro) under MacOs Sequoia 15.0.1. Roon Core also runs (2.0/1470) Problem description: after some minutes of playback the system is no longer able to skip to the next title. It skips all titles until it stops with an error message that too many errors occurred. After quitting Roon client and starting it again everything works for some minutes until the cycle repeats. Important observation: When the error occurs I can still use the Roon core with other devices without problems.
Describe your network setup
Roon Rock running on Intel Nuc. Network ist Ethernet based with FritzBox 7590 as Router
Thank you for your report. The particular class of error you’ve indicated, “Too Many Errors,” indicates an issue between RAATServer and the endpoint currently engaged in playback.
We’ve pulled diagnostic logging and can only see examples of this failure with the SMSL DAC connected via USB, not with the Mac’s System Output. Can you please provide a timestamp of when this occurred last with the Mac speakers or another endpoint other than the SMSL DAC?
In some cases, the SMSL DAC fails to synchronize any clocks with RAATServer. Is this device firmware attempting to serve as the lead clock in your setup? Please share a screenshot of the Audio Midi Setup tool under Applications → Utilities on this Mac.
In other cases, the SMSL instructs RAATServer to tear down the stream when receiving MQA files from Tidal. Tidal is phasing out MQA and replacing with high-resolution FLAC, but their library still contains some MQA content during the phased rollout.
Please provide a screenshot of the Device Setup for this SMSL Zone, as well as the Signal Path in Roon.
Hi Connor, thanks for looking into this. I investigated a bit more based on your findings and can now confirm that this problem ist narrowed down on the combination of Roon client with the SMSL DAC raw-mda1 (with newest firmware from Sept.24)
Update. After loosing sync I had the same problem with SysOut and CoreOut. Timestamp is Oct 22 16:25 and 16:27 German time
I can further confirm that the DAC is serving as lead clock (see screenshot)
When I get into this problem by just waiting some time (even idle time) I can force resync by either restarting the Roon client or the DAC.
Due to the fact that I own more that 1000 tracks of mqa coded audio mqa will remain a use case I will have even if tidal stops serving it. With my other DAC Roon gets some kind of confirmation that the DAC is doing the MQA rendering. With this DAC I get the MQA decoding message in Roon but no MQA rendering confirmation. However the DAC indicates the MQA signal and is doing the rendering. See the two screenshots
This is not limited to this specific DAC. I am having the same problem with a MacBook M2 Pro and mojo2 dac connection to a Mac mini running Roon server on a hardwired gigabit ethernet network.
Pausing playback and idle time/system sleep causes all following tracks in the queue to be skipped unless I restart the client app (have not yet tried reconnecting the dac.).
This only started occurring with the latest build 1470.
I was now able to reproduce this just with CoreOut without any DAC connected. Timestamp is Oct 22th 17:57 (German time). I think this is Roon build 1470. It was not there before.
Hi @Chris_KA,
Can you take a look at your firewall settings and make sure Roon processes are allowed through. RAATServer and Roon are the processes you want to whitelist.
yes, the firewall is on but I can’t turn It off on this (managed) laptop. I can try a different (identical) laptop w/o the firewall and see if it still happens.
same here. Managed laptop without option to turn it off. I installed MacOs 15.1 RC and sadly still have the problem. This will be most likely also with the final version of 15.1
to address your question RAATServer and ROON are listed green in the firewall settings
Could you please reproduce the issue and share the specific track name when you experience the audio dropout or skip?
Let’s also refresh your RAATServer settings on the Mac giving you issues:
You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
I can easily reproduce the issue by starting Roon and just waiting 5 to ten minutes. After that EVERY track will refuse to start and after a few tries Roon reports the “too many error” message. I of course did’t try it with every track but I have enough empirical evidence for that. We are talking about local Flac files (with or without mqa encoding) and tidal streaming files. In my experience this is absolutely not related to what is going to be played next the only trigger is time. After 5-10 minutes you cannot start a new title anymore.
I also refreshed the RAATServer settings on my Mac, The problem unfortunately persists.
unfortunately I cannot confirm this. The problem persists in 15.1 and 15.1.1 (which was released on Nov 19). This is clearly related to exclusive CoreAudio mode with Apple firewall active.
Thank you @Rick_Frankel and @Chris_KA for those updates. We will escalate this by creating a development ticket to investigate further. While the details of the issue are somewhat broad, we’ll do our best to make progress. Please know that resolving this might take some time, but we are committed to addressing it as thoroughly as possible.
I just did the upgrade to 1483 on Roon core and all clients. The issue with the Mac client is still there. Unfortunately I cannot switch off the apple firewall. So this is still an open issue for me wich really prevents the use of Roon on my Mac.
@Benjamin We are going in loops here.
It was said several times in this and other threads related to this issue that the Roon apps are all listed as exceptions in the macOS firewall but as long as the firewall is active the problem persists. You guys need to find out what changed on MacOS 15 firewall to get Roon play along an active firewall. Others confirmed that the problem goes away if a no or a third party firewall (Norton was mentioned) was used.
Unfortunately I cannot switch off my firewall due to the fact that my machine is configured by a profile which prevents the deactivation of the firewall. This was stated my me as well several times.
