ARC unfortunately still crashes with Google Pixel 7 Pro phone and Focal Bathys in DAC mode even with the new update (1.0.40) that supposedly fixes this issue:
Fixed a potential crash in ARC when connecting certain USB DACs
To narrow it down:
Crash is immediately when UBS beta driver is enabled and the Bathys is connected
It works fine when USB beta driver is not enabled.
USB beta driver works with Bathys in DAC mode on a Oneplus 8 Pro Android phone.
Latest ARC, Pixel 6 Pro, iFi DAC/amps (iDSD nano Black Label and iDSD Diablo). Beta driver runs for around 20 sec, loses contact with the USB device. Only way to restart is to unplug and plugh back again. Crashes again after a short period. No issues with beta driver off, but SQ is quite a bit worse.
Hi @brian ,
Yes, mine still the same, it crashed a few seconds after I plug in the AK-HC2. I don’t understand why this DAC was working fine in previous version when beta USB driver was released and now it no longer work anymore?
Lucky I’ve the iFi Go Bar works without any issue. Probably it uses XMOS chipset for USB audio?
We pushed a fix with the most recent release for the ARC regression introduced with MUSE that causes a crash with certain USB DACs. The fix was not nearly as comprehensive as we expected; some USB DACs are still going to crash ARC, unfortunately.
Temporarily disabling MUSE may resolve these symptoms, but this is something we’ll have to do for your account on the backend.
If you don’t rely on DSP and would like to volunteer, please reach out here. Our QA team will disable this feature temporarily, quarantining the component of ARC that is breaking USB drivers.
We understand and feel your frustration and we’re working to get this resolved as quickly as you’d expect.
I’ve merged your post into a tracking thread. You’re unfortunately encountering a known issue that we’ve only partially resolved with the most recent release of Roon/ARC. Please see my above comments for a potential path to a workaround, and we’ll keep posting updates here with the progress of the work to resolve this issue. Thanks!
Thanks for volunteering! We’re going to collect a few more in other threads before QA disables the MUSE feature - stand by and we’ll let you know as soon as we’ve flipped the switch.
If you have a) new symptoms or b) new technical details to provide, please post in that thread accordingly. Have faith that your frustration is reflected in the urgency of our internal efforts.
Note that we’ve concluded disabling MUSE is not going to restore functionality. We had initially thought this might be a workaround, but further investigation has disproven that notion. This crash concerns elements of DAC connectivity that are independent of MUSE, although the issue happened to coincide with the release of that feature.