OBS sound not working after Windows Update

J

jbarradale

New Member
I have been streaming for several weeks without a single problem. Went to turn off the computer, it had to install an update. My sound works everywhere else. I watched videos on how to fix sound problems. I restarted OBS, the settings in audio match what is on my system. I cannot find why there is no sound. Microphone in the audio bar shows activity, but I cannot hear any sound through headset.
 
I just ran the Streamlabs OBS, added a media source to the scene, changed it to monitor and output, and it works fine. The log file still says "[audio monitoring: 'BackgroundMusic2'] audio_monitor_init: Failed to get device: 80070490". I cannot find any settings that are wrong. I changed the audio to default, and it still does not work.
 
Have you considered that maybe OBS isn't the problem? Maybe the Windows Update changed something (Microsoft Win10 code quality leaves a LOT to be desired at the moment) , and now you need to update OBS to handle that change.
Have you tried removing the microphone /disabling the default audio settings, and re-enabling the microphone in a single scene as an Audio Input Source? if that works, you'll probably be most of the way to resolving your issue

I'm just a newbie myself, so just pointing out some troubleshooting stuff to try if/until someone far more knowledgeable chimes in. And others may not chime in until you post an OBS log with the problem present
 
Thank you. It is the Logitech headset that is not working. It works in every single other software program, but OBS. It actually works fine in Streamlabs version of the software. I have not found a single program where the headset is NOT working. JUST OBS is the problem. I see the same error code in the forum all the way back to 2015. Failed to get device: 80070490 is complained about by many people. No answer though.
 
You are assuming OBS references the device the way other programs do.... not a good assumption. And Logitech is NOT known for quality drivers (/heavy sarcasm). Logitech could have some crap left in the Registry causing problems for OBS [or not]. my point... your having problem with only OBS, doesn't mean its OBS' fault [it might be, it might not be. Let go of any frustration towards OBS, and your likely to get working sooner, regardless of fault]

did you try what I said, remove and re-add audio source?

Also, are you using Logitech microphone from default/system audio settings, or as a scene/source specific Audio Input? I was having audio issues until I followed the recommendation to DISABLE all default desktop audio, and then specifically enable only that desired within scenes (which works great for me)

So... if you are trying to get your system working, I repeat my recommendation from above, as well as if that doesn't work, removing Logitech microphone audio source from OBS, then deleting/rebooting/re-installing logitech driver, reboot again, then try adding audio source back into OBS.
 
I am having problem after Windows 10 update. Audio is not getting recorded & the audio indicator is also inactive. Using inbuilt mic. Audio working fine on Zoom, Filmora & other apps. Tried everything possible in the settings
 
I had a similar problem after a Windows Update, audio source (ZoomH4N) was working; however, the sound wasn't picking up in OBS. I reinstalled the driver for the ZoomH4N and it's working perfectly.
 
Lawrence_SoCal said:
did you try what I said, remove and re-add audio source?

Also, are you using Logitech microphone from default/system audio settings, or as a scene/source specific Audio Input? I was having audio issues until I followed the recommendation to DISABLE all default desktop audio, and then specifically enable only that desired within scenes (which works great for me)

So... if you are trying to get your system working, I repeat my recommendation from above, as well as if that doesn't work, removing Logitech microphone audio source from OBS, then deleting/rebooting/re-installing logitech driver, reboot again, then try adding audio source back into OBS.
Click to expand...

Okay, you say to disable, or remove, but where? In OBS it is in settings. Switching from one (speakers) to the other (headset) does nothing. OBS, no update. Disable all default desktop audio? Again, where, how? I fixed this once, stoopud me, did not write down what I did.
 
I had a similar issue after a Windows 10 update and I found that OBS "forgot" scene sources. I had to select each source and redefine what device it corresponded to.
2022-08-13 10_48_04-Window.jpg


I figured this out because the OBS audio mixer meters were not showing any input even though Windows sound meters showed input. When I selected a source it showed "not connected" next to device.

Hope that helps others who Google "obs audio monitoring not working after windows update" like I did.
 
@yak_
OBS didn't really 'forget', what happened (most likely) is that with OS and driver updates, the OS internal reference (a GUID or similar) to the device changed (even though Display name did not). I had to 'reset' [ie re-select] the same with mic input to motherboard RealTek audio system a month or two ago.
So, OBS didn't 'forget' .. instead the device identifier changed, and OBS doesn't know what the new 'source' is, so you have to update the pointer. Obviously, this normally doesn't (and typically shouldn't happen)... but I've found these occurrences to be really rare for me (less than once a year) and has to do with OS and associated h/w drivers. Personally, it is not worth my time to dive deeper, file bug report etc... I just update the device pointer and move on.
 
Every time MS does an update my audio source settings in OBS are forced to 'Default'.
Even once I get everything re-set, still nothing works.
(That is, audio indicators in OBS work, but there is no output)
If I go into OBS Advanced Audio Settings and change everything from 'Monitor & Output' to 'Monitor Only' then BACK again, VOILA!
Everything starts working.
(I think if you just change the setting from what it is, to something else and back again, will do the trick)
 
You must log in or register to reply here.
Back
Top