Thanks.
https://www.novadsp.com/files/I7-1607_20190602-114254.zip
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> On
Behalf Of Matthew van Eerde (Redacted sender "Matthew.van.Eerde" for DMARC)
Sent: 03 June 2019 16:39
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: WASAPI exclusive mode: USB glitches.
Upload it to a share somewhere and provide a link.
Alternatively, file a problem report in Feedback Hub, attach the .etl, and
provide a link to the problem report.
_____
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> <wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> > on behalf of Jerry Evans
<jerry@xxxxxxxxxxx <mailto:jerry@xxxxxxxxxxx> >
Sent: Monday, June 3, 2019 8:36:26 AM
To: wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] WASAPI exclusive mode: USB glitches.
One for Matthew I suspect.
tl;dr; I've assembled the ETL glitch trace package as detailed in the blog.
Where to send it?
WASAPI glitches badly with USB devices in exclusive mode. Win 10 1607 on a
gen4 4GHz i7 with Asus motherboard.
Changing the buffer sizes (according to the minimum and maximum values
returned by GetDevicePeriod()) has no effect. Tested on 2 USB full speed
devices, an ancient Roland adapter and a much newer Behringer based on a TI
chipset.
Shared mode is AOK.
using the onboard Realtek HDA in _exclusive_ mode is also AOK.
Results are identical using whatever the latest developer release might be.
Some scope images attached for anyone interested.
TAIA
Jerry.
