Download the latest Behringer USB AUDIO 2.8.40 driver for your computer's operating system. The supported operating systems are, Windows XP 32 and 64 bit, Windows Vista 32 and 64 bit and Windows 7 32 and 64 bit. Free behringer 64 bit driver windows 10 free download. software at UpdateStar - 1,746,000 recognized programs - 5,228,000 known versions - Software News. BEHRINGER USB AUDIO DRIVER - Shareware - more info. More Realtek High Definition Audio Driver 6.0.9088.1.

1. Behringer Usb Audio Driver Windows 10
2. Behringer Usb Audio Driver Windows 10 64 Bit
3. Behringer Usb Audio Driver 2.8 40 Download 64 Bit Windows 10
4. Behringer Usb Audio Driver 2.8 40 Download 64 Bit Windows 10 Free

USB Audio 2.0 Class Driver for Windows 10

• BEHRINGER UM2 DRIVERS for Windows 10 64 bit. My input and output settings are USB Audio CODEC for the Audio Interface Behringer U.
• Behringer Usb Audio 2.8.40 Driver for Windows 7 32 bit, Windows 7 64 bit, Windows 10, 8, XP. Uploaded on 1/20/2019, downloaded 512 times, receiving a 87/100 rating by 325 users. Apr 22, 2020 From your Windows taskbar, right-click the sound icon and select Playback devices.

FeaturesSupported PlatformsDemoPrices

Thesycon’s USB audio class driver TUSBAudio targets USB audio devices for professional and semi-professional use and highest quality audiophile HiFi systems. The driver supports devices which are compliant to the USB Audio 2.0 or USB Audio 1.0 device class specification. The driver provides an ASIO 2.3.1 compliant software interface and integrates with Windows as a standard WDM/DirectX compatible sound device. If the device provides MIDI features the driver exposes standard Windows MIDI ports.

To meet professional audio requirements, the audio class driver is optimized for low latency and low CPU load. Buffer depths can be adjusted by the user to optimize settings for a given computer. The driver implements a transparent (bit-perfect) playback and recording data path.

General

• supports Audio class 1.0 and Audio class 2.0 devices
• Supports USB 2.0 full speed and high speed, and USB 3.0/3.1/3.2 super speed or higher
• supports standard sampling rates (depending on device capabilities):
  44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz, 176.4 kHz, 192 kHz, 352.8 kHz, 384 kHz, 705.6 kHz, 768 kHz, 1411.2 kHz, 1536 kHz
• supports USB Audio Type I sample formats:
  PCM 16 bit, PCM 24 bit, PCM 32 bit, FLOAT 32 bit
• supports stereo and multi-channel configurations with as many channels as the device implements

ASIO

• ASIO 2.3.1 compliant driver DLL
• sample formats (depending on device capabilities): PCM 24 bit, PCM 32 bit
• bit-perfect playback and recording through ASIO
• playback mix (simultaneous ASIO and WDM playback)
• supports both 32-bit and 64-bit ASIO host applications
• multi-client support (multiple ASIO applications in parallel)
• configuration of ASIO buffer depth via driver control panel
• ASIO DSD mode supported (playback and recording), see below DSD Support

The TUSBAudio driver uses ASIO Driver Interface Technology and the Steinberg ASIO SDK. ASIO is a trademark and software of Steinberg Media Technologies GmbH.

WDM/DirectX Features

• standard Windows sound interfaces: MME, DirectSound, WASAPI
• stereo and multi-channel playback and recording sound devices (depending on device capabilities)
• flexible sound device configuration, for example:
  8-channel unit can either be exposed as 7.1 or 4 x stereo playback
• bit-perfect playback and recording through WASAPI
• volume and mute control through Windows standard GUI (depending on device capabilities)
• jack sensing (depending on device capabilities)
• PCM 16 bit, 24 bit, and 32 bit sample format (depending on device capabilities)

DSD Support

Behringer Usb Audio Driver Windows 10

• native DSD mode through ASIO (see above)
• DSD over PCM (DoP) supported through ASIO and WDM
• DSD sample rates: DSD64 (2.8MHz), DSD128 (5.6MHz), DSD256 (11.3MHz), DSD512 (22.6MHz), DSD1024 (45.2MHz)

MIDI Features

• Windows compliant MIDI input and output ports (depending on device capabilities)
• Multiple applications can share a MIDI input port.
• Optionally, multiple applications can share a MIDI output port.

Virtual Channels Add-on

The Virtual Channels Add-on is an optional component of the TUSBAudio driver and has to be licensed additionally.

• virtual input or output channels can be defined (e.g. loopback channels)
• virtual WDM sound devices can be built from virtual channels
• arbitrary signal routing between physical and virtual channels can be configured
• routing and weights are fixed (not dynamically configurable through API)

Mixer Add-on

The Mixer Add-on is an optional component of the TUSBAudio driver and has to be licensed additionally.

• driver implements complete mixer matrix for all input and output channels
• any mixer weight can be controlled through API at runtime
• SDK included, contains sample application for mixer control
• virtual input or output channels can be defined (e.g. loopback channels)
• virtual WDM sound devices can be built from virtual channels
• application examples: monitor mix, loopback channels, channel swap, balance, etc.

• The driver will be delivered fully customized for licensee’s product.
• Customization includes USB VID/PID, file names, text strings, etc.
• Windows 10 version of the driver is signed with Microsoft Attestation signing.
• Driver Customization Kit add-on: The Driver Customization Kit enables licensee to customize the driver by themselves.

• Wizard style user interface for interactive use
• Command line interface (silent mode) for integration into overall software setup
• Customization possible

• Control panel application with graphical user interface is included
• Device status and control via private programming interface (DLL)
• Source code of the control panel is part of the SDK.

• DFU utility with graphical user interface is included
• Firmware upgrade according to DFU device class
• Customization and Multi-language user interface is possible
• Source code of the DFU utility is part of the SDK.

NOTE: A DFU utility with identical functionality is available for macOS as well.

The SDK add-on is an optional component. It enables custom control panel development and direct access to custom firmware features. The SDK includes:

• API definition and link library for TUSBAudio API DLL
• API reference documentation
• Source Code of sample control panel implementation
• Source Code of DFU Application

The USB Audio 2.0 Class Driver for Windows implements the USB Audio 2.0 and 1.0 device class specification and is independent of the specific silicon and firmware solution used in a given device. As long as the hardware and firmware implement the descriptors, endpoints and requests defined in the class specification the driver should work. However, there are some requirements and assumptions as listed below.

• A device can implement a playback data path, a recording data path, or both.
• Both playback and recording path must be driven by the same sample clock source (as required by ASIO).
• An Audio 2.0 device must implement at least one clock source unit. If there is more than one clock source then a clock selector unit must be implemented as well.
• The driver supports the asynchronous, synchronous and adaptive endpoint synchronization model.
• If there is a recording path (IN endpoint) then the driver uses the incoming sample stream as clock reference to generate the outgoing stream (playback path).
• A playback-only device with an asynchronous OUT endpoint must implement a feedback endpoint.
• Optionally, a device can implement a feature unit to expose volume and mute controls.

Our software is purely designed and implemented by our team in Germany - no outsourcing. Technical support is provided directly by the developers.

Current Version: 5.12

To receive a free demo, prices or license agreement, please fill out the contact form.

The free evaluation version of the TUSBAudio driver works for an interval of 60 days without any limitation. After that evaluation period has expired, the driver stops working.

NOTE: The driver described on this page is *not for use by end users*. It will not help solve any problems you may experience with a consumer device such as a webcam, camcorder, card reader, external sound card, etc. Thesycon’s device drivers are software components intended to be used by hardware or software manufacturers to create end products.

For each USB device model an official USB vendor ID (VID) is required. Vendor IDs must be unique and will be assigned by the USB Implementers Forum (www.usb.org). Registration fees will be charged.

Thesycon owns a USB vendor ID and provides a subset of product IDs (PID) to licensees of Thesycon drivers.

© 2021 THESYCON

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:

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.

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

Behringer Usb Audio Driver Windows 10 64 Bit

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)

Behringer Usb Audio Driver 2.8 40 Download 64 Bit Windows 10

<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

Behringer Usb Audio Driver 2.8 40 Download 64 Bit Windows 10 Free

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