AudioDriverWASAPI error while using editor if another application is using exclusive mode

[Toshiwoz]

Godot version:
3.0.3 RC1

OS/device including version:
Windows 10, not related to video, apparently.

Issue description:
I have used the editor for a while and never got this error before, I haven't even used the audio features, yet this error message seems to be related to the audio:

ERROR: AudioDriverWASAPI::thread_func: WASAPI: GetCurrentPadding error
   At: drivers\wasapi\audio_driver_wasapi.cpp:533

Steps to reproduce:
Unkown

Minimal reproduction project:
unkonwn

[vnen]

cc @marcelofg55

[marcelofg55]

@Toshiwoz Hi, it happens everytime? Whats your soundcard?

[Toshiwoz]

Nope, it started recently, strangely maybe, when I started using Netflix (it sounds weird, but that aplication does strange things with the audio, it does not allow to control the volume). The sound card is an integrated soundcard, my pc is an old EEEBOX (with intel atom), and I use HDMI + TV (with it's audio device) 2018-05-09 8:03 GMT-05:00 Marcelo Fernandez <[email protected]>:

…

@Toshiwoz <https://github.com/Toshiwoz> Hi, it happens everytime? Whats your soundcard? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18732 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUT4zOb4st_i53x5WuHEVPK6_X_eaifPks5twukdgaJpZM4T3q1m> .

[marcelofg55]

So if you don't use Netflix there is no problem? If so then it's probably requesting exclusive access to the soundcard.

[Toshiwoz]

Yeah, I can confirm that now, I opened Godot editor, my current project. No error.
Then I open Netflix, the moment I start playing a video, Godot starts to log that error.
I wonder why the Netflix app does that strange thing (should I report that to them then?).

[marcelofg55]

Yes, you could try to contact them since we can't do much if an external application requests WASAPI exclusive mode. They could switch to shared mode and that will solve the issue.

[Toshiwoz]

I've been told it's how it is suposed to work, by the netflix support, lol..
Should I close this?

[akien-mga]

I guess we could try to improve the error message, but we can't prevent thirdparty apps from abusing the audio driver :)

@marcelofg55 Would there be an easy way to catch this source of error and print an understandable error?
Like "The WASAPI audio interface could not be initialized, due to the soundcard being used by another application in exclusive mode."

[marcelofg55]

Yeah, we should definitely improve the error messages for this so that it's more clear. But I think we won't be able to tell if another application that uses exclusive mode is actually the problem, afaik WASAPI funtions simply return AUDCLNT_E_DEVICE_INVALIDATED when this happens.

[benthillerkus]

I'm getting this error too; I am not using Netflix nor listening to any music.
ERROR: thread_func: WASAPI: GetCurrentPadding error
At: drivers/wasapi/audio_driver_wasapi.cpp:533

[marcelofg55]

I'm getting this error too; I am not using Netflix nor listening to any music.
ERROR: thread_func: WASAPI: GetCurrentPadding error
At: drivers/wasapi/audio_driver_wasapi.cpp:533

Happens every time you run godot? Or is it random? And what soundcard you're using?

[Toshiwoz]

It may happen also with any other program that takes full control of the sound card.
What I did was to remove the exclusive control of the program over the audio card... I don't remember where the setting is, there, in the image, try by unchecking "Allow applications to take exclusive control of this device".

[benthillerkus]

Removing the exclusive mode rights stopped this behavior, I think, it's def not happening anymore rn and that's the only thing I've changed

[matthieudesprez]

Thanks, it did fix the error for me as well.

To access the settings on windows 10:

• right click the sound icon on the bottom right
• click on Sounds
• go on Playback tab
• select your audio device and click on Properties
• then you can go on Advanced tab and disable exclusive mode

[jitspoe]

Also getting this. Windows 8.1. Certainly happens opening some sort of sound application like Sound Forge, but I've had it happen pretty regularly just doing basic stuff like web browsing, though tough to say exactly what caused it. I often have Godot open in the background and come back to see it spamming this nonstop. Updated line number on 3.1.1:

 ERROR: thread_func: WASAPI: GetCurrentPadding error
   At: drivers/wasapi/audio_driver_wasapi.cpp:646

Might be nice to, at the very least, avoid spamming the error. Best case would be to attempt to grab access of to the sound device again, maybe after a short delay.

[KoBeWi]

Can anyone still reproduce this bug in Godot 3.2.3 rc4 or any later release?

[jitspoe]

Can confirm it still happens in 3.2.3 rc4. I can repro it by simply opening godot to the project manager then launching VEGAS Pro, Sound Forge, or any other program that tries to take exclusive control of the sound card.

[vcprocles]

Stumbled upon this issue when playing music in the music player with exclusive mode to bypass all extra audio effects. The extra thing I got is a memory leak, but that could be related to all the logging (I got almost a million messages accumulated).

[kamtar]

somebody has a hot-fix for this? I would like to listen to Tidal the way I'm used to without rendering Godot unusable.

[dmhagar]

There is no reason for Godot to literally log HUNDREDS of thousands of these errors when this is happening.

A single, concise error message would be acceptable.

The Godot editor will also do this if VLC Media Player, an incredibly commonly-used media app, is playing a movie. The engine doesn't even have to be running a game, it just needs to be open. That's ridiculous.

[allenwp]

I've created PR #100116 to address the error spam in the Godot editor. If anyone is available for testing this fix, you can download an editor build from the artifacts on the checks page of the PR.

[elvisish]

I've created PR #100116 to address the error spam in the Godot editor. If anyone is available for testing this fix, you can download an editor build from the artifacts on the checks page of the PR.

This build seems to fix the spam problem when I use Realtek ASIO in Reaper at the same time as having Godot running. I get these errors when I start Reaper:

  drivers\wasapi\audio_driver_wasapi.cpp:780 - WASAPI: GetBufferSize error
  drivers\wasapi\audio_driver_wasapi.cpp:851 - WASAPI: Current output_device invalidated, closing output_device
  drivers\wasapi\audio_driver_wasapi.cpp:987 - WASAPI: Start failed
  drivers\wasapi\audio_driver_wasapi.cpp:780 - WASAPI: GetBufferSize error
  drivers\wasapi\audio_driver_wasapi.cpp:851 - WASAPI: Current output_device invalidated, closing output_device
  drivers\wasapi\audio_driver_wasapi.cpp:987 - WASAPI: Start failed
  drivers\wasapi\audio_driver_wasapi.cpp:780 - WASAPI: GetBufferSize error
  drivers\wasapi\audio_driver_wasapi.cpp:851 - WASAPI: Current output_device invalidated, closing output_device
  drivers\wasapi\audio_driver_wasapi.cpp:987 - WASAPI: Start failed
  drivers\wasapi\audio_driver_wasapi.cpp:780 - WASAPI: GetBufferSize error
  drivers\wasapi\audio_driver_wasapi.cpp:851 - WASAPI: Current output_device invalidated, closing output_device

But that's it. If I try to load Reaper with Realtek ASIO using regular 4.4.dev7, it spams until it hangs and I have to terminate it through Task Manager. I never had this problem with 3.5.