sorry for the delay on this. It took quite some time to get Collaborate up and
running for our company account, and now I’m stucking with filing the issues.
One has to join a so-called Program in order to file issues, and there is no
program for HLK / Windows Driver Kit et. al..
What is the recommended procedure for this? There is still quite few
documentation on Collaborate on the web...
Can you file (separate) bugs on Collaborate for the KS Position Test and
WaveTest / DataIntersection failures? Attach the failing test logs to each.
Send me the VSO IDs and I can route them to the right team internally.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Franz Detro <franz.detro@xxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, July 12, 2018 5:16:28 AM
Subject: [wdmaudiodev] Re: USB Audio Class 2 driver and HLK tests
Please try the April 2018 Update HLK, and Windows 10 April 2018 Update.
Audio Logo Test is working with the April 2018 version, the KS Position Test
error is exactly the same and Wave Test does show a slightly different
PinInstantiate Check #1 test is gone, but now DataIntersection tests fail
(which worked in 1709).
So it looks like the HLK test suite does not correctly handle the Microsoft
UAC2 inbox driver?
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on behalf of Franz Detro
Sent: Wednesday, July 11, 2018 12:18:40 AM
To: wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] USB Audio Class 2 driver and HLK tests
I’m trying to run the HLK tests (Controller version 10.1.16299.16299) on a
USB Audio device using the inbox Microsoft UAC2 driver.
I am seeing weird errors with three of the Audio tests:
* Audio Logo Test: test locks up when trying to render a sine wave in
exclusive mode, test run is killed by HLK after 30 minutes
* KS Position Test: Capture DriftAndJitter For AEC cannot set a viable
* Wave Test: PinInstantiate Check #1 fails for Render and Capture
Audio streaming using the device does work fine, all other audio tests do
pass. I can reproduce the above errors with every UAC2 device I have at hand.
Are these known issues with the Microsoft UAC2 driver / Windows 10 RS3 / HLK
Has anybody successfully ran these tests on a UAC2 device?
Any help on this is really appreciated!
Thanks in advance,