Our latest release (Build 918) contained some improvements in this area, for those impacted by this issue, can you please confirm if build 918 has helped your audio devices appear again? You can check to see which build you are on in Roon Settings → About.
Sadly I continue to have the same issue after updating to 918 and restarting. Neither of my 2 RoonReady DACs are available.
The console is reporting the following every 7 secs from ‘libsystem_network_dylib’:
“nw_path_close_fd Failed to close guarded necp fd 8 [9: Bad file descriptor]”
Sorry to hear that the update did not help, I’ve re-enabled logging for your affected Mac devices, can you please use them for at least a few minutes and then this post to know to check for the logs after you’ve done so? Thank you.
Hi Noris. Just a note that although I hearted your post, I am not really able to do anything with Roon other than browse. If I try to play a track I get an error saying, “No audio device selected!”
I can see and control as normal all the devices (other than the USB DAC connected to the roonserver) from the remote iMac/iPad/iPhone etc. I can stream from the roonserver (iMac) to all the other devices (remote iMac/iPads/iPhones/Sonos’s etc. All content local library (attached to roonserver) /Quboz/internet radio all works. Grouping of available devices works fine. All as normal.
*remote and roonserver iMacs are seperate machines.
I know the USB output on the roonserver is working because I can see it in the preferences/output menu. And I have Audirivana loaded (currently) on that machine and it works fine.
The only thing that’s not available/visible via all the roon remotes iMac/iPad/iPhone is the USB output on my roonserver (which is where my main system is connected). It’s not available/visible from all the Audio and the Zone pickers. In addition from Setup in Find Roon OS it doesn’t find the roon server/core?
The screen shots are missing the roonserver and it’s respective outputs including the USB output (formerly known as Denafrips).
All worked beautifully before the roon update.
Can we roll back the update to confirm that’s the problem?
Hey there. I realize this question is simplistic and quite likely off base, but since:
when I updated Roon to the build that broke the recognition of audio devices on the computer the core resides on, that machine was running Mac OS 10.12, and
now that I’ve upgraded it to 10.14, the audio devices are still not recognized,
is it possible that when the build was installed that OS 12.6 prevented some small piece of important code to be installed correctly, and that broke it as well as all subsequent updates?
If so, might the best course forward be to completely uninstall Roon on that machine and reinstall from scratch now that it’s running 10.14?
If so, what is the best way to do that so that I don’t lose all my custom input data? Is it as simple as creating a backup, uninstalling and reinstalling Roon, and importing that backup?
Also tried restoring from an old backup (build 898) and restarting everything. Same issue. @danny - I know this post was combined to include those of us having this issue due to 10.12.6, but since I have upgraded the server computer to 12.14 do you have any idea why this would be happening? Seems like updating should have fixed it if it was a bug with 10.12.6.
Thanks for letting us know that the issue is still the same. Can we please ask that you open Console.app, reproduce the issue by navigating to the Audio page on the affected Mac and then upload the log generated here and let us know?
As another test you can also perform a RAATServer refresh. You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
Just uploaded the Console log, but to be clear, you mean to run Console on any remote computer and navigate to the Manage Audio Devices page in Roon? I ask because the “affected” mac would really be the the core machine and I don’t run Roon on it, just Roon Server.