Does the issue happen with local library music, streaming service music, or both?
· *Only streaming* music is affected.
Please select the streaming service(s) with which you're encountering playback problems.
· TIDAL, Qobuz
Have you tried logging out and back in again to your streaming service in Roon Settings?
· Logging out and back in had no impact, the issue remains
What are the make and model of the affected audio device(s) and the connection type?
· Mac Studio M2 64GB , Macbook M1 32 GB
Describe the issue
Mac Update to Sequoia- After I installed Mac Sequoia 15 and 15.01 on my Mac Studio M2 64GB as a remote device, I have been unable to run Roon 2.0 build 1462 for any duration of time. It runs for perhaps appx 5 munutes and then stops and I get a message "Stopping placyback Too many Failures as it jumps from one song to another and stops. On My Macbook M1 which I haven't used for a while fith Roon, it will not connect to the Roon server running Roon OS- It says it will not initialize.
I am running Roon Server on an Intel Nuc running the current version of Roon Rock. It works fine with my IOS devices. I do not have issues connecting with my iPad or iphone. Thay are fine but my Mac Studio is my main method of connecting, Until the Mac OS upgrade, I have been running Roon without problem on any of my devices for a couple of years.
Please advise, I have a yearly upgrade coming up this month and I am concerned- I find folks with the same porblem online but no fix.
Describe your network setup
1GB Fios line. Roon Rook connected direct via Cat 6 cable to Dios Gigabit server. Client running vis wifi.
Thanks for writing in, it’s good to see you on the community again! As an initial first step in troubleshooting, can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed. If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.
I did reply. I have the issue on 2 Macs, one running Sequoia 18.01, and I tried the public beta 18.1, Hoping it would correct the problem, but no such luck. Hopefully, someone will post a solution, or Roon tech support will fix this, as it affects all my zones. At this point, I am using Roon daily to test if it works or if a patch has been made with an update. I have switched from a yearly to a monthly subscription, and if this isn’t fixed within the next month, I will be forced to cancel reluctantly. Any advice is appreciated.
Thanks for the additional details. We’ve gone ahead and enabled diagnostics mode for your account and what this does is upload a log set to our servers for review. Looking over the logs, it looks like the errors are most likely network-related.
The way that Roon works is that the remotes send commands to the Roon Server, the Roon Server does the processing and then it sends the sound to the audio endpoints. It is very strange that you say that this issue only happens when using the M2, as it should equally reproduce using any other Roon remote controller.
Have you made any changes to your network setup recently? The errors I’m seeing in your logs are often attributed to something going wrong on the internal routing from Server → Endpoints.
Hello,
The issue isn’t limited to my M2 Mac. It also occurs on my M1 MacBook. It seems more related to macOS and the devices themselves, as the problem started right after I installed macOS Sequoia 15 on both the M2 Mac Studio and my M1 MacBook. However, I have no issues with my M4 iPad Pro, which I’m currently using, or with my iPhone 16 Pro Max running iOS 18.01 on the A18 Pro processor. I also didn’t notice this issue on my older Intel i5-based MacBook Pro, but I haven’t used Roon on it for long enough to be sure. It is semi-retired.
I have not made any changes to my network. Everything else, including Tidal and Qobuz, is working perfectly. This happened immediately after upgrading my Mac OS to Sequoia. There have been no other changes. I have no problem on the same network with my iPad or iPhone—just the Macs with USB DAC or direct headphones. I just upgraded Roon. Same errors. Goes without saying very disappointed!
Thanks for the additional information - sorry to hear your crashing is still occurring.
We were able to enable diagnostics mode on your Roon instance running via the Mac, and saw some errors during startup in relation to TimeMachine. Do you currently have TimeMachine running on the Mac?
There are known issues with TimeMachine and Roon, and we advise users to keep them completely separate - make sure TimeMachine isn’t touching any files or folders related to Roon, and don’t run both applications at the same time.
Let me know if you’re able to work through the above, and if it helps with the crashing. Thank you!
Important finding: It only happens when switching from Tidal to Qobuz. It does not matter what format of he song is 192 mHz or any other The failure only occurs during the change in song and from Tidal to Qobuz and continues failing song after song. The reverse is fine- Qobuz to Tidal.
If I open Roon and start in Qobuz it works fine. No I am going to remove Qobuz and log back in to see what happens. This is big and gives me hope I may survive this.BTW- It’s the same on my other Macbook M1 laptop. I love Roon - I was very disheartened. I’ll let you know after the change shortly. Again, this just started after upgrade to Sequoia 15.
So I logged out of Qobuz and logged back in, synced the database, and had an immediate failure switching from Qobuz to Tidal. I restarted Roon, and it’s been working both ways, Tidal to Qobuz and back, but the problem was definitely while changing songs- now I haven’t had a failure Tidal to Qobus alternatively through four songs. I put my cancellation on hold and going monthly, but if all goes well, I’ll switch back to yearly on my yearly renewal in 12 days. I convinced myself I didn’t need Roon while it wasn’t working. I am still having intermittent problems. For example, I just had a new one trying to restart a song I had quit Roon on. Nothing to the extent as before. Can “tech support” look into this now that the trouble has been narrowed down to song changes? Also, I can’t seem to get rid of the (6 days left) showing on my app, though I have restored the account to monthly.
It’s still an issue because if I advance a song to the middle, it will cause a failure, but the constant failure has ceased. The issue comes up somewhere in the processing of the song. usually at the very beginning. or if I jump to the middle or another point in a song.
As I reported previously, this was the first thing I tried. I upgraded to 18.1 on my Macbook M1, hoping Apple might change something. No luck on that; sadly, I went from yearly to monthly and will quit Roon if this can’t be resolved in the next 28 days. It’s too much aggravation; I did try other potential solutions a few years back, but not since I got my hands on Roon. Nor am I wondering if there is anything similar. I have a DAC/amp for my headphones and speakers with a 7-band Parametric Equalizer, but that was only one aspect of what Roon did for me. Sadly, Roonlabs engineers can’t seem to make this right in a reasonable time. I hope they do soon.
Sorry to hear your issues persist - our team is still investigating potential issues, and so I’m not able to speaking on any timelines at this time.
That said, do you receive an Apple crash report when Roon crashes on your Mac? If so, can you save a copy of it, and upload it for our team to review? You can upload it here: File Uploader
With that, we’ll also need a fresh set of Roon logs from the Mac if possible, please use the directions found here and send over a set of logs to our File Uploader?
Thanks, Benjamin. I thought you gave up on me. I uploaded the logs, though I haven’t had much usage since the 18.1 update of Sequoia, when Roon would not see my USB DACs. I was wondering it may help if I delete the library files of Roon as well as the app and reinstall om the client Macs
