I am testing Roon with the server running on an M1 MacBook Air. I have a delay with my Yamaha R-N602. I have read the thread that suggests I am not the only one who has delays when grouping AirPlay 1 with 2. First question, has anyone found a solution?
2nd question, the aim was to run the server on A M1/2 Mac mini that will live next door to the Yamaha amp. Can I just output from the Mac to the Yam? I can’t seem to group the MacBook in this way without setting it up as an AirPlay receiver but this also has a delay. When I play through the MacBook as the output, I then cannot group the rest of my Airpay 2 speakers.
The N602 is connected via a switch to my Ubiquiti Amplifi. The AirPlay 2 speakers are a Naim Muso 1 and a Yamaha Musicast 20.
I tried version 1.8 and it worked mostly great on the MacBook Air.
So I have installed Roon on a fresh install of Mac OS on a Mac mini M2. It’s connected to via a network cable. I have connected all of the zones via WiFi. I first started with 1.8 and all good.
So I then have tried version 2 and initially still had the same issue with the AirPlay 1 zone. Another issue I have though is the muso will not play!! It lights up and shows it is on AirPlay but no sound.
Good news is that after a little fiddling, the delay between the Yamaha gear has gone. I switched on legacy for all.
If only the muso would now join in.
My server is on.
I think the switch is now not connected as everything apart from the Mac is connected to it.
We saw this occur from a recent Roon Server diagnostic report. More specifically, an I/O error which severed the RTSP (Real-Time Streaming Protocol) connection between Roon and the muso device.
Can you confirm:
The firmware on the Muso is up to date?
Power cycle the Mu-so and the Roon server.
Ensure that the necessary ports for AirPlay (TCP 7000 and 7100) are open and not being blocked (if other airplay devices are functioning properly this is likely not the case.)
Get a direct hardwire connection from the Muso to your router and see if you’re able to get things running properly.
The Muso is up to date. I powered it off and reconnected it to the network still by WiFi at the moment. I deleted it from the Apple Home app and then added it again, switched on legacy mode and it’s back!
I have only had a bit of time with it. The timing between zones is not completely correct. It seems to drift a bit and a pause and restart brings it back in line.
I think this may be down to my Network setup. I am going to try taking out the Ubiquti wifi router and just use the one my ISP has provided. I will hard wire everything in too to see if this tightens it up.
I think this will fix my last issue too which is getting Arc to work. I had an error which I put on the back burner when running the Arc test. I wanted to get the grouping fixed first so went back to it today and it says it’s now ready. However, it’s not! I cannot connect from outside the network.
We’re glad to hear the Airplay issue is resolved for now. Please take note that we’ll be continuing to iron out and improve Airplay compatibility with Roon 2.0, so please reach out in a new post if you encounter any new dilemmas with that protocol.
Concerning ARC: it looks like you’re going to rely on a MacOS RoonServer machine, whether it’s the Air or the Mini. Since that’s the case, I recommend bypassing port forwarding entirely and using Tailscale for NAT traversal instead. Tailscale will prevent you having to create manual port forwarding rules or eliminate routers to bypass the double-NAY layer created by your dual-router setup. In the event that your ISP blocks port forwarding with their own CG-NAT, Tailscale will still work when port forwarding won’t.
