Local audio options intermittently unavailable on Roon for M1 Max (ref#KX348E)

[Ken_Snyder]

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

Most of the time when I start Roon on my M1 Max laptop it does not show ANY local audio options. However, maybe 1 in 5 times it does and two options (System Output and Schiit Bifrost 2 DAC) are already open in the UI with red text above saying "Enabling...". Sadly there is no way to type into these fields. I noticed an issue with this problem in the community blog from 5 years ago but there was no real resolution.

Describe your network setup

I'm using Unifi network, mostly all wired connections with wireless only devices connecting via WIFI but I have very strong WIFI coverage and my laptop currently has both a strong WIFI connection and a wired connection.

Sadly, the service is now dead.

[Ken_Snyder]

Note: in the thread from five years ago it was suggested that one go into the server and rename the directory .RoonServer to .RoonServer_old which i’ve done but it seems to have had no impact on things.

I did run the .bin/info command and got the following:

I then rebooted the server and redid this command and got the more compact:

[Ken_Snyder]

I tried systemctl start roonserver but it just hung.

After that I tried the following sequence:

systemctl stop roonserver
systemctl enable roonserver
systemctl start roonserver

It now HAS started and my Roon Remote client connects to it but no local audio is available and now I see an intermittant dialog “Waiting for your Roon server” showing up which shows briefly that it’s “connecting/reconnecting” (I’ve never seen this before).

I finally quit and reconnected with the same lack of local devices showing but this time the dialog appeared again briefly but suddenly the local audio devices showed up with the now four devices in the “enabling…” state:

and of course still none of them are actually text inputs which can be entered into to give a name.

[Ken_Snyder]

Oh btw, that original “info” command that I posted was actually a small shell script which I wrote (sorry, i had that you’d provided that at first):

After restarting the server as I mentioned in my last post I then reran this script and got similar but not identical results to what I was getting before (notable differences highlighted):

[Ken_Snyder]

Not sure if there is any useful info in here but here’s the server log along with the raat log:

NOTE: I noticed that after restarting the .RAATServer/ directory was not recreated so what I’m presenting is what exists now in .RAATServer_old/Logs/RAATServer_log.txt (it may be that this log file is no longer in use).

[connor]

Hi @Ken_Snyder,

Thank you for your post.

Renaming the RoonServer folder will regenerate your RoonServer database, but it won’t regenerate the RAATServer instance installed via Roon Remote on the Mac. Instead, on the Mac, locate the RAATServer folder and rename that. Additionally, verify no third-party software is controlling coreaudio or restricting Roon’s access on the machine.

Your Macbook Roon Remote appears to be connected to our servers via several subnetworks, but none of them are the same subnetwork to which RoonServer is connected. How many subnetworks do you use in the network setup you’ve mentioned above? Roon will need to remain on a single subnetwork across your devices.

[Ken_Snyder]

I have a few VLANs here, 192.168.20.x/24 is IOT where my Apple Airpods, ATV’s, TV’s, Sony AV amp, etc. live. WIFI Clients use 192.168.10.x/24, and trusted wired devices would use either 192.168.100.1.x/24 or 192.168.1.1/24 depending on their functions. Other clients, like my intel based iMac worked just fine with this network configuration.

[benjamin]

Hi @Ken_Snyder,

@Ken_Snyder

I have a few VLANs here,

This is likely the culprit behind your issues here. If you temporarily disable all but one subnet (non VLAN) and connect your Roond devices, are you able to reproduce the issue?

[Ken_Snyder]

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

I explained the issue in detail here:

https://community.roonlabs.com/t/local-audio-options-intermittently-unavailable-on-roon-for-m1-max-ref-kx348e/279601/8?u=ken_snyder

but the issue was closed without my consent.

In short, my M1 Max laptop has a Supported DAC (Schiit Bifrost 2) connected to it but I can't add it to my Roon Remote.

I see a strong tendency to blame subnets but as I said in the last issue I raised ... it works on other devices on the network. I'm quite technical and all the obvious solutions have been tried.

Describe your network setup

Ubiquiti router and many switches, mainly wired but some wireless

[Ken_Snyder]

Please do NOT suggest subnet issues. I know this makes your work more complex but it IS NOT THE ISSUE.

Last time I tried to raise this a person suggested that I remove a folder on my client device but didn’t indicate where to locate this folder. I’m happy to try this but please be specific!

[Ken_Snyder]

[bearFNF]

Regardless of your desire to not look at subnets as the issue: Unfortunately, I agree that this could be a subnet issue. RoonServer needs to be on the same subnet as the endpoints and remotes to reliably work and given that you stated:

I have a few VLANs here, 192.168.20.x/24 is IOT where my Apple Airpods, ATV’s, TV’s, Sony AV amp, etc. live. WIFI Clients use 192.168.10.x/24, and trusted wired devices would use either 192.168.100.1.x/24 or 192.168.1.1/24 depending on their functions. Other clients, like my intel based iMac worked just fine with this network configuration.

This indicates that your wired and wireless devices are on different subnets. Is the Roon server wired? If so, and the M1 Max is wireless, then, issues will likely occur. The fact that

@Ken_Snyder

it works on other devices on the network

Has no bearing on the recommended and stated way that Roon and RAATserver works and should be setup.

What subnet are the Roon Server and M1 Max on?

Either way, a simple test would be to connect your M1 Max to the wired network and see if that “fixes” the issue. Or, assign the M1 Max an IP in the same subnet as the Roon Server and see if that fixes it.

[benjamin]

Hi @Ken_Snyder,

@Ken_Snyder

but the issue was closed without my consent.

The previous thread auto-closed due to 15 days of inactivity. I’ve reopened your prior case and merged threads.

@Ken_Snyder

Please do NOT suggest subnet issues. I know this makes your work more complex but it IS NOT THE ISSUE.

Unfortunately based on the system details and issue symptoms you’ve provided, its definitely something we’ll need to rule out, which it sounds like you haven’t tested yet. Please let us know if its something you’ll be able to try.

@bearFNF

Either way, a simple test would be to connect your M1 Max to the wired network and see if that “fixes” the issue. Or, assign the M1 Max an IP in the same subnet as the Roon Server and see if that fixes it.

VLANs fall outside the scope of Roon Support, so we’ll agree that moving all your Roon devices onto the wired network is the best next step in troubleshooting.

If you’d like to continue working within a VLAN ecosystem, we have a dedicated category Tinkering where other users in similar setups can offer additional advice.

[bearFNF]

@Ken_Snyder You might query over in this thread and see is the OP has ideas for oyu, seems like he figured something out using VLANs bu thas a few issues to figure out. Maybe you two can help each other?

Differences in RAAT discovery behavior between Roon Bridge and Roon Ready output devices

Hi folks, I have a question about the RAAT discovery protocol that Roon Servers use to discover available Outputs and how that differs between Bridge and Ready Outputs. My network is segmented into different VLANs for security. My ambition is to have all IoT devices (incl Roon Server and Roon Outputs) on an IoT VLAN and all personal computing devices (incl all Roon Controls) on the Default. All connections from Default to IoT are allowed but only established/related connections are allowed f…