OBS Sound stuck at 1 in Windows 11 - no sound from OBS and Wave Link

KingdomGuy

New Member
Hello guys I suddenly ran into a problem I never had before and it is driving me mad.

I didn't do any streaming in over a month now due to personal obligations.
I used my PC during this time but not OBS. When I tried streaming again a few days ago I noticed I had no sound coming from OBS.
I have Elgatos Wavelink Software set up and everything worked fine before. I did not change anything in there either.
I am not aware of any changes I did during this time whatsoever.

In the Soundmixer of Windows 11 the sound of OBS is stuck at 1. I can not change it. I can change the output device but it doesn matter.
No matter what I set it too, even if I stop Wavelink and put it all to standard, I have no sound coming from OBS. Usually when I set up my monitoring devices and I set certain sources to monitor and output or simply monitor I should hear it but everythingh is quiet.
1717453003288.png


Again, I already tried moving Wave Link out of the equation and trying everything without it but it does change nothing.

Does anybody have a clue what is going on?

Heres a current log file:

Every bit of help is greatly appreciated.

Thank you and best.
 

Suslik V

Active Member
Code:
00:01:41.948: [WASAPISource::TryInitialize]:[{0.0.1.00000000}.{4b604875-53f7-4e79-bee0-1d3d8e03a3d2}] Failed to enumerate device: 80070490
00:01:41.948: WASAPI: Device '{0.0.1.00000000}.{4b604875-53f7-4e79-bee0-1d3d8e03a3d2}' failed to start (source: Elgato Wave Stream Mix)
00:01:41.948: [audio monitoring: 'Elgato Wave Stream Mix'] audio_monitor_init_wasapi: Failed to get device: 80070490
00:01:41.948: [audio monitoring: 'Chat_JustChatting_Lumia'] audio_monitor_init_wasapi: Failed to get device: 80070490
00:01:41.949: [audio monitoring: 'Gameplay_Alert Box_Lumia'] audio_monitor_init_wasapi: Failed to get device: 80070490
00:01:41.949: [audio monitoring: 'Lumia Layout Start Bildschirm'] audio_monitor_init_wasapi: Failed to get device: 80070490
and similar errors means that OBS unable to get audio device. You may try to reinstall drivers for your sound device and check if OBS application has permissions to access this device.
 

Lawrence_SoCal

Active Member
Someone else recently posted regarding a Windows Update changing audio device (microphone and related) permissions, preventing OBS Studio from accessing said device
 

SaberRunTV

New Member
I made an account just to specify. A very simple fix is opening the folder where the .exe is located. right click and in properties then compatibility simply click on "open this application in administrator mode."
 

Lawrence_SoCal

Active Member
I made an account just to specify. A very simple fix is opening the folder where the .exe is located. right click and in properties then compatibility simply click on "open this application in administrator mode."
And that, though 'simple' is absolutely atrocious security practice and would be highly UNADVISABLE ... basically the sort of reason lots of people get compromised, data and money stolen, etc.

If getting something to run, and being ok to being hacked, then go for it... otherwise, fix actual root problem and do NOT run things in administrator mode that shouldn't/don't need to be (like OBS Studio ... yes I'm aware of some edge cases where Windows doesn't handle GPU scheduling well (with system running maxed out), and needs this workaround... unrelated to this post/issue).
 
Top