Roon Core is an M1 Mac Mini, base model with 8GB RAM
MacOS 12.6
Roon 2.0
Networking Gear & Setup Details
Eero wireless mesh - has always worked well with Roon
Connected Audio Devices
Mac Studio with M1 Max
64GB RAM
Mac OS 12.6
Number of Tracks in Library
8,000 tracks
Description of Issue
I bought a new Mac Studio (which seems amazing, esp. once I get Roon running as a remote). I used the migration tool to clone the Mac Mini to the Mac Studio, so I got all my apps running.
One of those apps was Roon. Now, if I go into Settings, I see the right machines:
I’ve tried uninstalling the app and clearing the hidden Library folder (Opt/Finder Go) include RAATserver and Roon. Re-installed. It’s still confused. Any thoughts?
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
2
I believe that’s a result of the cloning process.
You might need to uninstall Roon on the studio and then reinstall as a remote.
But I’m not a Mac guy so will let others chime in here as that didn’t seem to work for you.
No, it did not, I repeated the procedure again, just to make sure I didn’t do something wrong. When I reinstall and go to the settings/audio tab of Roon, I only see audio devices for the Mac mini, which is the core. No audio devices are visible for the studio.
I did have exactly the same problem. Everybody told me to uninstall Roon and reinstall it again. It does not work. The only solution was to wipe the new Mac completely und to reinstall it from scratch.
I did not have the time to reverse engineer in which uncommon location Roon stores its identification and how this identification is generated. But they definitely do something the should not do.
This is unnecessary, and your last comment absurd.
When you uninstall an application, the Application folder is deleted. However, settings are retained in the Library folder, as they are for most applications. @Mitchell_Baxter, simply delete these entries.
thanks @Martin_Webster. I had tried that with the Studio, which is a remote Roon player. It was the one that was migrated from the Mini using Apple’s utility.
To be safe, here’s what I just did:
On the Mac Mini, completely remove Roon, including the app and the RAATServer and Roon directories in Libraries. Then re-installed the Roon on that machine as the Core. Restored my library from a backup (so I have playlists, etc.). Works well.
Then in the Mac Studio, I did the same delete and re-install. When I connected to the Core, I see it:
Where it says, This Mac - that’s actually the Mini, and the devices connected to the Studio are not there, nor is the Studio. Here’s the Mini (Core’s) Audio devices for comparison:
Hopefully Roon support will look at this and respond, unless someone else can figure out why this is happening. I’d really rather not completely rebuild my Mac Studio, which I just got configured and works great with all apps but Roon!
You could do a factory reset of the Studio, I suppose. Then, install Roon without doing the cloning which you should not do with Roon. A factory reset may be the only way to eliminate all traces of the cloning process.
I am going to tag @support. I remember reading something about how Roon uses unique install identifiers and that cloning a Mac can cause issues with how Roon identifies the Core between the legacy and cloned Mac.
The steps you should have taken on the Mac Studio are…
Delete the App
Delete Roon and RAATServer folders from Library folder, and for good measure, Roon entries in Saved Application State starting com.roon.Roon.
Reinstall the Application
You don’t need to restore the database, since you’re running Remote on this machine (the database holds details of the core) and is only needed on the Mac Mini.
Thanks @Martin_Webster I was hopeful when I saw your note, as I had removed the app and the two folders in Library (Roon and RAATServer), to no avail. I removed the Saved Application State file com.roon.Roon (there was 1) and still my Roon instance on the Studio thinks it’s the mini.
