I'm having trouble with my DAC, speakers, streamer, etc.
What best describes the issue with your audio device?
Other
I am running Roon Core on a DS218+ NAS. I am running RoonBridge and Roon on my Macbook Air.
When I look in the Settings | Audio menu in Roon on my Macbook I do not see a This Mac setting. With the Audio menu open the screen flickers repeatedly.
Periodically it recognizes my Macbook as an Airplay device, but I’m unable to get sound that way.
I have KEF LSX II LT speakers connected to my Macbook via USB.
I’d like to stream Roon to my Macbook and then play to the speakers using USB output, however that isn’t working.
The MacBook is connected via a) WiFi as well as b) Ethernet to a Asus Zen AX mesh router node. The main router node is hard-wired to a Motorola cable modem.
Are the node and primary router connected via ethernet?
If not you are using WiFi between the two for backhaul and you are likely to run into trouble.
If you have your MacBook connected by WiFi and ethernet at the same time, you could be causing a conflict. Try one or the other. I’d suggest trying ethernet primarily, more so due to a mesh network with a WiFi backhaul.
Where does you Roon Server on the NAS connect in your network.
Thanks Menzies. I have made the Ethernet adapter inactive so it is only using WiFi now. There is no Ethernet backhaul so using WiFi.
I haven’t had any problem streaming over Chromecast or Airplay to my speakers, but I’d prefer to use the USB connection from the Macbook under the assumption the sound quality is better. I am constantly on Zoom meetings working from home with very few issues.
The Roon Server is on a Synology NAS connected via Ethernet to the main Asus router node. I looked at the Roon Server logs and I see these three lines repeated over-and-over:
{“request”:“enumerate_devices”,“subscription_id”:“0”}
03/16 13:53:30 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xx:9200] lost client connection. Retrying
03/16 13:53:30 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xx:9200] connecting (attempt 1)
Ok, I’m building a good picture of how things are set up and do believe the issue lies with the mesh setup using a WiFi backhaul.
Roon sends a continuous PCM stream and if operating with a WiFi backhaul and WiFi from the node to the MacBook will affect bandwidth.
I operate a mesh system with ethernet backhaul and have no troubles. I can also run on WiFi backhaul as I have more nodes than my house size requires but to ensure it all works should my ethernet switch go down.
Each hop from primary to node to device you reduce bandwidth quite a bit, up to half and so on.
Some mesh systems can cater for this.
My recommendations would be, in order, would be
turn off the mesh node unit and try connecting your MacBook to the primary nodes WiFi
If it works, great you may not need the mesh node
Doesn’t work, turn the mesh node back on, next step
try a long ethernet cable between primary and mesh nodes (toporarily)
If it works then I feel you may need to make this permanent
If it doesn’t work, try the same ethernet cable to your MacBook Pro (turn of WiFi and turn on ethernet)
If all this fails I’d be stumped as to the issue. A fault with the MacBook is unlikely if you use it for lots of other things.
Also, whilst other things work, Zoom, streaming services own apps, Roon is different and a sod when things go wrong.
I tried each of the steps below. In the last step, I connected the Macbook to an Ethernet cable, so directly linked to the NAS with Roon Core over Ethernet, and still getting those messages that RoonServer cannot connect to the Roon Bridge:
03/17 11:14:34 Debug: [easyhttp] [33] POST to https://api.roonlabs.net/discovery/1/query returned after 136 ms, status code: 200, request body size: 74 B
03/17 11:14:34 Trace: [raat] RAATServer discovered: RaatServer Mike @ xxx.xxx.x.xxx:9200
03/17 11:14:34 Info: [raatserver] GOT SERVER 17ff80e5-1fc0-d69b-ebf5-896500c3186d::05bc4c89-054b-4f3f-ba65-7443359ac10e @ xxx.xxx.x.xxx:9200 Mike PROTOVER=1 RAATVER=1.1.38
03/17 11:14:34 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] connecting (attempt 1)
03/17 11:14:35 Info: [stats] 4510mb Virtual, 1000mb Physical, 721mb Managed, 323 Handles, 61 Threads
03/17 11:14:37 Warn: [rnet/RnetJsonClient] failed to connect No route to host
03/17 11:14:37 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] client connection failed. Retrying in 500ms
03/17 11:14:38 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] connecting (attempt 2)
03/17 11:14:40 Warn: [rnet/RnetJsonClient] failed to connect No route to host
03/17 11:14:40 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] client connection failed. Retrying in 750ms
03/17 11:14:41 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] connecting (attempt 3)
03/17 11:14:43 Warn: [rnet/RnetJsonClient] failed to connect No route to host
03/17 11:14:43 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] client connection failed. Retrying in 1125ms
03/17 11:14:44 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] connecting (attempt 4)
03/17 11:14:44 Debug: [easyhttp] [34] POST to https://api.roonlabs.net/device-map/1/register returned after 155 ms, status code: 200, request body size: 2 KB
03/17 11:14:44 Trace: [devicemap] device map updated
03/17 11:14:46 Warn: [rnet/RnetJsonClient] failed to connect No route to host
03/17 11:14:46 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] client connection failed. Retrying in 1687ms
03/17 11:14:48 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] connecting (attempt 5)
03/17 11:14:49 Warn: [rnet/RnetJsonClient] failed to connect No route to host
03/17 11:14:49 Trace: [raatserver] [RaatServer Mike @ xxx.xxx.x.xxx:9200] client connection failed. Giving up
03/17 11:14:49 Trace: [raat] [sood] Refreshing device list
03/17 11:14:50 Info: [stats] 4502mb Virtual, 1004mb Physical, 721mb Managed, 322 Handles, 62 Threads
03/17 11:14:59 Debug: [easyhttp] [35] POST to https://api.roonlabs.net/device-map/1/register returned after 173 ms, status code: 200, request body size: 2 KB
03/17 11:14:59 Trace: [devicemap] device map updated
03/17 11:15:05 Info: [stats] 4502mb Virtual, 1003mb Physical, 721mb Managed, 322 Handles, 62 Threads
03/17 11:15:08 Info: [remoting/serverconnectionv2] Client disconnected: 192.168.1.67:57820
03/17 11:15:20 Info: [stats] 4502mb Virtual, 1001mb Physical, 721mb Managed, 322 Handles, 63 Threads
03/17 11:15:21 Debug: [easyhttp] [37] POST to https://api.roonlabs.net/device-map/1/register returned after 148 ms, status code: 200, request body size: 2 KB
03/17 11:15:21 Trace: [devicemap] device map updated
03/17 11:14:49 Trace: [raat] [sood] Refreshing device list
I haven’t been able to get to the point where I tell Roon to play anything on the machine with RoonBridge…so are you sure PCM dropouts are the issue? Is it that a port is being blocked instead?
@Michael_Weadley, how was the Air connected to the NAS, directly to it or is there an Ethernet switch that connects the Air and the Roon Server/NAS back to the router? The logs from Post #9 above is showing a connection error and it seems the Roon Server cannot find a path between the Air and the NAS/Roon Server.
Thanks, that means it should be a good connection, but the logs are showing otherwise. Have you confirmed you have firewall permissions set on the Air to allow for Roon?
Do I need to add RAATServer also, and if so how, since it is not a separate application?
I’ve been able to validate access to the Air port 9200 from a networked Windows machine, but I haven’t been able to validate access to other ports I see in the logs.
Not sure overall which ports I need to be able to hit remotely, nor precisely how to validate. I can validate from another Mac or PC; not sure if there is a way to validate from the NAS itself where Roon Core is running?
On Mac, if I look in Applications and expand Package Contents for RoonBridge I see a RAATServer.app. But even when I add that to the Firewall I’m still getting the connectivity errors.
What do you recommend as a way to validate whether the right ports are open?
Thank you. @support, please let me know where to upload logs and detailed description of the topology. I have 6d left of a trial, so hoping to get this working better than Audirvana and Synology DiskStation.
Thanks for writing in and thanks for giving Roon a try! Although I’m sorry you’re running into issues getting your connections squared away. We’ll be sure to get you properly setup with enough time to give Roon a proper try
A few additional settings to review from the Mac: Settings>Privacy&Security>Full Disk Access - is Roon enabled? If not, toggle it on and see if that changes anything.
If you temporarily disable the Macs firewall, does your issue still persist?
We’ve enabled diagnostic mode for both your NAS and your Macbook. While we take a closer look into things, I’d be curious to see if, temporarily, you could set your Macbook up to run as Roon Server - just to see if you can get Roon functioning the way you want it (outside of Roon Server running on your NAS)
Let me know if you’re able to give this a try, and I should have more information to share soon.
Hi benjamin, I have disabled the Mac firewall and it hasn’t changed things so far. I’ve uninstalled Roon from the NAS and my Macbook and I’ll try to install RoonServer on the Macbook. Then I’ll check Full Disk Access.
Hi benjamin, I’ve uninstalled Roon from the NAS and my Macbook. I then reinstalled Roon on my Macbook and created the RoonServer on my Macbook. Now I can play to my Kef speakers using Airplay, but cannot play using the Macbook USB connection. When I try the Macbook USB connection, I see the track proceed second by second, but have no sound output.
