Dual-booting Windows 10 and Linux Mangaro on the XMG 16 × AMD Ryzen 7 4800H with Radeon Graphics knows every audio device under WASAPI (Windows 10) and ALSA (Linux Manjaro).
Roon.exe (Windows RoonInstaller64-923) occasionally loses the ALSA devices. Incorrectly offers WASAPI Devices that can only run directly under Windows 10.
Uninstalling the Windows GUI and reinstalling it fixes it again.
This misbehavior could be partly responsible for other audio problems and crashes reported in the community, because if an audio device is not found, remains incorrectly assigned via IPs, there are crashes, title jumps or dropouts when streaming.
Sometimes incorrectly offers WASAPI Devices on XMG (this PC)
Info: Starting RAATServer v1.8 (build 923) stable on linuxx64
Trace: [RAATServer] detected ALSA support
Trace: [bits] myinfo: {“os”:“Linux 5.16.14 MANJARO”
…and the two ALSA devices (internal, USB-DAC ) are made ready for operation.
…many hundreds of error-free logs to ALSA and Sharkoon Mobile DAC, but no log about keywords like Pulse, WASAPI
My guess also goes in the direction of browsers and other music applications that might be in disruptive competition with the ALSA setup via the RAAT server.
Here it is Google Chrome and Foobar2000. Foobar2000 also runs via Wine with these OUTPUT devices:
Test: Restart of Roon while Foobar2000 is playing.
The Sharkoon Mobile DAC is not found because it is currently being used via Foobar2000. After Foobar2000 playback stop the DAC is found correct as Alsa device.
