Hi Florian, How can you tell what driver it is based on? Are you working for NI? I didn't find a way to file a proper bug report with NI on that matter, however telling from the discussion going on in the NI forums, the developers and the customer support in particular should be well aware of the problem. I'd like to stress again that the problem did not yet occur in ASIO only mode, however I don't know about any latency issues either. Regards, Xaser From: florian.schirmer@xxxxxxxxxxxxxxxxxxxxx Subject: [wdmaudiodev] Re: Debugging unknown WDM Driver Date: Wed, 18 Dec 2013 14:13:55 +0100 To: wdmaudiodev@xxxxxxxxxxxxx Hi All, On 18.12.2013, at 11:11, Clemens Ladisch <clemens@xxxxxxxxxx> wrote:It's a USB device. Don't they use the stock system driver -- usbaudio.sys? The current version (2.0) of the USB audio specification was coauthored by Microsoft and is only seven and a half years old, so _of course_ it is not yet supported by usbaudio.sys. Even if it would, you still need to solve the issue with the low latency ASIO support. If I got any results, maybe I could point the NI devs in the right direction and they'll maybe even release a fix. Can you find out if they started with one of the UAC2 drivers from Thesycon or XMOS, or wrote their own? It is based on the driver we also use for our non UAC2 compliant devices. Instead of investing time into reverse engineering the driver on your own i strongly recommend to file a proper bug report. If you already did, please forward it to me and i will make sure it gets the proper attention. Best, Florian