It indeed depends on what kind of driver you use. WASAPI and asio don't have that issue, standard MME or WDM drivers have this issue. WASAPI is now the best option, but not always availeble for your system and limites the audio out to one application only (as it uses direct kernel streaming). Asio is in general almost as good as WASAPI but is more flexible.
Glad to hear it. I've been tempting to try a pi + Moode but Windows UI seems much easier and more flexible, and better supported by the streaming Apps.
I think a proper future for audio would be industry movement towards a turnkey as easy to use as Sonos or KT receiver dedicated fanless device that could do all this (room measure, eq+convolution, all the streaming apps + DLNA, same streaming UI flexibility and layout as windows) headless from a tablet or cell, but the future of audio is stuck in the past. There's always Roon or JRiver but they still keep you stuck on an OS that pushes updates
Oh, I haven't seen that. As far as I can tell, Windows sound controls don't do anything to an ASIO stream. But this is certainly worth tsting. Wonder what would be an easy test?Regarding Windows 10, if an audio device is running ASIO drivers and is still assigned as "Default Sound Device" and or "Default Communication Device" then Windows still mucks with SQ.
Hm, ASIO and windows sound engine are different animals, I have never seen of heard of them working with each other. But both operate the same soundcard. It's perfectly possible the windows sound engine driver can take over the device before ASIO can claim it for itself. Or some fake ASIO driver which is just a COM shim on top of the standard windows driver (Asio4All?) can feed the stream through the windows internals.I assume it is Windows sound engine that is causing the problem, I have seen it resample PCM ASIO streams in the past when I had a sound card that displayed the received sample rate and bit-depth.