As I mentioned, with Thesycon all of the various drivers for Windows all end up in the very same place, so the only reason to choose one over the other is for picking which Windows features you want. (e.g. fade in/out with Direct Sound.) As I mentioned, in general, ASIO drivers are used for low latency, e.g. audio editing, and are the usually the most twitchy and buggy drivers out there. But they have the reputation of keeping Windows from messing with the sound as much. With the Thesycon drivers that we use that’s not the case: you can have one device using ASIO and another WASAPI and they can be mixed together by the Windows audio stack. In Windows land after WASAPI came along there was no particular reason to use Kernel mode drivers. WASAPI is the replacement for kernel mode drivers and has the benefit of isolation from bugs in the kernel mode drivers affecting, well, the kernel. WASAPI also provides exclusive mode, etc. which give the control you need to guarantee bit perfect playing. Once again with Thesycon drivers you can get bit perfect playback with any Windows output method: ASIO, WASAPI, KS or Direct Sound. Of course if you are using the foobar2000 foo_input_sacd plugin and it’s ASIO proxy you need to use an ASIO driver if to play DSD. In, say, JRiver there’s no particular advantage to any particular Thesycon driver.
With Thesycon drivers putting ASIO4ALL in the mix can only lead to trouble and can’t really make anything sound better: the only real purpose of ASIO4ALL is to provide an ASIO interface when your hardware doesn’t have ASIO drivers. It doesn’t provide what’s expected from real ASIO drivers, namely low latency and (compared to the Thesycon ASIO drivers) can only add bugs. The buffering settings in ASIO4ALL are only for it. The drivers it vectors to still have their own buffering settings that ASIO4ALL doesn’t affect. Once again using ASIO4ALL can only lead to more bugs when talking about PS Audio audio drivers.
No we can’t have test builds of the drivers out there - customer support of Windows USB drivers is already hard enough and we will soon be providing a newer version anyway. And FWIW our current install doesn’t even install the control panel so it’s not just a question of enabling or disabling the control panel - it doesn’t exist in our system and if we put it back in we’d need to debug it, debug it’s installation, etc.
The things that make many other systems sound better don’t necessarily make the PS Audio drivers and hardware sound better - the Thesycon drivers all do the same things and run the same code under the covers and the DS and DS Junior both are much less sensitive to jitter from any source (that isn’t to say that the character of any EMI or other electrical pollution on your audio system won’t change with differing drivers, but those changes will likely be different than they are for other DACs.)