1) Windows 10 now has native support for USB Audio 2.0 so this class of drivers are supported regardless of the VID / PID details. 2) Windows 7 still links the INF file to the VID / PID details. Also, if these IDs change then the.CAT file will be invalid. You will have to get the INF file signed with the IDs you have applied. Driver development. 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 The driver is named: usbaudio2.sys and the associated inf file is usbaudio2.inf.
- For the record, Windows 10 Technical Preview has the same support in this area as Windows 8.1: native support for USB 1.0, USB 2.0, and USB 3.0 controllers. Native support for USB Audio 1.0 audio devices. But, as you point out, USB Audio 2.0 devices require a third-party driver. Matthew van Eerde.
- Windows Drivers: USB 2.0 Video & Audio Capture DVD Maker With Real Time TV Display: Windows Drivers: Download: VD-GRBR 1 files 1730 downloads User Manuals: USB 2.0 Video & Audio Capture DVD Maker With Real Time TV Display: User Manuals: Download: USB-WA62 3 files 1297 downloads Mac Drivers, User Manuals, Windows Drivers: USB 2.0 Adapter 1600.
I have designed a board around the XU216-512-TQ128 chip.
Windows 10 Usb Audio 2.0 Driver Full
I started from a Dev Kit suppplied by a third party and with the kit I received also the Driver for Windows.The firmware with the Dev Kit reports:
#define VENDOR_STR 'xxx'
#define PRODUCT_STR_A1 'yyyyyyyyy'
#define PRODUCT_STR_A2 'yyyyyyyyy'
#define SERIAL_STR ' // default to empty serial number - a value can be loaded into the str table from the OTP at runtime#define VENDOR_ID (0x1CBA) // Xmos VID so as to use the drivers installed with the Xmos tools
#define PID_AUDIO_2 (0x----)
#define PID_AUDIO_1 (0x----)
I prefer to hide the information about his third party.
I received my PID and the related driver a few days ago.
I introduced the PID received in the following way:
// #define VENDOR_STR 'xxx'
// #define PRODUCT_STR_A1 'yyyyyyyyy'
// #define PRODUCT_STR_A2 'yyyyyyyyy'
// #define SERIAL_STR ' // default to empty serial number - a value can be loaded into the str table from the OTP at runtime
// #define VENDOR_ID (0x1CBA) // Xmos VID so as to use the drivers installed with the Xmos tools
#define PID_AUDIO_2 (0x30B3)
#define PID_AUDIO_1 (0x30B3)
I have installed the driver on a Win10 PC and the behaviour is strange:
Windows 10 Usb Audio 2.0 Driver Download
1) Wasapi works 2) direct sound works 3) ASIO KO
I have installed the same driver on a Win7pro PC and the driver is signalled with a question mark and a yellow triangle in the device manager of the control panel of Win7pro and, of course, the board doesn't start.
If I flash the exactly the same board with the firmware used when the board was designed and I use the driver received with the Dev Kit of the third party everything is perfect.Usb Audio Class 2
Any suggestion?