The old one was with the iPhone local output, I believe this is a bit different. I occasionally see this, too, still after the supposed fix mentioned in your old thread. Restarting Roon on the phone seems to fix this for me.
I believe on your Mac it might be a different issue that quite many people experienced. Try this, it helped often in similar cases:
My guess is that, after an update, macOS considers it new software and requires a reconfirmation but doesn’t signal it with a notification. I don’t know if it happens once after the macOS 15 update or after every Roon update, but the issue started to occur with macOS 15. Neither do I know if the cause is in macOS and/or if Roon has to adapt something, but Apple made many changes to security very late in the macOS 15 release cycle and Roon isn’t the only affected software.
Local device discovery in Roon goes through the network layer as well, as far as I know. Which makes sense to keep it simple and not have two code paths for remote and local devices. But I can be wrong.
I thought you had said that it worked after toggling the switch. Did it not?
Hi @amk221,
Thanks for reaching out to as us about this issue. @Suedkiez is correct that local device discovery passes through the network just like discovering other devices. What is the current state of your Roon Server? Are you seeing your local audio devices?
@Suedkiez right so, I was rushing - basically I had Remote Desktop’d into the Roon Server. And the music was playing through that. I just figured, since I could hear music, it was sorted.
@daniel set up is 1 Mac mini Roon server, 2 mbp laptops. Very basic, nothing special in terms of network config. As per above screenshot, no local devices showing
Sequoia’s tighter network security is policing the interaction between coreaudio and Roon’s loopback connection. Toggling Local Network access On/Off for RoonServer might continue to resolve the issue if you lose all local Zones on a MacOS 15.x machine. Restarting RoonServer or the machine might also help.
