Yes. Odd.
I just posted an issue on the feedback hub but I've got no link. I was under
the impression that was the right conduit. LMK if that is not the case.
Thanks for the help. Much appreciated.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> On
Behalf Of Matthew van Eerde (Redacted sender "Matthew.van.Eerde" for DMARC)
Sent: 03 June 2019 19:19
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: WASAPI exclusive mode: USB glitches.
*scratches chin*
So. what to do.
I think the next step is to take this problem to the owners of usbxhci.sys
and ask them why the IRP completion cadence is 15 milliseconds instead of
10.
Can you make an official problem report in Feedback Hub and send me the
link?
_____
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> <wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> > on behalf of Matthew van Eerde
<dmarc-noreply@xxxxxxxxxxxxx <mailto:dmarc-noreply@xxxxxxxxxxxxx> >
Sent: Monday, June 3, 2019 10:58:20 AM
To: wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: WASAPI exclusive mode: USB glitches.
Thanks.
Looks like the exclusive-mode audio pump is running off of
usbaudio.sys/ks.sys IRP completions, which in turn is running off of
usbxhci.sys ISR/DPCs. So far, so good.
The constant glitching is because, for reasons I am unable to fathom,
USBXHCI.sys ISRs are happening every 15 milliseconds, instead of the
expected 10 milliseconds.
_____
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 9:05:22 AM
To: wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: WASAPI exclusive mode: USB glitches.
Thanks.
https://www.novadsp.com/files/I7-1607_20190602-114254.zip
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.novad
sp.com%2Ffiles%2FI7-1607_20190602-114254.zip&data=02%7C01%7CMatthew.van.Eerd
e%40microsoft.com%7Cfd0a96e31b0e43ecb4e708d6e84d22cd%7C72f988bf86f141af91ab2
d7cd011db47%7C1%7C0%7C636951815393363785&sdata=2%2B5zKqy3H8WXGDGc%2BzgUlLy8q
k0duJQHtWU7w7qbO3k%3D&reserved=0>
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> <wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto: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 <mailto: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.
