But I found some differences against adding Virtual Audio Cable (Kernel Streaming) at front.ġ) When Virtual Audio Cable was not used and VB Hifi Cable was set as default audio device, I found that sample rate setting in device properties Advanced tab (you call it Windows Mixer) has influence. You are right that device volume setting has no influence. Yes I tried to set VB HiFi Cable as default output device and it functions with ASIO Bridge. Can you see if you still get DSD without Virtual Audio Cable? Since I posted I tried VB Audio Hifi Cable and got it to act so the Windows mixer audio volume control has no effect, leading me to believe that VB Aufio Hifi Cable bypasses the Windows audio stack.

These ASIO proxies allow to perform some digital signal processing before audio is sent to DAC.Īny reason not to just use VB Audio Hifi Cable from Windows Mixer out to foo_dsd_asio or Asio4All for that matter? I used foo_dsd_asio from Maxim Anisiutkin, but also JRiver Media Center ASIO device could be used. It means it is possible to pass bitperfect Windows audio from any Windows application to any ASIO device, including special ASIO proxies. Now I am playing video with 44.1k audio in Windows Media Player, my DAC control panel app shows 352800 (that's DoP sample rate corresponding to DSD128) and my DAC display shows DSD128. VB Audio HiFi cable and ASIO bridge from VB-Audio Virtual Apps Virtual Audio Cable as vladimirb0b suggested in OP I reached it by passing default output audio device to foo_dsd_asio ASIO proxy. I found a way to get DSD128 output from any Windows application (DSD128 is max. I got the idea to get things yet more complicated and to reach yet more!

Windows 10 virtual audio cable