USB Audio 2.0 Class Driver for Windows

FeaturesSupported PlatformsDemoPrices

Software and Drivers. DCP Manager, DCM Manager, DPM Manager, DCPNet, and USB Drivers. Cinema Software Create designs using the Q-SYS platform. Control and monitor. This section describes Universal Serial Bus (USB) support in the Windows operating system, so that you can develop USB device drivers that are interoperable with Windows. Where applicable. USB devices are peripherals, such as mouse devices and keyboards, that are connected to a computer through a single port.

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.

Qs Industries Usb Devices Driver Download

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 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.

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.
• Windows 7/8 version of the driver is signed with Thesycon’s code signing certificate.
• 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.0

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

It is frustrating to find that your Android device is not recognized as USB driver when you want to transfer files between phone and PC or recover data from Android phone. While the result is similar, the causes and solutions may vary from case to case. Similar symptoms or notifications, like “USB device not recognized”, “PC not recognizing Android phone”, or “USB device not detected but charging”, may occur on different devices. Please check following solutions to fix Android USB device not recognized on Windows problem.

Try Following Measures First
Here are some small tips that might help and won’t take a long time even if not working.

• Try a new USB cable and another computer. Some cables are power only.
• Connect Android device to PC directly instead of through USB hub.
• Reboot phone and connect to PC while in Airplane mode.
• Remove battery and SIM card, and wait a while, then put them back and reboot.
• If Windows detects your phone but doesn’t find any content, you should unlock your phone screen and try again.

If above tricks don’t work for you, please try solutions below.

Qs Industries Usb Devices Driver Updater

Solution 1. Connect Android to Computer as MTP to Fix Charging Only Problem

Android device can be connected as Media device (MTP), Camera (PTP), USB flash drive, Charge only, etc. If you want to transfer files between phone and PC, you need to set USB connection as MTP mode.

When an Android device is connected to computer, a notification should appear on the drop-down menu named as “Connected as a …” or “USB Charge Only”. You can tap it to open USB computer connection options and choose MTP from the list.

If nothing appears when connected to computer, which often happens after system upgrade, you’ll have to find USB connection menu manually. Try following methods.

• Go to Settings> Storage> More (three dots menu)> USB computer connection, choose Media device (MTP).
• For Android 6.0, go to Settings> About phone (> Software info), tap “Build number” 7-10 times. Back to Settings> Developer options, check “Select USB Configuration”, choose MTP. But no way to set MTP as default on Marshmallow.
• Dial *#0808#, if you get “USB Settings”, choose MTP+ADB, then reboot.

Solution 2. Update or Install Proper Driver for Android USB Driver Not Working Problem

Sometimes Windows won’t recognize Android device because the driver is corrupted and USB driver not working. Hence, you need to update or install proper driver for your device. Following are two common methods. (Check more ways to install Android USB driver.)

Update Driver for Android Phone Manually

Step 1. Go to Start> Control Panel.
Step 2. Click “System and Security”, then “System”.
Step 3. Click “Device Manager” on the left list.
Step 4. Locate and expand “Other devices” or “Portable devices” and find the driver. If there is a problem with the driver, it should be labelled with a yellow exclamation mark.
Step 5. Right click on the driver and choose “Update Driver Software…”.
Step 6. Successively choose “Browse my computer for driver software”> “Let me pick a list of device drivers on my computer”, then hit “MTP USB Device” and click Next. Once the driver is updated, connect your device again.

Install Proper Driver via Manufacturer Tools

Manufacturer management tools usually go with drivers for their devices. You can install official management software, like Samsung Kies or Smart Switch, and HTC Sync Manager, on your computer. Then connect your phone to computer and run the software to install drivers automatically.

Solution 3. Install Necessary Kit for Windows 10 to Fix Android Not Detected Problem

If you encounter Android USB not recognizing problem after Windows 10 upgrade, you’ll need to install some missing files to help Windows 10 recognize your Android phone as MTP device. The following two might help.
Media Transfer Protocol Porting Kit
Media Feature Pack
Notice: Check more tips about Windows 10 doesn’t recognize Android.

Solution 4. Try a Trick to Fix Android Not Recognized Problem Caused by Hardware

Qs Industries USB Devices Drivers Update

If none of the above solutions can fix your Android device connection problem, it might be a hardware glitch, and you may try this trick. This is not a regular tech tip, but many people say it works. Please do it at your own risk.
Step 1. Hold your phone and look at the micro USB port.
Step 2. Insert something tiny and nonmetallic into the USB port, and lift up the thin contact points gently.
Step 3. Connect your phone and PC with USB cable again.

Please enable JavaScript to view the comments powered by Disqus.