V29.1.3 Upgrade Problems

[davdue]

We upgraded from V27.1.3 to V29.1.3 on Wednesday night. We got the dialog box below but it also had NDI listed

We upgraded the NDI plugin and NDI was working fine in OBS. This morning it won't work. Upon more research and looking closely at the OBS NDI plugin release page I realized that we needed to upgrade the NDI tools to V5. I did that and it still doesn't work.
When I go into the properties for the NDI source I don't see anything but the local computer listed for sources. Here is the source that was selected previously for NDI

Any ideas what is going on?

Also we do not have any audio from our sound system in OBS. We are using the ATEM Mini mic 1 input. We see audio in the ATEM software but nothing in OBS. We select the audio source within the scene/source list and have all the audio inputs disabled (nothing was changed here).

TIA

 

[PaiSand]

If the issue is in the plugin please contact directly on the plugin page sub forum for support.

 

[davdue]

We figured out the NDI problem. Some how the computer was on wifi not the Ethernet network. So it wasn’t seeing the other computer. We got that fixed. Still have the audio problem.

 

[Lawrence_SoCal]

Also we do not have any audio from our sound system in OBS. We are using the ATEM Mini mic 1 input. We see audio in the ATEM software but nothing in OBS. We select the audio source within the scene/source list and have all the audio inputs disabled (nothing was changed here).

I assume you mean you have all OTHER audio inputs disabled (not ALL, which would include your mic/ATEM mini input)?
Once you enable the mic (whatever you've named it), does that show up in sound meter in OBS Studio? I'm assuming it does (if not, time to fix your Audio Source Input), but shows no activity? if yes, I'd start with the basics of making sure OBS Studio granted access (security permission) to access that mic. Some of these may help (or they may be way too basic)... OBS Audio related articles

• https://obsproject.com/wiki/Understanding-The-Mixer
• https://obsproject.com/wiki/Windows-10-App-Volume-Device-Preferences
• https://streamershaven.blog/softwar...hlight/advanced-audio-properties-obs-and-you/
• https://support.focusrite.com/hc/en...e-in-OBS-Open-Broadcaster-Software-on-Windows

My standard suggestion (for years now)... make sure Sources working at Operating System level first, with OBS Studio NOT running (not just in background). In your case, you mention seeing audio in ATEM software. One thing to account for is software that locks exclusive access to a source (like OBS Studio tries to do). As such, you have to be account for any ATEM software requirements/config if both ATEM software and OBS studio trying to get exclusive lock on physical hardware audio interface (OS, OBS Studio, and ATEM driver updates could have changed behavior, so time to double-check). I'm not an ATEM user, so I can't comment if this is a known issue/consideration... just thinking aloud

 

[davdue]

here is what we have for audio settings

yes it shows up in the sound meter in OBS but no activity

Here is the activity in the ATEM software

The thing is that all we did was upgrade OBS from 27.1.3 to 29.1.3 and lost audio so maybe something changed with how OBS locks the audio like you are saying above. We will read some of those articles and see if they shed any light.

 

[davdue]

One more thing I was thinking about is where or how can we look to see what audio is coming into OBS or can we assume that if we have nothing in the sound meter then nothing is coming into OBS? Is that when we have to look at the Windows level? We went into sound properties and the microphone is 0 all the time there as well.

 

[Lawrence_SoCal]

One more thing I was thinking about is where or how can we look to see what audio is coming into OBS or can we assume that if we have nothing in the sound meter then nothing is coming into OBS? Is that when we have to look at the Windows level? We went into sound properties and the microphone is 0 all the time there as well.

Yup, that means Windows OS audio-subsystem doesn't have/see content in that device, which means OBS Studio won't as well (I think... and from what I surmise fromn the above, without actual OBS Studio log, and more OS config details [OBS Studio log does not, probably can't reliably, if at all, provide physical and processing path for audio & video. The end user has to know and provide such info. This includes understanding the configuration of the audio data path and exact processing steps configured (fileters, effects, etc) before getting to OBS Studio).

Others on this forum have much more knowledge about the Windows Audio sub-system, and its 'limitations' .. it works, somewhat for me, but even I'd like a bit more robust capability.

My suspicion ... there is an interaction between Operating System updates, ATEM driver changes, and the OBS Studio upgrade that came together to cause your issue. As you are seeing the issue at OS layer, it was NOT just OBS Studio upgrade. Now, the more important thing is - how to fix? and I suspect - there are multiple options, with different Pro's & Con's (the joy of IT... 'it depends' )

First, I'd start with why you have a Mic/Aux (2)? shows disabled in Global, but in your Source list? a duplicated source? or ?? something from the 2 mics in ATEM ?
Then, do you use Desktop Audio at all? I don't, and have disabled it as well... that way the ONLY sounds in our stream/recordings will be exactly what I want it to be. If I play anything pre-recorded, it is its own audio source. I never have any need/use for Desktop Audio
As for ATEM connected mic,
- One approach would be to make sure ATEM s/w outputting to windows Audio system?
- though I'd think it would be better getting audio direct from ATEM into OBS Studio (why go through extra processing layer (OS) if no need? granted there may be good reason I'm just not thinking about... ) . I don't know ATEM/Black Magic audio hardware so can't comment more specifically. Many professional DAWs (digital audio workstations) don't output to Windows Audio sub-system (though starting to change). There are ways with VST plugins on DAW and OBS Studio to create a direct connection (Reaper VST comes to mind, if I'm remembering correctly). There may be (hopefully) a better way with the Blackmagic ATEM mini you have