Can’t use 2 Mac clients simultaneously on Roon

[Bob_Silver1 (Bob Silver)]

Roon Core Machine

I’m using 2 Mac’s as remote clients. Both are running Mac Ventura software. Individually each works fine. But when I try and launch the other Mac Roon cannot find/connect to Roon Core. If I close Roon on the other Mac then it connects fine. Behavior is identical on either machine.

I’m using the most current software on all Roon devices. My iOS devices work normally regardless of the Mac issues.

I’m stumped by the cause of this issue.

Networking Gear & Setup Details

Connected Audio Devices

Number of Tracks in Library

Description of Issue

[Suedkiez (Just a fellow user like you)]

Have you cloned the Macs with Time Machine or similar backup software?

[Bob_Silver1 (Bob Silver)]

Long ago when the Mac mini was new I used the settings from the MacBook. Yes it behaves as it it’s cloned. How can I kill that? Uninstall and reinstall Roon??

[mSpot (Richard)]

Not sure if this would matter, but take a look in Roon Settings > Audio on your two Macs. Are they assigned with the same Roon name?

[Suedkiez (Just a fellow user like you)]

Cloned Mac completely mixed up with original Mac

Cloning moves files that are / should be unique to a single machine. Exit Roon on the remote and delete the Roon library folders like here: There is also a Roon file /Users/USERNAME/.rmembid (note it starts with a period and is therefore by default hidden) that should not be cloned to a different machine. Delete it (see the internet for how to make dot files visible in Finder) To move Roon, make a backup on the old machine, install fresh on the new machine, restore the backup. You may also w…

[Bob_Silver1 (Bob Silver)]

I deleted the Roon file /Users/USERNAME/.rmembid. Then uninstalled and reinstalled Roon. Mage no difference. The audio zone names are completely unique to each computer. When trying to launch Roon from other computer causes playback to stop and Roon to crash/quit.

Whats odd is I do have another Mac mini on my network that is an older Mac running Catalina. It coexists fine on the network.

Stumped.

[Suedkiez (Just a fellow user like you)]

Did you also delete the folders before reinstalling as in the instruction?

[Suedkiez (Just a fellow user like you)]

@Bob_Silver1

Whats odd is I do have another Mac mini on my network that is an older Mac running Catalina. It coexists fine on the network

Well that’s the normal behavior and easily explained if you didn’t clone this one but really did clone one of those that are acting up

[Bob_Silver1 (Bob Silver)]

Ok I deleted the following.

Deleted the App Roon and deleted RAATServer folders from Library folder,

Could not locate the following to delete. Roon entries in Saved Application State starting com.roon

I deleted the Roon file /Users/USERNAME/.rmembid

Reinstalled Roon. Same behavior as before. Even after deleting Roon still came back on the same album I had been playing before. So clearly this was not a clean installation.

[Bob_Silver1 (Bob Silver)]

One other thing if it matters. I am running Mac Sonoma not Ventura on both Apple Silicon macs

[Suedkiez (Just a fellow user like you)]

@Bob_Silver1

Deleted the App Roon and deleted RAATServer folders from Library folder,

Not to be annoying but it said

1. Delete Roon and RAATServer folders from Library folder, and for good measure, Roon entries in Saved Application State starting com.roon.Roon.

So did you delete the Roon and RAATServer folders?

@Bob_Silver1

I deleted the Roon file /Users/USERNAME/.rmembid

Just to be sure: You did replace the USERNAME, right?

@Bob_Silver1

Could not locate the following to delete. Roon entries in Saved Application State starting com.roon

The Saved Application State probably does not matter, but you are right that the instructions were not very clear. It’s like this:

1. Open finder, in the menu bar click Go > Go to Folder
2. Enter ~/Library/Saved Application State/ and then press Enter
   
   
3. You will be in the ~/Library/Saved Application State/ folder
4. Find and delete anything starting in *com.roon, probably there is only com.roon.Roon.savedState

[Bob_Silver1 (Bob Silver)]

Could not locate the Roon folder. I looked after I deleted the application.

And yes I did use my user name to delete .rmembid

Update

I have just deleted everything again. Found the Roon folder now as I hadn’t deleted the app yet. Reinstalling again.

WORKING!

So it appears that I had to delete the folders before deleting the app. This time when I reinstalled it I got the initialization screen which I hadnt been getting before.

Thanks for the Help!!

Bob

[Suedkiez (Just a fellow user like you)]

Great. The Core must be able to recognize each remote as a unique one. The cloning duplicates the Roon and RAATServer folders as well as the .rmembid file, and so it looks to the Core as if one Roon remote is talking to it, when it’s really two.

By deleting them and reinstalling they get recreated as unique new ones, so all should be good now.