scan80269

USB Audio 2.0 Class Driver in latest Windows 10 RS2

Rate this topic

10 posts in this topic

The latest Microsoft Windows 10 Creators Update (a.k.a. Redstone2 or RS2) includes a new USB Audio 2.0 class driver, usbaudio2.sys.  This driver is an alternative to supplier-provided drivers for USB DACs.

 

I've tried running a few of my USB DACs with this OS and driver and they all seem to work properly, though unlike many supplier-provided drivers, the MS USB Audio 2.0 class driver does not appear to expose any user controls, such as buffer size.  When running a USB DAC with this inbox driver, I noticed there is an extra USB endpoint device, typically named "<DAC name> DFU".  For example, with my Cambridge Audio DACMagic XS, a "CA DFU" device shows up in Device Manager with a yellow bang.  I'm pretty sure this is a USB endpoint intended to support firmware updates (DFU = device firmware update) and can be safely ignored, though having a perpetual yellow bang device in Device Manager is a nuisance.

 

I have yet to do sonic comparisons between supplier-provided driver and this MS inbox USB Audio 2.0 class driver for the same DAC HW, but hope to get to this soon.

 

1

Share this post


Link to post
Share on other sites
2 hours ago, Dr Tone said:

What formats did you try?  PCM, DSD DOP etc?

Using the Microsoft USB Audio 2.0 driver with my Holo Audio Spring DAC, I successfully played PCM up to 384K, and up to DSD256 DoP..  I tested with HQPlayer in WASAPI mode, since this driver has no ASIO functionality.

 

0

Share this post


Link to post
Share on other sites

Win10 Creators  Update is expected to become downloadable from Windows Update starting on April 11.

 

I've successfully completed the OS update manually for several PCs, but on my ultrabook, access to files on a mapped network drive over wireless got badly messed up. I rolled back to Win10 RS1 to restore the functionality.  Not sure why only one PC was affected though.

 

0

Share this post


Link to post
Share on other sites

For my M2Tech Hiface Two USB converter, I replaced the M2Tech driver with the Microsoft driver.

 

At first, it seemed to work fine. I can play files (24/96 PCM) with Foobar2000, I hear sound.

 

But some things didn't work right. The track progress bar was stuck and didn't react, i.e. impossible to navigate within a track. The visualisations in Foobar2000 (VU meter, spectrum meter) didn't work.

 

I switched back to the M2Tech driver.

Edited by CatManDo
0

Share this post


Link to post
Share on other sites
On 9-4-2017 at 5:29 PM, CatManDo said:

For my M2Tech Hiface Two USB converter, I replaced the M2Tech driver with the Microsoft driver.

 

At first, it seemed to work fine. I can play files (24/96 PCM) with Foobar2000, I hear sound.

 

But some things didn't work right. The track progress bar was stuck and didn't react, i.e. impossible to navigate within a track. The visualisations in Foobar2000 (VU meter, spectrum meter) didn't work.

 

I switched back to the M2Tech driver.

 

I've got a CM6631A based USB>SPDIF unit based on USB class 2 and ik works perfect now. With the original driver I got nasty pops and clicks when switching between songs. When switching during a loud passage the buffer seems to be filled when switching so a loud click appears.

 

With this new driver it works perfect. In Event mode WASAPI I got the same problem you have. It does play but no visuals. In Push mode everything works fine. I already used push mode because event mode gave the loudest clicks/pops.

 

I'm very happy with this native driver!

Edited by Fairy
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now