OK. But for most people, WASAPI is more stable than Kernel streaming. WASAPI Exclusive is the modern API that Microsoft actively supports and that audio devices are tested with nowadays. It’s also a simpler API than WDM-KS (i.e. kernel streaming). This means applications using WASAPI Exclusive are less likely to have bugs where they’re using the API incorrectly.
What do you mean by WASAPI Exclusive? I have exclusive mode enabled in driver properties, advanced tab, both checkbox checked. And in AS I can select WASAPI on Audio tab. Is this or something else?
You set exclusive mode via the Windows’ Sound Control Panel:
Exclusive mode can be set for ASIO or WASAPI. I don’t know if the same is true for kernel streaming.
1 Like
Yes, that’s what I wanted to say, thanks. For me, as I said, Kernel is best. I had some problems with WASAPI, with AS/foobar, Realtek/external dac. Sometimes the music sounds strange, the sound is altered, very bad. When I press stop and then play everything is ok again. Strange. With Kernel or ASIO no problems.
1 Like
So it seems that there have been an issue with MQA identification and we have made a fix for it.
For everyone having this issue, please try the test version you can find here
3 Likes
Thank you @Antoine . I can confirm with this test version the output of the original 16bit/44.1kHz is correctly identified as MQA and the magenta light on my DAC is turned on.
Just one thing: the output audio stream is displayed as 24bit/44.1kHz instead of the original 16-bit.
2 Likes
Since you have a MQA Renderer, the first unfolding is done in Audirvana, and no other audio processing is done as the DAC is doing the other unfolding. But the unfolded of the signal need to be sent in 24 bits to convey all the MQA data.
2 Likes