Core Machine (Operating system/System info/Roon build number)
Core: Mac Mini M1 (Mac OS 11.1)
Client: MacBook Pro (2009), Mac OS El Capitan 10.11.6.
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
All network connections via Ethernet.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Core: Peachtree DAC ITx USB
Client: Audioquest Dragonfly DAC USB
Description Of Issue
Three Days ago I upgraded the 2009 MacBook Pro to a Mac Mini M.
Now, the Core cannot see the Mac Mini at all, even though the Mac Mini sees the Core just fine, and the Mac Mini can play music everywhere (there are a couple of Apple TV’s around the house, along with the Peachtree) except from its own local USB Dragonfly.
Other music software, such as Audirvana, and the Mac OS, recognize the Dragonfly with no problem.
I can take the old 2009 MacBook Pro, set it next to the Mac Mini, move the Ethernet cable and Dragonfly from the Mini to the MacBook Pro, walk over to the Core (2015 MacBook), and both DACs appear just as they did three days ago. Once the cables are back on the Mini, the Dragonfly disappears.
I have deleted and reinstalled the Roon Software three times, with no change. I even made the Mac Mini a Core Machine and the 2015 MacBook a client, with the result being I could then see the Dragonfly on the Mini, but no longer see the Peachtree DAC on the MacBook.
Hello @Robert_Place, my apologies for the confusion here, I wanted to confirm some details. Is your Mac Mini M1 your core or the 2015 Macbook? Also, does the dragonfly DAC work fine if connected to one of the other mac’s involved?
Hi, thanks for getting back to me. The 2015 MacBook is the Core, and yes, the Dragonfly can be seen on the other macs if I unplug from the Mini and plug them in.
Hello @Robert_Place, could you please let me know how you chose to migrate to the new mac? Did you do a fresh install and restore a backup or something else?
Hi, it was from a backup-I’ve wondered if something with that was the issue. I reinstalled Roon in both machines and it obviously did not resolve it, and a clean install was going to be my next step if another solution wasn’t found here. I may just go ahead and give that a shot.
Have you been able to give a fresh install a try? In the past we’ve seen this type of behavior occur when something like Apple’s Migration Assistant or Time Machine was used to clone a machine to a new Mac. A fresh install of Roon might help, and then you can install a Roon backup.
Hi Dylan-Yes, a clean install fixed it, just completed everything last night. It took some time getting everything back, but worth it. All is good, we can close this issue. Thanks.
Robert