This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 57.00000000000001%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKF%3C/text%3E%3C/svg%3E)
I'm using a native WASAPI exclusive mode application, that outputs a sine tone to a generic USB speaker. When the latency is set to the minimum allowed (3 msecs), the application can connect to the USB speaker and the output audio sounds correct, and the callback is triggered every 3 msecs. The frequency is 44100 Hz, and the buffer size is 132 samples (132 / 44100 = 3ms latency).
However, after a length of time (it could be 15 mins to several hours), the audio starts playing really slowly and sounds distorted. I find that the callback time has changed from 3ms to 9ms, but the buffer size is still 132 samples and the device is still in WASAPI exclusive mode.
This could be related to the generic USB audio driver supplied by Windows, because the bug doesn't happen when I output to my laptop speakers which use the Realtek driver.
Is this a known issue? I've been able to reproduce with a native WASAPI implementation, and have also reproduced using the third party library Juce, when set to WASAPI exclusive mode.
NOTE that I have a sample app to be used to reproduce the issue (WASAPIRenderExclusiveEventDriven.exe) but I can't upload it here - please let me know how I can send it to you.
Here are some steps for recreating:
Setup:
A sine tone should start playing from the USB speakers. Leave the setup running. After several hours (it can be overnight for some laptops), you will find that the audio is not playing correctly and sounds distorted. In this case, the callback time has changed from 3 ms to 9 ms. The only way to recover the audio is to restart the connection.
Thanks for your help,
Kotisi
As a bit of background - originally I was trying to connect to a Pro audio hardware with WASAPI exclusive mode for minimal latency, but started hitting this bug. To rule this out as a hardware specific bug, we started testing with some USB speakers (M1Active 320USB speakers) and were able to reproduce the issue. In both cases, I believe the standard Windows USB audio driver is being used (usbaudio.sys). Thus far we have only reproduced the issue when connected to output devices that use the standard Windows driver.