· Roon Remote on MacBook Pro disabled and stuck in "Enabling" in Audio settings.
Tell us about your home network
· Roon Remote running on MacBook Pro (v2.60, build 1629) can access and control Roon Server running v2.59, build 1625 (EA), however it somehow disabled as an audio endpoint. Worked before. Attempted to enable it in Audio Settings, but it gets stuck with red message "Enabling..." and never gets added.
Yes, that’s what happens currently when you run a mix of EA and Production, it’s been reported and answered many times. Probably because of the code signing changes in the security fix in 2.60 Production, which makes it incompatible with the EA version.
Don’t run a mix of EA and Production is the easy answer. It may often work, but sometimes it may not because the versions are incompatible. Running a mix is just asking for trouble.
There’s not much difference. I’d say it depends mostly on whether you generally want to run EA or Production in the future.
Not sure what your server runs on. When switching between EA and Production with Windows or Mac, the process involves simply installing Roon from the appropriate setup file either for EA or for Production, so there is zero difference in difficulty. Switching Nucleus or ROCK involves downloading a file, placing it in the Data folder, and rebooting. Not very difficult either - and if you use Nucleus/ROCK, you already did this when switching it to EA.
See How do I sign up? and How do I leave? (depending on which one you want to do) in the instructions:
One thing to consider: If you use Roon Bridge somewhere, switch the server to Production at least for the time being. That’s because Roon Bridge was also updated to 2.60 Production, and they kind of forgot about a corresponding EA update, so currently an EA server does not work with Bridge. (This should be fixed next week).
Thanks for writing in! We wanted to check in and see if you’ve been able to get things sorted out, based on your account admin it looks like your devices are all on Production and up to date.
Yes — thanks so much for checking! And thanks again to the Weekend Warrior Community members who talked me off the ledge!! Not sure why a Production release got updates before the EA release.
In any case, all good now… all remotes (2 other MacBooks + 2 iPhones) are CoreAudio-enabled and back online. But having noted that, I already miss the scheduled background analysis feature in the EA release… any idea when that feature will be in production?
Also, will the need to re-toggle LAN access to Roon in Mac OS following a reboot ever get fixed?
There’s no clean answer there although the team continues to look for one.
MacOS Sequoia reengineered local network security, but it provides no programmatic way for apps to “safelist” themselves. Unfortunately, Roon cannot influence the OS to permanently grant local network permissions. From Apple’s perspective, retoggling the permission is the intended fix.
This can affect any third-party app that relies on local network access, including browsers and audio applications.
The macOS 15.3 update quietly reduced the frequency of retoggling by recalibrating the system’s sensitivity, but the issue can still occur, even on Tahoe.
Not sure why a Production release got updates before the EA release.