I have 2 MacBook Pros and 1 MacBook Air (along with various iPhones) running Roon Remote to Core on a Grimm MU2. The MacBook Air environment was transferred from MB Pro #1 when I set it up (i.e., a "clone" of MBP #1). MacBook Pro #2 is 'independent' of either MBP #1 or MB Air. I can run MBP1 and MBP2 together as Remotes without issue. I can run MBP2 and MB Air as Remotes without issue. But when I run MBP1 and MB Air Remotes at the same time, the screens go crazy. One or the other instance will search for the Core and time out. Screens on both flash and refresh over and over. Music might continue to play from Core, but the two screens are not usable. One instance will ALWAYS time out looking for Core, and this happens even if different output devices are chosen for the two Remotes. The only "fix" is to quit one instance of the two, and things go back to normal. Theoretically, these two devices should be able to act as Remotes together, as happens with MB Air and MBP#2. This is an issue because I usually run Remote on MBP#1, but sometimes grab MB Air as it's more handy, but nooooo... Can you help?
Describe your network setup
Altice modem/router 1Gbps hardwired to Netgear switch, hardwired to Grimm MU2. WiFi only for Roon communications.
I will look into that when I return home. Sounds reasonable. It’s like two twins who are goofing on Roon Core, and Core is not able to tell one from another.
This did not work. Thanks for the suggestion, though.
I would love to pursue this option, but… after deleting the app on MB Air, I couldn’t find ANY files with Roon or RAAT in the name. I poked around quite a bit.
Can anyone provide a specific path for these files?
As for the dot-hidden file, still working on that.
By the way, doing a fresh install of MacOS is not a good option for me.
Yeah, but I don’t think deleting them is necessary for just the deduplication of the cloned instances of a remote, based on previous cases, and I didn’t want to make it more complicated than necessary.
(The case I linked initially had a particularly sticky scenario where IIRC a server had been cloned, and therefore old devices were shown in Settings > Audio, so we went as far as deleting the Library files as well. We can go there if needed… I should not have linked this particular case but a simpler one, I suppose).
I was so hoping that this simple solution would work, but instead it only munged things up even more. After deleting the .rmembid file, I briefly saw that the original problem was still occurring (flashing screens, disconnect, etc.) In recovering from that situation…
Somehow, I managed to break both iterations on MBP1 and MBAir. Neither worked, so I had to delete files (AppCleaner) and reinstall. At this point, I have Roon running properly on MBP1 (most important), after a clean reinstall. On the MBAir, after reinstallation, it looks to connect to the Grimm, but just sits there doing nothing. So, MBAir seems completely Roon-broken.
Sheesh… how did we get here, Roon Labs?
At least the music is playing via iPhones and MBP1&2. But I’d really like to get the MBAir functional.
There’s probably some remnant of the cloned install lingering on the MB Air. If it was me, I would delete anything and everything related to Roon and do another fresh, clean install of Roon on the MB Air.
Yes, I would like to delete anything and everything related to Roon on the MB Air before attempting another install of Roon Remote. However, I’m getting the impression that I’m missing something, because I still haven’t had a successful reinstall. (Everything else is working just fine.)
Is there documentation on file paths for MacOS? Can @support provide some insight on places to look for any and all files?
This is not the biggest issue in the world, of course, but a pesky problem that I’d really like to chase down and fix.
Having some time to deal with this, I went on a search & destroy mission on the MB Air for anything related to Roon, and also deleted again the .rmembid file. Dumped the Trash and rebooted for good measure. Downloaded a fresh copy of Roon for Mac.
I can now run two instances of Roon Remote on the MB Pro and MB Air without screens freaking out. Evidently, I found and deleted some files that hadn’t been found on previous attempts.
The ONLY weird thing that I’ve noticed (so far), is that with the two machines running side-by-side, I couldn’t name System Output or MacBook xxx Speakers… on either system. I quit the MB Pro instance, and could then rename the MB Air outputs. But, when I restarted the MB Pro instance, it picked up the output names from the MB Air. Weird (or it’s weird when you don’t know how these things work).
I can easily live with this anomaly. I rarely, if ever, use system outputs for playing Roon.
Of course, if there was a way around this issue, I’d love to address it.
