I have updated to Roon 2.60, using a Mac Studio with Tahoe 26.3. I have reinstalled Roon Mac and reinstalled Roon server. Rebooted Mac/router/ROCK multiple times. My iPhone suffers similar problems; it won’t let me play through the iPhone and all the other audio outputs show a red “enabling…”
I also went into privacy and toggled Roon in local networks.
I had overlooked this. However, I see now that there is another issue because you are running a mix of Early Access and Production, which you shouldn’t do as it may always cause issues, and I think it’s currently causing precisely what you are experiencing:
Well you must have installed EA on the ROCK at some point. It‘s probably best to revert it to Production.
Follow these instructions:
Moving RoonOS (Nucleus / ROCK) servers back to production
Download the instruction file and save it on your computer. Do not modify the name, extension, or content of this file.
Navigate to the /Data/Reinstall directory on your Nucleus / ROCK.
Copy the instruction file that you downloaded into the Reinstall directory.
Visit the RoonOS admin page and click on the “Reinstall” button.
The instruction file will be deleted after the installation process is completed. Once on a particular track or version you will continue to receive updates lo from that track without any intervention. This includes future use of the Reinstall function.
I just opened Time Machine and reverted to 2.58. Now it works. Seems to me Roon shouldn’t push updates when it trashes mine and many others ability to find audio devices. The support board is full of this issue!!!
Oh, and you probably still have to sort out the update channels your various machines are in, or they may update to the wrong, inconsistent versions in the future again.
Maybe a bit weird, I don’t know. But maybe it‘s normal if it has to run a scan after switching between EA and Production. (I switched to EA years ago when it was introduced and I never switched back to Production, so this would never have occurred for me).
Normally, switching between Production, EA, and back, should not cause any issues and shouldn’t require any additional measures, so I hope it finishes up normally and nothing gets messed up
Glad to hear that everything is working as expected once again! I will forward your remarks to the team, and will mark this thread for closure, thanks!