Jump to content
  • The Computer Audiophile
    The Computer Audiophile

    This Just In: Microsoft Launches Native Class 2 USB Audio Support. Wait, What?

    It's a bummer that headline is from 2017. Apple released a good working version of class 2 USB audio support on June 15, 2010 with Snow Leopard 10.6.4. Linux has supported UAC2 for ages as well. I guess it isn't surprising though, given the word on the street about Microsoft's Windows audio team. Sometimes there's one guy on the team who really gets this stuff, other times the whole team has pretty much left, etc... Sorry to burst your bubble if you had visions of a well-oiled Windows audio team with vast knowledge and interest in ... audio. 

     

    This news is still nice to read, but is it too little too late? For the most part it's a good thing, but it won't change anyone's life like the same announcement would have back in the first decade of the 2000s.


    What Is It, Do I Need It, and How Do I Get It

     

    What is USB audio class 2 support? In the simplest terms, UAC2 support, as it's known to some, is what enables you to play high resolution audio to a USB DAC without the need for additional software / drivers. To be precise, class 1 USB audio support enables playback of PCM music up through 24 bit / 96 kHz. Class 2 support enables much higher sample rates such as PCM 24 bit / 384 kHz and DSD (DoP) up through DSD256. It may support higher sample rates, but I have no way of testing anything higher at the moment. 

    Windows has supported class 1 USB audio "forever."  This is why early USB DACs were plug and play. Remember when CEntrance licensed its adaptive USB technology to several manufacturers back in the day? This enabled us to play up to 24/96 on Windows, and we didn't need to install any custom drivers. 

     

    When high speed USB audio came to the HiFi market, everyone using Windows had to install third party drivers. Many of these drivers were from Thesycon for XMOS based implementations or even M2Tech for all the companies that licensed its technology. With third party drivers also came the pains of keeping up with technology changes. HiFi companies had to keep drivers updated whenever new operating systems were released or even a minor update that caused something to stop working. Many members of the CA community are well aware of the pitfalls of third party drivers and waiting for a HiFi manufacturer to fix a software issue. I don't blame anyone here. HiFi manufacturers have always been hardware guys, so this is new territory. 

    Now, Windows 10 features native support for class 2 USB audio. Plug in a USB DAC, and you'll be able to play high resolution audio without installing anything. Of course this won't work for every DAC in the planet. 


    Do I Need It?

    If you use Windows and your DAC is working, then no you don't need it. You may want it though. In the future, HiFI companies may elect to not release custom drivers and to depend on the native class 2 USB audio support from all major operating systems Windows, macOS, and Linux. At such time, you'll need it.


    How Do I Get It?

    Currently, you need the Windows 10 Creators Update. This is a free update. Microsoft has seen some issues with the update and has held off from pushing it to everyone through Windows Update. If you want to install this, manually go to the Windows 10 Creators Update download site here - link.


    Wrap Up

    Again, this would have been big news back in 2009. Today many people have moved on to Linux based systems or network based systems. People using Windows 10 for playback should be happy that there is another option. They no longer have to depend on HiFi manufacturers to release updates to software (for the most part). Windows 10 UAC2 support is via WASAPI, not ASIO. Those of you who demand ASIO are out of luck. 


     




    User Feedback

    Recommended Comments



    Hi, Chris,

     

    I have enjoyed reading your reviews of the Berkeley Alpha DAC and Alpha USB, and have read that you presently use their Reference DAC.  Berkeley provides a custom USB driver for use with a Windows PC.  

     

    In your opinion, do you believe the new Windows 10 USB audio class 2 driver would offer an audio performance upgrade over the Berkeley-provided driver?  Your thoughts on this are appreciated.

     

    Possibly others on this forum use Berkeley DAC's and Alpha USB converters, have used the new Windows driver, and can comment.

     

     

    Share this comment


    Link to comment
    Share on other sites

    27 minutes ago, csx31 said:

    Hi, Chris,

     

    I have enjoyed reading your reviews of the Berkeley Alpha DAC and Alpha USB, and have read that you presently use their Reference DAC.  Berkeley provides a custom USB driver for use with a Windows PC.  

     

    In your opinion, do you believe the new Windows 10 USB audio class 2 driver would offer an audio performance upgrade over the Berkeley-provided driver?  Your thoughts on this are appreciated.

     

    Possibly others on this forum use Berkeley DAC's and Alpha USB converters, have used the new Windows driver, and can comment.

     

     

     

    I don't believe there should be an audio performance upgrade, but I'm guessing it may work better. The manufacturer supplied driver i really old and has to be massaged just to get it installed on Windows 10.

    Share this comment


    Link to comment
    Share on other sites

    "There is no such thing as a class driver specification."

    Sorry mansr but you are manifestly wrong on this crucial point: please see ...

    http://www.usb.org/developers/docs/devclass_docs/

    Note just one title from this International Standards body:

    "APPROVED CLASS SPECIFICATION DOCUMENTS"

    Share this comment


    Link to comment
    Share on other sites

    For those who are concerned about the impact of upgrading to a new version of Windows 10 I refer back to my post with the Powershell command:

    Export-WindowsDriver -Online -Destination D:\DriverBackup

    Good practice (or should I say 'sound' practice, get it?) might be to run this command from a working Windows 10 installation before upgrading ... and if the upgrade disturbs working drivers, then re-install from the old configuration in the backup folder.

    Share this comment


    Link to comment
    Share on other sites

    Although one might want to delay upgrading to the Windows 10 Creators Update ...

    ... once you've got there, Microsoft have extended the ability to control further changes:

    http://www.intowindows.com/how-to-delay-or-defer-updates-up-to-365-days-in-windows-10/

    Don't forget too that you can rollback to the previous installation if you don't like the upgrade result.

     

    My view is that one should be looking to upgrade ... but at a convenient time (now better supported) ... since MSFT are improving Windows 10 free of charge. Consider for example that flac support came with the first version of W10, and now USB class 2 audio with the Creator's Update. If the audio industry decides to add functionality in web browsers then it is a pound to a penny that MSFT will deliver this via Edge and other newbies via Groove.

     

    It's hypocritical to lambast MSFT for not supporting flac or USB audio class 2 ... if you then say you aren't prepared to upgrade for free!

     

    That doesn't mean you should jump off a cliff ... but recent changes to updating make the upgrade process more convenient and manageable. Since I enjoy a lot of computing I treat maintenance of my PC's as regularly as the maintenance of my house, car, ...

    Share this comment


    Link to comment
    Share on other sites

    1 hour ago, JackoUK said:

    "There is no such thing as a class driver specification."

    Sorry mansr but you are manifestly wrong on this crucial point: please see ...

    http://www.usb.org/developers/docs/devclass_docs/

    Note just one title from this International Standards body:

    "APPROVED CLASS SPECIFICATION DOCUMENTS"

    That's all about hardware, the thing you connect to a USB port. Drivers are software.

    Share this comment


    Link to comment
    Share on other sites

    "In your opinion, do you believe the new Windows 10 USB audio class 2 driver would offer an audio performance upgrade over the Berkeley-provided driver?"

     

    As I have been trying to persuade another contributor the IT theory is that class drivers are interoperable: one can switch them without any effect whatsoever.

     

    However we are talking about 2 companies developing a piece of software (the driver) ... and every piece of software contains errors. Most likely Berkeley subcontracted the development of the driver to a software house. So the question is "Did the subcontracted software house do a better job than Microsoft?"

    Answer: <your opinion here>.... or would it be better to try a test or two?

     

    My guess is:

    - your CD laser has read the next PCM 16-bit digital sample as 0000000000101011 (that should have been decimal 42 but it's actually 43 because you have dust on the CD)

    - the error correcting process in your CD software has corrected this to 0000000000101010

    - your music player software has called WASAPI or ASIO code and asked it to transfer the value 0000000000101010  without alteration to the USB audio driver

    - the USB audio driver has sent 0000000000101010 to your DAC

    - your DAC plays 0000000000101010 at the right time because it is pretty good

    Some errors occur on the way now and then ... but you never hear them ... in the same way that when you attend a live concert the performers are so good that even when they make a mistake you at not knowledgeable or attentive enough to notice them ... or you do on rare occasions and ... so what?

     

    0000000000101011

    0000000000101010

    0000000000101010

    0000000000101010

    0000000000101010

     

    What performance upgrade can you do to 0000000000101010 ?

     

    [OK, so I have over-egged the process.]

     

    OTOH ... maybe you know something about the subcontractor software development team used by Berkeley or the team MSFT used for UAC2?

     

     

     

    Share this comment


    Link to comment
    Share on other sites

    1 hour ago, JackoUK said:

    My view is that one should be looking to upgrade

    The fix released on 5/9 that made HQPlayer crash was a quality (security) update, not a feature update like Creators Update.  Quality updates can only be deferred for 30 days.  Feature updates can be deferred up to 365 days.

     

    A lot of the new features in Windows 10 are incomplete and buggy.  Microsoft is rolling out a lot of infrastructure that they haven't even exploited yet.  The recently announced fall Creators Update gives you a good idea of where they are trying to go.  

     

    I agree with you for general computing requirements, but not so much on a PC primarily used for audio.

    Share this comment


    Link to comment
    Share on other sites

    3 hours ago, JackoUK said:

    "In your opinion, do you believe the new Windows 10 USB audio class 2 driver would offer an audio performance upgrade over the Berkeley-provided driver?"

     

    As I have been trying to persuade another contributor the IT theory is that class drivers are interoperable: one can switch them without any effect whatsoever.

     

    However we are talking about 2 companies developing a piece of software (the driver) ... and every piece of software contains errors. Most likely Berkeley subcontracted the development of the driver to a software house. So the question is "Did the subcontracted software house do a better job than Microsoft?"

    Answer: <your opinion here>.... or would it be better to try a test or two?

     

    My guess is:

    - your CD laser has read the next PCM 16-bit digital sample as 0000000000101011 (that should have been decimal 42 but it's actually 43 because you have dust on the CD)

    - the error correcting process in your CD software has corrected this to 0000000000101010

    - your music player software has called WASAPI or ASIO code and asked it to transfer the value 0000000000101010  without alteration to the USB audio driver

    - the USB audio driver has sent 0000000000101010 to your DAC

    - your DAC plays 0000000000101010 at the right time because it is pretty good

    Some errors occur on the way now and then ... but you never hear them ... in the same way that when you attend a live concert the performers are so good that even when they make a mistake you at not knowledgeable or attentive enough to notice them ... or you do on rare occasions and ... so what?

     

    0000000000101011

    0000000000101010

    0000000000101010

    0000000000101010

    0000000000101010

     

    What performance upgrade can you do to 0000000000101010 ?

     

    [OK, so I have over-egged the process.]

     

    OTOH ... maybe you know something about the subcontractor software development team used by Berkeley or the team MSFT used for UAC2?

     

     

     

     

    The company is called Thesycon and it has done drivers for many companies. 

     

    I'm not sure what you are trying to say with your example.

    Share this comment


    Link to comment
    Share on other sites

    This Microsoft UAC2 driver is not as "universal" as I was led to believe.  So far, two of my DACs don't work with this driver:

     

    * Schiit Yggdrasil - I have a post about this

     

    * Anedio D2 - No yellow bang in Device Manager so driver loaded OK, but both Foobar2000 and HQPlayer choked up trying to play any track in WASAPI mode.

     

    For both these DACs, the manufacturer supplied Windows driver represents the only working driver option.

     

    Share this comment


    Link to comment
    Share on other sites

    5 hours ago, scan80269 said:

    This Microsoft UAC2 driver is not as "universal" as I was led to believe.  So far, two of my DACs don't work with this driver:

     

    * Schiit Yggdrasil - I have a post about this

     

    * Anedio D2 - No yellow bang in Device Manager so driver loaded OK, but both Foobar2000 and HQPlayer choked up trying to play any track in WASAPI mode.

     

    For both these DACs, the manufacturer supplied Windows driver represents the only working driver option.

    Add Steinberg UR242 to that list. The device is displayed in the control panel and applications, but it doesn't work at all.

    Share this comment


    Link to comment
    Share on other sites

    Working fine so far with the Ayre Codex.  PCM and DSD DOP.

    Share this comment


    Link to comment
    Share on other sites

    Worked fine for my Wyred 4 Sound Dac2v2SE. However I started getting clicking sounds from my ripped SACD's? I've read about that before but never experienced it. Switched back to ASIO and it plays fine again. Anyone have an answer?

    Share this comment


    Link to comment
    Share on other sites

    1 hour ago, KDinsmore said:

    Worked fine for my Wyred 4 Sound Dac2v2SE. However I started getting clicking sounds from my ripped SACD's? I've read about that before but never experienced it. Switched back to ASIO and it plays fine again. Anyone have an answer?

    What format are you playing your SACD rips in?

    Share this comment


    Link to comment
    Share on other sites

    Hi Chris,

    JRiver latest version.

     

    Keith

    Share this comment


    Link to comment
    Share on other sites

    Hi Bala - Thanks so much for posting here at CA. We value open communication between our community and developers / manufacturers.

     

    Thanks for the links as well. Good stuff. 

    Share this comment


    Link to comment
    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




×
×
  • Create New...