USB Audio 2.0 Drivers
Starting with Windows 10, release 1703, a USB Audio 2.0 driver is shipped with Windows. It is designed to support the USB Audio 2.0 device class. The driver is a WaveRT audio port class miniport. For more information about the USB Audio 2.0 device class, see https://www.usb.org/documents?search=&type%5B0%5D=55&items_per_page=50.
The driver is named: usbaudio2.sys and the associated inf file is usbaudio2.inf.
The driver will identify in device manager as «USB Audio Class 2 Device.» This name will be overwritten with a USB Product string, if it is available.
The driver is automatically enabled when a compatible device is attached to the system. However, if a third-party driver exists on the system or Windows Update, that driver will be installed and override the class driver.
Architecture
USBAudio.Sys fits within the wider architecture of Windows USB Audio as shown.
Related USB specifications
The following USB specifications define USB Audio and are referenced in this topic.
- USB-2 refers to the Universal Serial Bus Specification, Revision 2.0
- ADC-2 refers to the USB Device Class Definition for Audio Devices, Release 2.0.
- FMT-2 refers to the Audio Data Formats specification, Release 2.0.
The USB-IF is a special interest group that maintains the Official USB Specification, test specifications and tools.
Audio formats
The driver supports the formats listed below. An alternate setting which specifies another format defined in FMT-2, or an unknown format, will be ignored.
Type I formats (FMT-2 2.3.1):
- PCM Format with 8..32 bits per sample (FMT20 2.3.1.7.1)
- PCM8 Format (FMT-2 2.3.1.7.2)
- IEEE_FLOAT Format (FMT-2 2.3.1.7.3)
Type III formats (FMT-2 2.3.3 and A.2.3):
- IEC61937_AC-3
- IEC61937_MPEG-2_AAC_ADTS
- IEC61937_DTS-I
- IEC61937_DTS-II
- IEC61937_DTS-III
- TYPE_III_WMA
Feature descriptions
This section describes the features of the of the USB Audio 2.0 driver.
Audio function topology
The driver supports all entity types defined in ADC-2 3.13.
Each Terminal Entity must have a valid clock connection in compatible USB Audio 2.0 hardware. The clock path may optionally include Clock Multiplier and Clock Selector units and must end in a Clock Source Entity.
The driver supports one single clock source only. If a device implements multiple clock source entities and a clock selector, then the driver will use the clock source that is selected by default and will not modify the clock selector’s position.
A Processing Unit (ADC-2 3.13.9) with more than one input pin is not supported.
An Extension Unit (ADC-2 3.13.10) with more than one input pin is not supported.
Cyclic paths in the topology are not allowed.
Audio streaming
The driver supports the following endpoint synchronization types (USB-2 5.12.4.1):
- Asynchronous IN and OUT
- Synchronous IN and OUT
- Adaptive IN and OUT
For the asynchronous OUT case the driver supports explicit feedback only. A feedback endpoint must be implemented in the respective alternate setting of the AS interface. The driver does not support implicit feedback.
There is currently limited support for devices using a shared clock for multiple endpoints.
For the Adaptive IN case the driver does not support a feedforward endpoint. If such an endpoint is present in the alternate setting, it will be ignored. The driver handles the Adaptive IN stream in the same way as an Asynchronous IN stream.
The size of isochronous packets created by the device must be within the limits specified in FMT-2.0 section 2.3.1.1. This means that the deviation of actual packet size from nominal size must not exceed +/- one audio slot (audio slot = channel count samples).
Descriptors
An audio function must implement exactly one AudioControl Interface Descriptor (ADC-2 4.7) and one or more AudioStreaming Interface Descriptors (ADC-2 4.9). A function with an audio control interface but no streaming interface is not supported.
The driver supports all descriptor types defined in ADC20, section 4. The following subsections provide comments on some specific descriptor types.
Class-Specific AS interface descriptor
For details on this specification, refer to ADC-2 4.9.2.
An AS interface descriptor must start with alternate setting zero with no endpoint (no bandwidth consumption) and further alternate settings must be specified in ascending order in compatible USB Audio 2.0 hardware.
An alternate setting with a format that is not supported by the driver will be ignored.
Each non-zero alternate setting must specify an isochronous data endpoint, and optionally a feedback endpoint. A non-zero alternate setting without any endpoint is not supported.
The bTerminalLink field must refer to a Terminal Entity in the topology and its value must be identical in all alternate settings of an AS interface.
The bFormatType field in the AS interface descriptor must be identical to bFormatType specified in the Format Type Descriptor (FMT-2 2.3.1.6).
For Type I formats, exactly one bit must be set to one in the bmFormats field of the AS interface descriptor. Otherwise, the format will be ignored by the driver.
To save bus bandwidth, one AS interface can implement multiple alternate settings with the same format (in terms of bNrChannels and AS Format Type Descriptor) but different wMaxPacketSize values in the isochronous data endpoint descriptor. For a given sample rate, the driver selects the alternate setting with the smallest wMaxPacketSize that can fulfill the data rate requirements.
Type I format type descriptor
For details on this specification, refer to FMT-2 2.3.1.6.
The following restrictions apply:
Format | Subslot size | Bit resolution | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Type I PCM format: | 1 = terminal ID (As defined in the descriptor) Convention for and is:
T1_NrJacks, T1_J2_ChannelMapping, T1_J2_ConnectorType For additional audio jack information, see KSJACK_DESCRIPTION structure. These registry values can be set in various ways: By using custom INFs which wrap the in-box INF for the purpose to set these values. Directly by the h/w device via a Microsoft OS Descriptors for USB devices (see example below). For more information about creating these descriptors, see Microsoft OS Descriptors for USB Devices. Microsoft OS Descriptors for USB ExampleThe following Microsoft OS Descriptors for USB example contains the channel mapping and color for one jack. The example is for a non-composite device with single feature descriptor. The IHV vendor should extend it to contain any other information for the jack description. TroubleshootingIf the driver does not start, the system event log should be checked. The driver logs events which indicate the reason for the failure. Similarly, audio logs can be manually collected following the steps described in this blog entry. If the failure may indicate a driver problem, please report it using the Feedback Hub described below, and include the logs. For information on how to read logs for the USB Audio 2.0 class driver using supplemental TMF files, see this blog entry. For general information on working with TMF files, see Displaying a Trace Log with a TMF File. For information on «Audio services not responding» error and USB audio device does not work in Windows 10 version 1703 see, USB Audio Not Playing Feedback HubIf you run into a problem with this driver, collect audio logs and then follow steps outlined in this blog entry to bring it to our attention via the Feedback Hub. Driver developmentThis USB Audio 2.0 class driver was developed by Thesycon and is supported by Microsoft. C-Media USB Multi-Channel Audio Device Driver 7.12.8.2140 for Windows 7 64-bitDescriptionFree DownloadThe package provides the installation files for C-Media USB Multi-Channel Audio Device Driver version 7.12.8.2140. If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version. Take into consideration that is not recommended to install the driver on Operating Systems other than stated ones. In order to manually update your driver, follow the steps below (the next steps): 1. Extract the .cab file to a folder of your choice About Sound Card Driver:Usually, Windows operating systems apply a generic audio driver that allows computers to recognize the sound card component and make use of its basic functions. When enabled by proper files, the characteristics of the sound card (like model, manufacturer, number of channels) are completely available to computers, and all its features are made accessible. Updating the audio version can improve sound quality, resolve different compatibility issues, fix related errors spotted throughout the product’s usage, add support for new operating systems, and bring various other changes. As for applying this package, the steps are quite simple since each producer intends to uncomplicate things for users: just download the package, run the setup, and follow the on-screen instructions. Bear in mind that, even though other operating systems might be compatible as well, it is not recommend that you apply any software on platforms other than the specified ones. Also, when the installation has finished, do perform a restart to ensure that all changes take effect properly. Therefore, if you wish to install this audio version, click the download button and apply the package. Remember to check with our website as often as possible to stay “updated one minute ago.” It is highly recommended to always use the most recent driver version available. Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer. Usb Multi Channel Audio Device Driver DownloadUsb Multi Channel Audio Device Driver Details:Usb Multi Channel Audio Device File Name: usb_multi_channel_audio_device.zip Usb Multi Channel Audio Device Driver Version: 901.6Wi Usb Multi Channel Audio Device ZIP Size: 116.kb Usb Multi Channel Audio Device now has a special edition for these Windows versions: Windows 7, Windows 7 64 bit, Windows 7 32 bit, Windows 10, Windows 10 64 bit,, Windows 10 32 bit, Windows 8, Windows Vista Home Basic 32bit, Windows 10 64bit, Windows 7 Professional 64bit, Windows 7 Ultimate 64bit, Windows 10 Team 64bit, Windows 8 Pro 64bit, Windows 10 Pro 32bit, Windows 10 S 32bit, Windows 10 Home 64bit, Windows 10 Pro Education 32bit, Windows 7 Starter 64bit, Windows Vista Home Premium 32bit, Windows 7 Enterprise (Microsoft Windows NT) 32bit, Usb Multi Channel Audio Device Download Stats:Direct Download Success Stats:Reports Issued By 336/359 Users Success Reported By 91/336 Users Driver Download Score67/100 Driver Installation Score62/100 Overall preformance Score66/100 Installation Manager Success Stats:Reports Issued By 5241/5542 Users Success Reported By 4566/5241 Users Driver Download Score78/100 Driver Installation Score76/100 Overall preformance Score95/100 DOWNLOAD OPTIONS:1. Direct DownloadThis option requires basic OS understanding. 2. Driver Installation ManagerThis option requires no OS understanding. Other drivers most commonly associated with Usb Multi Channel Audio Device problems:Usb Multi Channel Audio Device may sometimes be at fault for other drivers ceasing to functionThese are the driver scans of 2 of our recent wiki members*Scan performed on 4/25/2019, Computer: Sony VGN-CR313H_B — Windows 7 64 bitOutdated or Corrupted drivers:7/20
Scan performed on 4/26/2019, Computer: Sony VGN-AW120D — Windows 7 32 bitOutdated or Corrupted drivers:8/18
Please Note: There are particular operating systems known to have problems with Usb Multi Channel Audio Device:
If you encounter problems with the direct download for these operating systems, please consult the driver download manager for the specific Usb Multi Channel Audio Device model. |