The Thesycon driver (TUSBAudio) currently takes over all device interfaces, e.g. HID, MIDI, DFU etc.. since it re-implements part of the functionality of the windows composite driver.
If TUSBAudio is installed against a device that doesn't expose a UAC interface the TUSBAudio driver will not be loaded
This means that the HID class driver cannot loaded as a child device for the HID tuning interface and AWE Designer/Server cannot connect.
A future release of the Thesycon driver will avoid this issue by using the built in composite driver.
In the meantime a separate PID should be used for configurations that don't expose a UAC interface (or uninstall he TUSBAudioDriver)
The Thesycon driver (TUSBAudio) currently takes over all device interfaces, e.g. HID, MIDI, DFU etc.. since it re-implements part of the functionality of the windows composite driver.
If TUSBAudio is installed against a device that doesn't expose a UAC interface the TUSBAudio driver will not be loaded
This means that the HID class driver cannot loaded as a child device for the HID tuning interface and AWE Designer/Server cannot connect.
A future release of the Thesycon driver will avoid this issue by using the built in composite driver.
In the meantime a separate PID should be used for configurations that don't expose a UAC interface (or uninstall he TUSBAudioDriver)