We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 4289 - DirectSound: Strong noise after killing of app that using DirectSound on Windows 10
Summary: DirectSound: Strong noise after killing of app that using DirectSound on Wind...
Status: RESOLVED WONTFIX
Alias: None
Product: SDL
Classification: Unclassified
Component: audio (show other bugs)
Version: HG 2.1
Hardware: x86_64 Windows 10
: P2 major
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-01 20:54 UTC by Vitaly Novichkov
Modified: 2018-10-01 21:46 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vitaly Novichkov 2018-10-01 20:54:23 UTC 
While running an audio stream by SDL Audio with using of DirectSound audio driver on Windows 10, the killing or suspending of application will cause a strong woodpecker noise that will never go away even after sound card driver toggling off/on. The only reboot is able to get rid of this.

However, after a little research, a simple DirectSound demo app also causes the reproducing of this bug:
https://www.codeproject.com/Articles/8396/Using-DirectSound-to-Play-Audio-Stream-Data

Possibly it's a bug of Windows 10 itself, or, sound card driver or Direct X itself.

Windows 10 Home 64-bit (10.0, Build 17134)

The sound card is ASUS Xonar DSX.

The bug was reported by a user of one of my projects. I did the test on my VM and bug doesn't reproduce.

The test was done on a 64-bit operating system with a 32-bit app build. The bug doesn't reproduce with a 64-bit app build.

---------------------------------------------------------
Does anyone have a similar issue with this?

So, I'll report this to M$ right now. But maybe can you make a workaround for this?
Comment 1 Sam Lantinga 2018-10-01 21:46:52 UTC 
This is a bug in Microsoft's DirectSound wrapper around WASAPI in Windows 10. We recommend using the SDL WASAPI driver directly to avoid these issues.