· the last couple of updates as always stopped Roon from finding my speakers/amp all these are run ready products which have worked for the last couple of years fine until these last few updates I used to be able to just restart Roon after the update and this usually fix my problem but now I cannot use room at all. It will not find any of my speakers. I have done the obvious of restarting the router and restarting all of my hardware nothing works. Roon is now useless. It does not work.
Same problem for me! After each reboot of my mac I have to run Roon. And Roon does not recognize my peripherics. I have to close Roon application + Roon in menu bar. Then restart Roon and perhaps Roon recognizes my peripherics. If not, then restart + restart + restart +…… and suddenly the peripherics are recongnized.
I’m actually relieved to hear it’s not just me experiencing this, but it’s incredibly frustrating nonetheless. It’s honestly disappointing that the very core functionality of Roon—playing music—isn’t properly tested before updates are pushed out. Once again, it’s the weekend, and I can’t even enjoy music in my own home despite having invested significantly in this platform. This shouldn’t be happening with a product at this level.
Thanks Carl — that resolved the issue and everything is working again as it should.
That said, it’s incredibly frustrating to go through such a disruptive experience just to find out it was due to a permissions setting that could have been highlighted ahead of time. If this is a known change with macOS Sequoia, it would have saved a lot of stress and wasted time if Roon had communicated it clearly during or after the update process.
I really hope the team considers proactively informing users of potential OS-level conflicts like this in future releases — it would go a long way toward avoiding these kinds of painful weekends without music.
