Is the affected network Zone connected with Ethernet or WiFi?
· Ethernet
Does the issue affect all file formats?
· The issue affects *multiple/all* file formats.
Does the issue happen with local library music, streaming service music, or both?
· *Both streaming and local* *library* music are affected.
Do you encounter any playback errors with the "System Output" Zone?
· I don't have a System Output available, but I'd like to keep troubleshooting
How is the affected Zone connected to your RoonServer machine?
· Network - Ethernet
Which network audio protocol is the Zone using with Roon?
· Airplay
Since this is an Airplay Zone, have you tried toggling Airplay Compatibility Mode for this Zone in the Device Setup window?
· There is no change in behavior.
Does the device show up at all in Roon Settings -> Audio?
· Yes, it shows up there, but it isn't Enabled
Does the "Enable" button unlock the Zone?
· I pressed Enable, but the Zone remains disabled
Does the device play audio from another source when using the same connection?
· The device has no problems with another audio source
Have you checked that Roon is whitelisted in any firewalls?
· I've checked the firewall and the issue remains
If the device has multiple output options, do the other options work as expected?
· Multiple output types are affected
Is the device using the latest firmware as per the manufacturer?
· Firmware is up-to-date but the issue remains
What are the make and model of the affected audio device(s) and the connection type?
· Mac Mini M1 and Mac Studio M1 Max both on the most recent version of MacOS
Describe the issue
I have roon on my home mac mini server, and when I try to play it through my mac studio setup as an airplay audio device nothing happens so there's no way to stream my music on my pc.
Describe your network setup
both machines are connected to the same router through ethernet
The RAAT endpoint on the Mac should show up as an endpoint in Roon → settings → Audio where you can enable it.
Unfortunately, I don’t use Macs so I can’t say exactly where it would show up.
With wired ethernet, the only downside to using RAAT streaming is that RAAT zones/endpoints can’t be grouped with airplay zones/endpoints (all grouped zones must employ the same streaming protocol).
Hi @Oscar_Mendez,
Thanks for writing in to let us know a bit this issue. We have seen users solve issues of this type in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let me know if it helps?
Hey thanks for the quick response! I actually found a workaround that I can’t believe I didn’t try yesterday. I used system output on the mac mini and just airplayed it through the control center instead of through roon and it seems to work! I’d have to have it auto connect through airplay on reboot and there’s a bit of latency when pausing/playing but its good enough for now. I’d still like for it to work natively in the app eventually though. I tried the other DNS servers as well as disabling my firewalls, and turning off my vpn but the behavior is the same sadly.
Thanks for the suggestion, I don’t see any option for RAAT unless I’m misunderstanding? Perhaps that’s a Windows specific thing since they rely on Airplay for macs. I am enabling my PC though.
Install Roon on your Mac you then can select and enable it as a Roon zone to play to. This won’t use Airplay it uses Roons streaming protocol RAAT as it would to any Roon Ready audio device.
RAAT is the Roon developed protocol for streaming to Roon Ready devices and also devices running Roon endpoint software in some form (either explicitely by running Roon Bridge or the equivalent functionality in the Roon Clients [desktop and remote] and Roon Server).
On the Windows machines running the the Roon Client, it appears in Roon Settings Audio under “This PC”. I imaging there will be something similar for Macs. When setting up from other remotes, it will appear as one or more endpoints that can be enabled under a group associated with your Mac machine name.
If you want to use it on your Mac without having to run the desktop client, you will need to install Roon Bridge on your Mac and set it to run on startup.
RAAT has an advantage over Airplay in that it can play lossless audio at much higher sampling rates - so if that is important to you, you should definitely prefer RAAT.
I am running both Roon (For controls) and Roon bridge on the non-server(mac studio) mac, in the audio settings of the roon app I don’t see anything but “This mac” which is just the hardware directly attached to the mac mini server, “Roon tested” with apple tv and homepod and “Other Network devices” with the non-functioning Airplay option for the mac studio unfortunately. RAAT does sound appealing though so hopefully that is something I can get to work eventually.
When you run Roon Client on the (non server) Mac Studio, “This Mac” refers to the Mac Studio - not the Mac Mini running Roon Server. Hardward connected to the Mac Mini should appear under a section titled “Connected to Roon Server” or some such.
By contrast, if you run the Roon Client directly on the Mac Mini that is your Roon Server, the “This Mac” section will indeed refer to hardware connected to your Roon Server.
The following two screen shots show what I see when I run Roon Client on may laptop (which is not my Roon Server):
I see, For me “This Mac” isn’t referring to the mac studio unfortunately which i am assuming should not be the case. Here’s a screenshot of both roon apps in audio, they are identical. I also tried reinstalling roon and that didn’t help either sadly.
OK. In the first screenshot, you appear to be running the Roon client on your Mac mini which is your Roon Server. You can see your Mac Studio under “Other Network Devices” reporting itself as an Airplay device. However, if this is all that you see associated with the Mac Studio (ie nothing hidden off the bottom of the screen that would appear if you scroll down) then it would appear that you do not have either the Roon client application or Roon Bridge ruuning on the Mac Studio.
I’m not sure what I’m looking at in the second screenshot.
“This Mac” will always refer to the machine that the client application is running on.
In order for your Roon Server - the Mac Mini - to see RAAT enabled devices on the Mac Studio the Mac Studio must be running either the Roon Client or Roon Bridge.
The left screenshot is of the mac studio actually, and the right is the mac mini. The screens are identical and there’s nothing under other network devices even though I am running the Roon bridge and client on the mac studio.
