Is the screenshot you’ve shared from MacOS or from your PC?
MacOS System Output is a locally-controlled zone. It won’t be visible on your Windows machine; it will only show up in Roon Settings → Audio when you run the Roon app on the Mac itself.
If you’re still not seeing it there, ensure that you’ve toggled local network access on for Roon in your MacOS Privacy & Security → Local network list.
Thank you for the update and for confirming those settings.
Since the Mac is running both Wi-Fi and Ethernet simultaneously, RAAT (Roon’s audio transport protocol) can sometimes get confused about which network interface to use to discover the local system output.
Before we dive deeper into network troubleshooting, let’s try a quick and effective workaround. Please try installing Roon Bridge on your Mac laptop. It runs as a lightweight background service specifically designed to expose audio outputs to the Roon Core.
You can download it here: Roon Downloads (just scroll down to the Roon Bridge section and select the macOS installer).
Once installed and running, check Roon Settings → Audio again to see if the Mac’s speakers appear under a new Roon Bridge zone.
Let us know if this gets the sound playing!
FYI MacOS gives a warning that RoonBridge will not run on future MacOS versions.
So I thought it was something with the Mac because this started after I had updated the OS, but it seems maybe it was with the computer that the Roon Server is running on. Because I restarted that and now the Mac speakers are discoverable. This seems to be true with or without the RoonBridge.
Thanks for letting us know that rebooting the Roon Server PC allowed the Mac speakers to show up, that is certainly strange. Please let us know if you observe this behavior occurring again and if you do please note the exact local time + date when it occurs so that we can enable and review diagnostics logging from your Roon Server.
If the handshake between Roon Server and the RAAT Server instance hosted on MacOS had gone stale, then a restart would prompt a fresh handshake and connection.
We’ll allow this thread to auto-close but please reach out here if this happens again.