32.1 audio output routing has changed?

L

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.
 
You must log in or register to reply here.
Back
Top