Windows update affecting audio to OBS

[segraham]

Anyone experience issue where WIndows update has caused audio to quit working in OBS?

I am getting audio from sound board to PC; Line In shows audio activity.
OBS is not picking up the activity.

Audio worked before the updates. Tried to uninstall but will not allow.
Just wanted to see if anyone has had similar experience and if there are other updates that may fix this issue.

Windows 10
Latest OBS (ran check for updates)
See attachment for updates that were installed.

 

[segraham]

Attachment showing the updates

 

[Lawrence_SoCal]

I had an issue about a month/6 weeks ago ?? with something, likely a Win10 update, change OS default audio handling (or at least the way OBS interpreted that)
In my case, I have Realtek audio drivers, and somehow (possibly my fault), the audio mapping changed (PC has 3.5mm TRRS connection on both front and back of PC, one I use for mic in, the other for speaker out) and the mic stopped being processed by OBS. After a very stressful set of minutes right before a scheduled livestream I finally figured out the OS to device to OBS mapping, and made a slight tweak in OBS Audio device selection (from default, if I recall correctly on Audio Input device) to the named device and all was well.

The joy of Win10.....
sometimes one knows too much.... the fix was relatively easy [just something I'd never dealt with previously...so didn't know to check it]
In OBS 26, there is now a dropdown above the Scenes/source list when selecting an Audio Input device, with a listing in my case of "Default", plus 2 different camera drivers which also have audio (webcam, and PTZ NDI connected camera)... line is isn't currently connected, as I'm pretty sure that should appear as well [listed as Realtek Audio something or other]
So either in Windows 10 Sound settings, or in OBS's Device selection for the Audio Input, make sure the right item is listed. at least that was my fix as the default had changed (not an OBS issue)... so making the default be the expected thing within the OS, and specifically selecting the device in OBS.. wither worked as the fix for me

 

[segraham]

I had an issue about a month/6 weeks ago ?? with something, likely a Win10 update, change OS default audio handling (or at least the way OBS interpreted that)
In my case, I have Realtek audio drivers, and somehow (possibly my fault), the audio mapping changed (PC has 3.5mm TRRS connection on both front and back of PC, one I use for mic in, the other for speaker out) and the mic stopped being processed by OBS. After a very stressful set of minutes right before a scheduled livestream I finally figured out the OS to device to OBS mapping, and made a slight tweak in OBS Audio device selection (from default, if I recall correctly on Audio Input device) to the named device and all was well.

The joy of Win10.....
sometimes one knows too much.... the fix was relatively easy [just something I'd never dealt with previously...so didn't know to check it]
In OBS 26, there is now a dropdown above the Scenes/source list when selecting an Audio Input device, with a listing in my case of "Default", plus 2 different camera drivers which also have audio (webcam, and PTZ NDI connected camera)... line is isn't currently connected, as I'm pretty sure that should appear as well [listed as Realtek Audio something or other]
So either in Windows 10 Sound settings, or in OBS's Device selection for the Audio Input, make sure the right item is listed. at least that was my fix as the default had changed (not an OBS issue)... so making the default be the expected thing within the OS, and specifically selecting the device in OBS.. wither worked as the fix for me

Thank you for you response!

 

[segraham]

I found fix!

One issue I had before this issue happened is that the desktop Line In is connected to the sound board; I had to configure the sound in OBS as “Audio Output Capture” in order to get the sound to stream onto FB. I would have figured this should be configured as “Audio Input Capture”; was confusing...

After this MS Update, here is what I had to do to fix:
1. set the OBS app to run as Admin
2. reconfigure the audio to “Audio Input Capture”; as I would expect

I still want to research what the security patch did in this update!

 

[Lawrence_SoCal]

Running OBS as admin typically is done when you have hardware resource scheduling constraints (ie asking PC to do more than there are resources to do it), so you want to prioritize OBS over other processes/software. This audio shouldn't require being admin