32.1 audio output routing has changed?

Larry Groebe

New Member
It's entirely possible this is something I'm doing/not doing, but the new OBS with the new audio engine isn't routing audio properly in the way that it used to.

I'm using OBS as a rich Zoom source. With 32.0.4 I could set up a mike in one OBS input and turn its monitoring OFF; while leaving Monitoring ON for other inputs (streamdeck) and video clips inside scenes. I then routed monitor output specifically to my headphone jack. That worked wonderfully - I didn't hear myself, but everyone else did. With the new version, I can't do that. Either I can send everything to Zoom, including my mike, resulting in me hearing myself on a slight delay, or else nothing -- and the nice new monitoring buttons don't do anything.

Am I missing something? I have used VB Cable and Soundsource to help manage routing options, but I can't find any combination that works with 32.1. (It sure would be nice if OBS had a setting for main-output routing like it does for monitor routing. )
 
The 32.1 audio rewrite changed how monitoring interacts with the virtual camera output. In 32.0.4 the virtual cam just passed through whatever OBS was mixing, but now monitoring and main output are on separate buses.


What should still work: set your mic to Monitor Off like before, then in the new Audio panel click the headphone icon on sources you want to hear locally, and confirm Settings > Audio > Monitoring Device points at your headphones (not VB Cable). The main output/virtual cam should carry everything regardless of monitoring toggles. If Zoom is getting silence check that VB Cable isn't set as the monitoring device when you actually need it as main output, the new UI makes it easy to mix those up.
 
That's about what I *was* doing. And coming back to it today - today, it works as expected. That's good news.

Now, if I can just git the new version of OBS to QUIT. Mine refuses, and has to be force-quit every time.
 
If you don't mind me asking - where would I make the VB Cable my audio output? I was using the virtual cable to send audio to zoom, setting it as the monitoring device. But since the update, if I want to mute the microphone for both the recording (mainoutput) and the zoom conference (virtual cable/monitoring device), now i have to mute clicking on two buttons instead of just one as before. Is there something I should be setting up differently now that OBS has separated these two?
 
If you don't mind me asking - where would I make the VB Cable my audio output? I was using the virtual cable to send audio to zoom, setting it as the monitoring device. But since the update, if I want to mute the microphone for both the recording (mainoutput) and the zoom conference (virtual cable/monitoring device), now i have to mute clicking on two buttons instead of just one as before. Is there something I should be setting up differently now that OBS has separated these two?
Since Virtual Camera doesn't have audio, and OBS doesn't provide a way to send Main audio (the stream or recording) to a designated local output, you do need to use the Monitor to get audio to Virtual Camera, which as you found requires you to toggle both Monitor and Output for the mic when you want to mute it.

The more advanced solution is to use another piece of software to mix your audio and send it where you want it. Full-fledged DAW software is probably overkill, two lighter-weight options are SoundDesk and Caster. Those both let you configure multiple real or virtual outputs, and choose where every audio stream from every individual app goes. You mix it all there, and send your program stream to both OBS and Zoom, and your monitor to your headphones.
 
AT THE MOMENT (he says with cautious optimism, because it's working well but he doesn't know exactly why) OBS 32.1.1 and VB-Cable and Zoom seem to be playing well together. I don't know how OBS does it, but if I set Zoom's audio input to VB-CABLE, I get the program audio output from OBS. Since Zoom mutes all audio coming from me, then back in OBS I turn on monitoring for everything EXCEPT my microphone, and set OBS' monitoring output to "headphones." That setup seems to be working,

I will add that I also use (and love) Rogue Amoeba's paid audio apps - especially Soundsource and Audio Hijack. I often fire up the latter to help me record multiple sources simultaneously, and when I *don't* need OBS when using Zoom, I use Audio Hijack as an audio mixer/aggregator to combine signals to feed into Zoom.
 
Back
Top