FlexASIO does not work well with Qobuz or my EF500 DAC/amp about flexasio HOT 2 OPEN

WASAPI exclusive mode is full of stutters no matter what the suggested latency and buffer size is.

Yeah, sadly, the WASAPI backend code could probably use some work. And the WDM-KS backend is in an even worse state I'm afraid, suffering from severe issues like PortAudio/portaudio#763.

When switching to WDM-KS mode, the first few times I would get bluescreens whenever I started to play audio giving me "WDF Violation."

This points to a bug in the Windows audio device driver. Userland code (which includes applications, and FlexASIO) cannot be held responsible for BSODs, although they can indirectly trigger them by surfacing pre-existing bugs in device drivers that do not correctly check userland inputs.

WDM-KS triggering bugs in drivers is not too surprising given WDM-KS allows apps to talk directly to device drivers, leaving them exposed to code paths that would not normally be taken when the audio device is being used in the "normal" way (i.e. through the standard Windows audio stack).

from flexasio.

WASAPI exclusive mode is full of stutters no matter what the suggested latency and buffer size is.

Yeah, sadly, the WASAPI backend code could probably use some work. And the WDM-KS backend is in an even worse state I'm afraid, suffering from severe issues like PortAudio/portaudio#763.

When switching to WDM-KS mode, the first few times I would get bluescreens whenever I started to play audio giving me "WDF Violation."

This points to a bug in the Windows audio device driver. Userland code (which includes applications, and FlexASIO) cannot be held responsible for BSODs, although they can indirectly trigger them by surfacing pre-existing bugs in device drivers that do not correctly check userland inputs.

WDM-KS triggering bugs in drivers is not too surprising given WDM-KS allows apps to talk directly to device drivers, leaving them exposed to code paths that would not normally be taken when the audio device is being used in the "normal" way (i.e. through the standard Windows audio stack).

Thank you for the reply! Also, yes, I'm not blaming the issue on you, and I understand the BSOD is caused by an issue with the driver. I just thought I would report this as I did not know if it has already been reported or not. I will e-mail the DAC developer and see if they plan on a proprietary driver as it currently uses a default Windows audio driver.

Thank you for the reply though. I appreciate it!

from flexasio.