USB Audio 2.0 Class Driver for Windows 10 and Windows 11

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.

Feature Summary - USB Audio 2.0 Class Driver for Windows

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

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.

Customization of the Driver

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

Driver Installer

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

Control Panel

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.

Firmware Upgrade

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.

Software Development Kit – SDK

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

Mixer Add-on

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

Driver implements complete mixer matrix for all input and output channels
Any mixer weight can be controlled through API at runtime
Virtual input or output channels can be defined (e.g. loopback channels)
Virtual WDM sound devices can be built from virtual channels
SDK available, contains sample application for mixer control

Mixer Software Development Kit – Mixer SDK

The Mixer SDK is an optional component and requires the Mixer add-on. It includes:

API definition and link library for TUSBAudio API DLL
Source Code of sample control panel implementation
Source Code of DFU Application
Sample application for mixer control
Any mixer weight can be controlled through API at runtime
TUSBAudio Reference Manual

Supported Platforms

Windows 11 arm64
Windows 11 x64 (64-bit)
Windows 10 x64 (64-bit)
Windows 10 x86 (32-bit)

Device and Firmware Requirements

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.

Software made in Germany

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

Free Demo, Licensing conditions & Prices

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.

Current Version: 5.74

Security Advisory (CVE-2024-25376)

An Insecure Permission vulnerability in the MSI-based driver installer has been reported by Julian Horoszkiewicz from the Eviden Red Team. The MSI installer before v5.68 allows a local attacker to execute arbitrary code via the msiexec.exe repair mode. A local user can trigger msiexec in repair mode (/fa flag) on the MSI package present in C:\Windows\Installer. In result, a copy of tlsetupfx.exe executable is executed with SYSTEM privileges, from the local %TEMP% directory, creating a race condition giving the regular user an opportunity to switch executable files (e.g. DLLs) and get their own code executed as SYSTEM.

All TUSBAudio driver installers after v5.40.0 and before v5.68.0 are affected.

For more information about this vulnerability, see also CVE-2024-25376.

Thesycon has fixed the vulnerability in v5.68.0 and provides updates for all affected driver packages. Thesycon strongly encourages customers to update any released driver packages.