Roon fails to initiate or control DAC device (ref#77TM07)

What’s happening?

· Other – My issue isn’t listed above

Describe the issue

Roon Loses Control of a DAC/Roon won't start the DAC Device

Describe your network setup

Topping D50s external DAC

Hello @Paulo_Chamie-Queiroz ,

Thanks for reaching out. Can you please confirm if a reboot of the Roon Server or the DAC triggers any change in behavior? When this issue occurs, is the DAC using the correct input? Sometimes USB cables can go bad, do you have another USB cable that you can try to use?

I have always used this DAC and nothing strange ever happened. Also nothing changed in my setup. Things have been funny with Roon since I updated my Mac to iOS26 Tahoe, like crashing many times before opening and now this. Thank you for reaching out

Hello @Paulo_Chamie-Queiroz ,

Yes, the crashing was a known issue that we have created a fix for, are you still seeing the crashes? We are looking into an issue on Tahoe with sample rate switches that can cause similar behavior, it sounds like you may also be affected by this, here is the main tracking thread:

If you use MUSE to resample everything to one sample rate, does the issue go away on your end?

I have not tried Muse. But I would rather be able to play the different sample rates, my DAC supports DSD 512 and up to 768kHz. And, I have many 96, 192 and 352.8 kHz files. I hope you can fix this bug soon

What “Fix” have you created?!

1 Like

It sounds like the OP is patiently navigating two known issues with Roon/Tahoe:

  1. the GUI is crashing. There is a fix for the first issue contained in the most recent release, build 1582. Please update per @noris’s suggestion to help with this one.

  2. the HAL isn’t initializing properly for generic/custom USB class-two audio devices with Roon during sample rate transitions. This is a deeper issue and concerns coreaudio discrepancies introduced by Apple with Tahoe. This fix requires more serious intervention by the team and potential involvement from Apple.

Please refer to the main tracking thread shared by @noris for announcements from the team concerning the second issue.

For housekeeping purposes and to keep responses in one thread, we’ll be closing this thread.