- 5.1 Sound Card Driver Download
- Frontier Design Sound Cards & Media Devices Driver Download 64-bit
- Frontier Design Sound Cards & Media Devices Driver Downloads
- Frontier Design Sound Cards & Media Devices Driver Download Windows 7
- Frontier Design Sound Cards & Media Devices Driver Download Windows 10
- Frontier Design Sound Cards & Media Devices Driver Download
- Sound Card Driver Download
Bluetooth Speaker Driver free download - Bluetooth 2.0Broadcom Bluetooth Driver and Applicationv6.0.1.4900.zip, Bluetooth Driver 5.0.1.1400.zip, Bluetooth Driver. AMD is proud to power the graphics behind Apple's line of world-class workstations and mobile solutions, enabling artists and designers with the ability to create at the speed of their imagination. LG Software, Firmware, & Drivers Download: Optimize your LG devices by downloading the latest drivers and firmware updates. Keep your LG products up-to-date.
5.1 Sound Card Driver Download
FreeSync 2 HDR does not require HDR capable monitors; driver can set monitor in native mode when FreeSync 2 HDR supported HDR content is detected. Otherwise, HDR content requires that the system be configured with a fully HDR-ready content chain, including: graphics card, graphics driver and application.
-->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
usbaudio2.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 (FMT-2 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 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 ADC-2, 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 <= bSubslotSize <= 4 | 8 <= bBitResolution <= 32 |
| Type I PCM8 format: | bSubslotSize 1 | bBitResolution 8 |
| Type I IEEE_FLOAT format: | bSubslotSize 4 | bBitResolution 32 |
| Type III IEC61937 formats: | bSubslotSize 2 | bBitResolution 16 |
Class-Specific AS isochronous audio data endpoint descriptor
For details on this specification, refer to ADC-2 4.10.1.2.
The MaxPacketsOnly flag in the bmAttributes field is not supported and will be ignored.
The fields bmControls, bLockDelayUnits and wLockDelay will be ignored.
Class requests and interrupt data messages
The driver supports a subset of the control requests defined in ADC-2, section 5.2, and supports interrupt data messages (ADC-2 6.1) for some controls. The following table shows the subset that is implemented in the driver.
| Entity | Control | GET CUR | SET CUR | GET RANGE | INTERRUPT |
|---|---|---|---|---|---|
| Clock Source | Sampling Frequency Control | x | x | x | |
| Clock Selector | Clock Selector Control | x | |||
| Clock Multiplier | Numerator Control | x | |||
| Denominator Control | x | ||||
| Terminal | Connector Control | x | x | ||
| Mixer Unit | Mixer Control | x | x | x | |
| Selector Unit | Selector Control | x | x | ||
| Feature Unit | Mute Control | x | x | x | |
| Volume Control | x | x | x | x | |
| Automatic Gain Control | x | x | |||
| Effect Unit | – | ||||
| Processing Unit | – | ||||
| Extension Unit | – |
Additional information on the controls and requests is available in the following subsections.
Clock source entity
For details on this specification, refer to ADC-2 5.2.5.1.
At a minimum, a Clock Source Entity must implement Sampling Frequency Control GET RANGE and GET CUR requests (ADC-2 5.2.5.1.1) in compatible USB Audio 2.0 hardware.
The Sampling Frequency Control GET RANGE request returns a list of subranges (ADC-2 5.2.1). Each subrange describes a discrete frequency, or a frequency range. A discrete sampling frequency must be expressed by setting MIN and MAX fields to the respective frequency and RES to zero. Individual subranges must not overlap. If a subrange overlaps a previous one, it will be ignored by the driver.
A Clock Source Entity which implements one single fixed frequency only does not need to implement Sampling Frequency Control SET CUR. It implements GET CUR which returns the fixed frequency, and it implements GET RANGE which reports one single discrete frequency.
Clock selector entity
For details on this specification, refer to ADC-2 5.2.5.2
The USB Audio 2.0 driver does not support clock selection. The driver uses the Clock Source Entity which is selected by default and never issues a Clock Selector Control SET CUR request. The Clock Selector Control GET CUR request (ADC-2 5.2.5.2.1) must be implemented in compatible USB Audio 2.0 hardware.
Feature unit
For details on this specification, refer to ADC-2 5.2.5.7.
The driver supports one single volume range only. If the Volume Control GET RANGE request returns more than one range, then subsequent ranges will be ignored.
The volume interval expressed by the MIN and MAX fields should be an integer multiple of the step size specified in the RES field.
If a feature unit implements single channel controls as well as a master control for Mute or Volume, then the driver uses the single channel controls and ignores the master control.
Additional Information for OEM and IHVs
OEMs and IHVs should test their existing and new devices against the supplied in-box driver.
There is not any specific partner customization that is associated with the in-box USB Audio 2.0 driver.
This INF file entry (provided in a update to Windows Release 1703), is used to identify that the in-box driver is a generic device driver.
The in-box driver registers for the following compatible IDs with usbaudio2.inf.
See the USB audio 2.0 specification for subclass types.
USB Audio 2.0 Devices with MIDI (subclass 0x03 above) will enumerate the MIDI function as a separate multi-function device with usbaudio.sys (USB Audio 1.0 driver) loaded.
The USB Audio 1.0 class driver registers this compatible ID with wdma_usb.inf.
And has these exclusions:
An arbitrary number of channels (greater than eight) are not supported in shared mode due to a limitation of the Windows audio stack.
IHV USB Audio 2.0 drivers and updates
For IHV provided third party driver USB Audio 2.0 drivers, those drivers will continue to be preferred for their devices over our in-box driver unless they update their driver to explicitly override this behavior and use the in-box driver.
Audio Jack Registry Descriptions
Starting in Windows 10 release 1703, IHVs that create USB Audio Class 2.0 devices having one or more jacks have the capability to describe these jacks to the in-box Audio Class 2.0 driver. The in-box driver uses the supplied jack information when handling the KSPROPERTY_JACK_DESCRIPTION for this device.
Jack information is stored in the registry in the device instance key (HW key).
The following describes the audio jack information settings in the registry:
<tid> = terminal ID (As defined in the descriptor)
<n> = Jack number (1 ~ n).
Convention for <tid> and <n> is:
- Base 10 (8, 9, 10 rather than 8, 9, a)
- No leading zeros
- n is 1-based (first jack is jack 1 rather than jack 0)
For example:
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 Example
The 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.
Troubleshooting
If 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 Hub
If 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 development
This USB Audio 2.0 class driver was developed by Thesycon and is supported by Microsoft.
See also
Dakota Frequently Asked Questions
I've seen pictures of Dakota, but where are the MIDI and SPDIF connectors?
Dakota includes two breakout cables that aren't shown in the ads or literature. One connects to a small round 8-pin socket on the Dakota bracket. This molded black cable breaks out to 2 DIN-5 MIDI standard inputs and 2 DIN-5 MIDI standard outputs. The second breakout cable connects to a 15-pin high density socket on the Dakota bracket. On its other end are two RCA jacks, one for SPDIF input and one for SPDIF output, and the 9-pin ADAT Sync In jack.
Can I use a WaveCenter and a Dakota together?
Dakota can coexist in a computer with another soundcard, including WaveCenter. For best results, multiple audio cards that are used together in a system should be using the same sample-rate clock. This minimizes drift between tracks that will undoubtably occur when different audio channels are being clocked at slightly different rates. With Dakota and WaveCenter, sample- rate lock can be achieved by making one of the boards obtain its clock via a digital audio connection from the other (acting as master). For example, if you set Dakota to 44.1 kHz internal operation, WaveCenter to 'Sync:External' and connect a cable from the coaxial S/PDIF out of Dakota to the coaxial S/PDIF in of WaveCenter, the two boards will be locked and no drift will occur. Note that within a Dakota system, this is not an issue -- a common clock is always used for all audio channels. This is also not a problem when expanding a Dakota-based system with the 16-channel Montana expander, since the sample-rate clock is communicated across the ribbon cable that connect the two cards. Many analog soundcards have no mechanism for providing a clock to another card, or for accepting a master clock from an internal source. If you're using such a card with Dakota, we recommend that you avoid using both cards simultaneously, to avoid the drift problems mentioned above.
Frontier Design Sound Cards & Media Devices Driver Download 64-bit
Can I use all of Dakota's digital audio inputs and outputs simultaneously?
Absolutely. And you can add the Montana expansion card to Dakota for even more digital audio I/O.
Doesn't Dakota really support 18 channels of digital audio, not 16?
OK, you win. Yes, a standalone Dakota really has 18 digital audio channels (16 on ADAT optical ports and 2 more on SPDIF ports), both input and output. And with an attached Montana it supports 34 channels in and out (32 on ADAT opticals plus 2 on SPDIF). Sometimes our literature says 16 or 32 channels just to 'simplify.'
What is 'bus-mastering, scatter-gather, zero wait state, PCI DMA,' and why should I care?
That entire nerdy phrase is about efficiency, and Dakota is the best. The less time your CPU spends doing boring audio transfers on the PCI bus, the more time it has to pull tracks off disk, to run DSP plug-ins, and to respond to your commands. We've designed Dakota to be the most efficient soundcard possible so that you can do as much audio work as possible with your computer.
How many channels of digital audio can my computer support with Dakota?
It depends tremendously on your computer, and especially on its disk subsystem. We have many customers who successfully record and play back more than 32 channels using high-speed CPUs and fast SCSI or Ultra-DMA disks.
Since it has an ADAT Sync In port, can I do sample-accurate transfers with it and my ADAT MDM?
Frontier Design Sound Cards & Media Devices Driver Downloads
Currently there are no applications on Windows with a driver interface that supports sample-accuracy. We expect that to change dramatically in 1999, and hope to help lead the way. Stay tuned on that front. In the meantime, you can still use Dakota's ADAT Sync In port and its timecode. Dakota's software driver can take that information and translate it into a form that all current applications understand. The result is *very* tight. (Ask any of our golden-eared customers who use it!) And for phase-critical tracks, like drum kits with multiple microphones, the samples stay perfectly aligned with each other as long as those tracks are transferred to and from digital tape in one pass. Up to 8 tracks can be bounced in or out of the computer that way.
What is SoDA technology?
SoDA (SMPTE on Digital Audio) is Frontier Design Group's innovative technology that lets you use any Dakota or Montana audio channel for transmitting SMPTE timecode. And once you are done using SMPTE, that channel can once again be used for audio. It's easy, flexible, and extremely powerful.
Where do I plug in my SMPTE signal to make use of it as a SoDA input?
SoDA lets you select any digital audio channel for SMPTE use, input and output. Any source of audio that gets digitized can become a SMPTE input. That means any analog input on a converter box, such as Tango24 or Zulu, digital mixer, or MDM tape machine that is connected to Dakota can be used for SMPTE. Similarly, any analog output can become SMPTE out. And with a click of a mouse button, the SoDA input and output channels revert to their normal audio use. Of course, if you don't want to lose an audio channel to SMPTE use, you can attach a Sierra to Dakota and get dedicated SMPTE I/O jacks as well as 8 MIDI input and output ports.
I have an old 8-track analog tape with SMPTE striped on one track. How does SoDA help me put this on hard disk?
Dakota can chase to SMPTE coming in on any digital audio channel, locking its digital sample rate to the timecode on the tape. With an 8-channel converter, such as Tango24 or an ADAT MDM in monitor mode, you can record that tape to hard disk in one record pass. If the original material lasted 01:15:02:16, the result on hard disk will be the same ... not one frame longer or shorter. And it will be recorded without the audio distortion (some would say 'mangling') that software-only solutions inject.
I have another piece of gear with a 2-channel SPDIF optical port (TOSLINK). Can I use it with Dakota?
Of course. The Dakota control panel lets you select the source of the SPDIF input to be the coax input jack, the CD-ROM connector, or any of the optical inputs on Dakota (or Montana, if present). The control panel also lets you route the SPDIF output to any and all of the optical outputs in addition to the coax output jack.
What CD-ROMs have digital output that I can use with Dakota?
Here is a partial list of CD-ROM drives known to provide digital output connectors:
- Goldstar GCD-R580B (8x IDE)
- GoldStar CRD-8320B (32x EIDE)
- GoldStar CRD-8241B (24x EIDE)
- GoldStar GCD-R542B
- Hitachi CDR-8130 16x IDE
- NEC 462 (8x SCSI)
- NEC 501 (4x SCSI)
- NEC 502(E) MultiSpin 6Xi
- NEC 251 4x4
- NEC CDR 4400A
- Panasonic (Matsushita) LK-MC686BP 24x ATAPI
- Panasonic (Matsushita) LK-MC682BP 32x ATAPI
- Pioneer DRA 24x Toshiba XM-5602B (8x IDE)
- Toshiba XM-5702B (12x IDE)
- Toshiba XM-6002B (16x IDE)
- Toshiba XM-6102B (12-24X IDE)
- Toshiba SD-M1002 (DVD player)
- Toshiba XM-1602 (20x ATAPI EIDE)
- Toshiba XM-1702 (24x ATAPI EIDE)
- Toshiba XM-6201 (32x SCSI-2)
- Toshiba XM-6202 (32x ATAPI EIDE)
- Toshiba SD-M1202 DVD/CD-ROM
- Mitsumi 24X CD-ROM
- Creative Labs 24X MX CD-ROM
- Acer 8x IDE model 685A048
- Smart and Friendly CD TurboWriter-SCSI Internal [SAF758]
- Toshiba SD-M1212 IDE 6x/32x DVD-ROM
- Mitsumi 48x IDE CD-ROM
- Memorex 40x CD-ROM
- Acer CD-640A 40x CD-ROM
- TEAC CD540E IDE/ATAPI
- Afreey 4006E 6x DVD-ROM
- Afreey 4008E 8x DVD-ROM
- Afreey 4010E 10x DVD-ROM
- Plextor Plexwriter 12/4/32 SCSI CD-RW
- Plextor Plexwriter 12/10/32 ATAPI CD-RW
Do you know of a CD-ROM drive that should be added to the list? Please send us e-mail!
Frontier Design Sound Cards & Media Devices Driver Download Windows 7
Can I record and playback AES/EBU audio with Dakota?
Yes. The Dakota control panel lets you set the output channel status bits to either Consumer (S/PDIF) or Professional (AES/EBU), and you can connect Dakota's RCA/coax jacks to an inexpensive converter, like the Hosa CDL-313. See the Dakota AES/EBU application note for more details.
How do I record digital audio from my CD-ROM drive?
Here's the process for recording from CD-ROM to (or through) Dakota:
- Verify that your CD-ROM drive has a fully-functional 2-pin digital audio output. Some drives have a 2-pin output, but it's not connected to anything inside the drive! The Dakota FAQ page of our website has a list of CD-ROM drives that have a fully-functional 2-pin digital audio output.
- Make sure the ribbon cable (included in the Dakota package) is properly connected from the drive's 2-pin output to Dakota's internal CD-ROM connector.
- In the Clock/Device Status tab of the Dakota control panel, set the 'S 1:2' device to CD-ROM, *and* set the 'Clock Source' to Dig In S/PDIF. (CD-ROM drives are automatically set to Internal sync, so Dakota must be slaved to the CD-ROM drive.)
- Load an audio CD into the CD-ROM drive, and begin playback. (Some CD-ROM drives only have active output if an audio CD is spinning and the drive is actually counting playback time.)
- If you want to listen to the audio through Dakota's outputs connected to a D/A converter, open the Patchbay tab of the Dakota control panel and route the S/PDIF inputs to the desired (optical or coax) outputs.
Frontier Design Sound Cards & Media Devices Driver Download Windows 10
Can I use an IDE (ATAPI) hard drive with Dakota?
Frontier Design Sound Cards & Media Devices Driver Download
Yes. If you hear audible noise during playback and are using an IDE (ATAPI) hard drive, check to make sure that DMA is enabled for that drive. You can check by going to the Device Manager (Start->Settings->Control Panel->System->Device Manager), clicking the '+' next to 'Disk Drives', double-clicking on the listing for the hard drive in question, going to the 'Settings' tab, and making sure that 'DMA' is checked under Options. You'll need to reboot for this change to take effect.
Is Dakota compatible with my Mac?
Sound Card Driver Download
Yes, as long as you use Mac OS 8.6 - 9.2, but there's no driver for OS X currently available. Note that the Mac driver for Dakota does support the digital audio and MIDI features of Dakota/Montana/Sierra, but does not support the timecode features (SMPTE, 9-pin, SoDA and so on).