Please let us start with correct statements. The driver does support Wasapi in Windows 10. But the driver lacks the capability to let applications change the sample rate, so you have to manually do this in the driver's Settings dialog. This is caused by the driver being capable of multi-channel, multi-client WDM/ASIO operation as well as multi-interface usage. The driver was not designed and built to support just two channels of playback.

And this will not change. Please use ASIO for automatic sample rate changes.

ASIO also has the advantage to support sample rates above 384 kHz, not screwing up Windows' Audio Enhancements above 192 kHz sample rate, and not needing workarounds to support higher DSD rates by packing more data into half the sample rate (768 kHz = DSD256).

Found this thread while trying to figure out how to make my sample rate on the ADI2 while using Windows match the sample rate of the source material ... how do I "use ASIO for automatic sample rate changes?"

Thanks very much

Dear MC, I need the automatic sample rate, but have to use Windows Server 2016 which does not include "usbaudio2" driver, while technically this OS is one of Win10 versions. Is there any way to download and install the USB Audio 2.0 Class Compliant driver to WS2016? I tried to pull the files from a donor Win10, it did not work. Other consumer/audiophile vendors provide such driver.

I use jriver + ADI-2 DAC myself, had the same problem which is caused by the presence of the ASIO driver.

You must remove the RME ASIO driver completely, i.e. uninstall and then remove the ADI-2 from device manager (Gerätemanager). Do a search for new devices thereafter and everything will be ok using ASIO. If you pm me your email I weill send you screenshots of jriver settings, though it is difficult to go wrong there.

Thanks for thoughts, however, it was a fresh Win10 laptop without any RME drivers.

Just checked my other DAC is Amanero based, there are thousands of these made in China. When using Amanero's driver, there is no distortion on any frequency / bit depth when playing thru WASAPI Event. When playing with the same settings with standard windows diriver, there is a distortion on freqs more than 44k.

Another notice is that ADI-2 DAC while using Windows Driver occasionally gots stuck on some freq and it cannot be changed in Windows "default frequency dialog", while my other DAC with the same Windows driver does not have such behavior.

I really appreciate the ADI-2 DAC hardware, however dealing with its software 'features' like no automatic freq with RME driver and strange glitches with Windows driver are not enjoying.

Hi Argon. I think I have a solution for you for WS2016 involving ASIO as suggested by MC.

You can install the RME driver (which includes the ASIO driver). Then you can make any software 'support' ASIO by using Hi-Fi CABLE & ASIO Bridge ( download link halfway down this page https://www.vb-audio.com/Cable/index.htm ) . Then you select ASIO MADIface USB as the ASIO Device in the the VB-Audio ASIO Bridge / Hi-Fi Cable Control Panel. Then in whatever player software you are using (Tidal, etc.) you select the Hi-Fi Cable Input device as the audio device with exclusive/WASAPI mode.

This should also work on your Windows 10 laptop. It is working for me in Windows 10.

Regarding your other posts about Usbaudio2 driver, I too am having weird behaviour with the ADI2-DAC in Windows 10 with the Usbaudio2 driver. I'll post about it later.

Thank you for an interesting idea. I also want to try Sonarworks true-fi and already scared imagining how it could behave with ADI-2 driver which does not support automatic sample rate except ASIO mode... Will see...

I'm sure RME devs will appreciate your info. In software industry you cannot underestimate the value of constructive user feedback and consistent reproduction steps.

Here are the results of my troubleshooting using the ADI-2 DAC and Windows 10 with the Windows UAC2 driver.

I emailed RME support about this recently but since this thread is active and I've done some more troubleshooting since then I thought I would post here.

When I refer to the 'sound control panel' below, I mean the menu that you navigate to by going to Control Panel -> Hardware and Sound -> Sound -> selecting the ADI-2 DAC in the Playback panel -> clicking on Properties -> clicking on the Advanced tab

PC 1 (HP N36L running Windows 10 Pro):

- using Win10 version 1803 - sound control panel shows eight 32 bit sample rates ranging from 44.1 kHz to 384 kHz.

- clean install to version 1809 - same result as version 1803

- clean install to version 1903 - sound control panel shows 44.1 kHz and 48kHz (both 32 bit). Playing a test sound with 44.1kHz works but playing a test sound with 48kHz does not work and Windows then removes 48kHz as an option

(- Win 10 version 1903 using a DAC with Amanero USB and Windows UAC2 drivers  - sound control panel shows eight 32 bit sample rates ranging from 44.1 kHz to 384 kHz.)

PC 2 (HP Spectre X2 running Windows 10 Home):

- using Win10 version 1803 - same as PC 1 with 1803

- upgrade to Win10 version 1903 - sound control panel only ever showed 32 bit 44.1kHz

(-  Win 10 version 1903 using a DAC with Amanero USB and Windows UAC 2 drivers - same as PC 1 using the Amanero USB DAC)

PC 3 (Computer using a z390 chipset motherboard running Windows 10 Pro):

- Windows 10 version 1903 - same as PC 1 using version 1903

- downgrade to Win 10 version 1809 - same as PC 1 using version 1903

(-  Win 10 version 1903 using a DAC with Amanero USB and Windows UAC 2 drivers - same as PC 1 using the Amanero USB DAC)

I did some more playing around with PC 3 and the ADI-2 DAC. One odd thing I found is that if I play an 88.2 kHz file in JRiver Media Center in WASAPI mode it works and the sample rate does show 88.2 kHz on the DAC. But more oddly, after doing that, if I go in to the sound control panel it then shows all eight 32 bit sample rates ranging from 44.1 kHz to 384 kHz (which all work with the test sound). But then if I turn the DAC off and on again the sound control panel goes back to only showing 32 bit 44.1kHz.

Given the behaviour of the Amanero USB DAC and JRiver described above, I'd like to suggest there is something flakey with how the ADI-2 DAC works with Windows 10 UAC2 at least in version 1903.

Thanks from me as well! So it looks like MS screwed 1903 (no surprise), and we have to find out if it will stay this way (which means we have to find a fix) or will be fixed by MS later on. But first I will verify your findings on a 'non-RME' machine with 1903.

The fact that JRiver can make it work until reboot strongly points to MS, though, because our hardware doesn't change (it's not dynamically changing its properties).

Is this why several apps can mix into a stream even Exclusive mode is used?

Even I get sample rate switch when using VB-Audio driver on Tidal, or ASIO (with DSD) on Foobar, im not sure if drivers are doing re-sampling: I play 96k song in tidal/foobat, Win plays its OS sounds, they all mix and I can hear both - what and how does that happen, was my tidal/foobar audio stream mixed with OS sounds and resampled?

And WDM only playback on Win10 1903 is not working at all for me, I need MADIface.

Can we vote for special 2 channel only playback driver mode optimized for HIFI usage? Most audiophiles do not need multi client and multi channel capabilities, just a bit perfect (no up/down sampling) and sample rate change capability? Pretty please:)?

I am on the same Windows build and the same driver gets loaded for both the ADI-2 DAC and the Amanero USB DAC.

Here are some screenshots just so you don't think I'm trying to perpetrate some bizarre ruse:
https://imgur.com/a/DKPvpbU

Picture 1 shows all those driver/OS details and the Default Format dialog greyed out.

Picture 2 shows the JRiver behaviour I described. 88.2kHz file playing even though only 44.1kHz is available in Default Format

Picture 3 shows that you can close the Properties menu while that same song is still playing, open the Properties menu again and all the sample rates are now shown.

Picture 4 shows that this behaviour with JRiver cannot be reliably produced. Sometimes (and I can't discern what conditions have changed) JRiver just complains that 88.2kHz is not a supported format.

I am stumped. If you think there is something else I can check (event logs?) please let me know. But, if no one else is experiencing this issue, it is probably not worth pursuing for me personally. Now that I've discovered Tidal doesn't appear to do exclusive mode if the only rate supported by the driver is 32 bit (which is all UAC2 seems to provide?), I wouldn't use UAC2 even if it was working properly. I'll stick with using the optical out of my motherboard or the ASIO Bridge solution mentioned above to get the 16 bit and 24 bit rates available that Tidal needs.

Thanks for looking in to it, anyway.

Thanks for that.

Pic 1. In that example, the dialog is always greyed out whether there is anything playing or not because there is nothing else to select in that drop down box.

Pic 4. As far as I can tell, the conditions in this example are exactly the same as for pic 1 i.e. there is nothing else playing when I try to play the song in JRiver. So there shouldn't be anything blocking the playback engine.

I guess there must be some other software difference that I don't know how to ascertain in my 3 Win10 systems that is stuffing things up. My ADI-2 DAC works fine on my MacBook without RME drivers with the latest OS updates so I don't think there is something wrong with my particular unit.

(The Media Room Video device is just the name I gave to the Chromecast connected to the TV in another room. I don't know why it shows up in that PC's device manager.)

Anyway, please don't spend any more time on this issue on my account. Given I don't intend to use UAC2 in Windows any more, it is all a bit academic.