New to streaming and experiencing audio echo with everything. If I turn the desktop audio off the echo goes away but then obviously cant hear anything. I have muted my mic and only run the desktop audio and still getting an echo. I am watching my own stream on youtube but its muted, not sure if OBS picks up the audio even if youtube is muted. Also how would you clip a video and show it back live without having the stream double play audio?
Audio Echo
- Thread starter SirHella
- Start date
Do you use the Monitor? Does it use the same device that the Desktop audio picks up? If yes to both, then that's a loop that you need to break.
The Desktop audio is literally ALL that the selected device is doing. Including what OBS sends to it. That's just how Windows (and pretty much every other system) works. There's no "mix minus", as we call it.
The Desktop audio is literally ALL that the selected device is doing. Including what OBS sends to it. That's just how Windows (and pretty much every other system) works. There's no "mix minus", as we call it.
Hey I use the desktop audio to capture my audio but monitor is off. So what should I do? I want game plus game chat? I guess I'm just confused by this
Is the Monitor off for *everything*? Anything at all that has the Monitor on, will go to the device that the Monitor is set for, and a Desktop audio source that is set for that same device will pick that up.
Draw a diagram of where and how each signal flows through your rig. That's a critical part of any serious system design. You build that diagram from the settings, but it's far more understandable than the settings themselves are. When you change something, change the diagram first, and *then* change the settings to match the new diagram.
- If the Desktop source is not Monitored, then you only get a single echo: the original from the source that you expect it from, and a slightly delayed copy from the Monitor -> device -> Desktop loop.
- If the Desktop source *is* Monitored, then the echo repeats forever.
Draw a diagram of where and how each signal flows through your rig. That's a critical part of any serious system design. You build that diagram from the settings, but it's far more understandable than the settings themselves are. When you change something, change the diagram first, and *then* change the settings to match the new diagram.
Weirdest thing is it worked the night before last and I didn't change anything lol now just the endless echo
Hmm... OBS should not be outputting any audio then, but you're still getting the echo?
I'm pretty sure you've missed something. Can you post some screenshots?
THAT could be because you're still using "Default". That setting is only useful to prove that a fresh installation works. The same thing that makes it useful for that, is also a ticking time bomb for everything else, that goes off in the form of everything working just fine and then breaking for no reason at all.
The reason it breaks, is because "Default" defers the choice of device to the operating system and whatever logic *it* has. Often, it'll select the last device that appeared, whether you plugged it in or it was asleep and just happened to wake up. It can't tell the difference. So a mic that is always plugged in, might "just not work" all of a sudden, because a bluetooth headset that you don't use, somehow happened to connect just before you went live.
Or, maybe you do have different selections for your Monitor and for your Desktop capture, one directly and one as Default, and you unplugged the one that Windows used to have as Default. Or it went to sleep, or disconnected, or whatever. Windows automatically switched the Default device to something else, which happened to be the same one that the other connection in OBS is set for directly. So now they're looking at the same device. Same device = echo.
ALWAYS select a *specific* device in your audio settings! Do not use Default!
Okay so is it best to have global audio devices or scene specific devices? It was global devices yesterday but im in the process of switxhing to scene specific now thinking that could have caused an issue. What should I change that default to for monitoring device, my headset? Do people usually have the Monitor active? Thanks for the help. Everything else is like perfect except for this audio lol.
Makes sense to what you posted about windows deciding on what device "default" is. I currently have all set to disabled and set scene specific audio. I have the Monitor set to my headset under settings->audio not sure if that should be something else.
I can get screen shots if needed. I truly appreciate the help!
Makes sense to what you posted about windows deciding on what device "default" is. I currently have all set to disabled and set scene specific audio. I have the Monitor set to my headset under settings->audio not sure if that should be something else.
I can get screen shots if needed. I truly appreciate the help!
The Monitor is for you to listen to, similar to the headphones that you might see on a professional mixing console. If you personally need to hear something that comes from OBS, in the moment, that's what it's for. Just pay attention to the routing, and don't make a loop.
I greatly prefer global sources. Keep the scenes silent. That's because (historically at least) scene-specific audio would only cut, not fade like I wanted. So I keep everything global, and do this instead:
Or something like this to control a DAW (Digital Audio Workstation), which handles *all* of the audio on a larger rig, including my headphones or speakers:
Not all signals in that DAW are audio, and the message shown here actually controls one of the "other" signals (on channel strip 1). The hard cut-on from this (0dB), goes into the side-chain of a Gate, so I can use the Gate's timing controls to create the fade.
I greatly prefer global sources. Keep the scenes silent. That's because (historically at least) scene-specific audio would only cut, not fade like I wanted. So I keep everything global, and do this instead:
Advanced Scene Switcher
This plugin will allow you to automate various tasks using "Macros". Macros consist of a list of conditions under which a list of actions will be performed. Examples and guides can be found in the wiki. Feel free to contribute! If you run...
obsproject.com
Or something like this to control a DAW (Digital Audio Workstation), which handles *all* of the audio on a larger rig, including my headphones or speakers:
Not all signals in that DAW are audio, and the message shown here actually controls one of the "other" signals (on channel strip 1). The hard cut-on from this (0dB), goes into the side-chain of a Gate, so I can use the Gate's timing controls to create the fade.
Lawrence_SoCal
Active Member
When you set Monitor On, and you are using something like Desktop Audio as a source, you are combining both Desktop Audio and a slightly delayed OBS Studio output (hence echo) to the Operating System speakers (by default). The echo is happening because you asked/configured for it (even if unintentionally).
As for not changing anything... usually something has changed, maybe an automated Operating System and/or driver update? and for the most basic? Do you stream your voice (ie use a microphone)? if yes, are you absolutely sure that Mic can't hear anything from the computer? If the Mic is picking up speaker audio, then you have an audio loop.
I don't need to hear/listen to anything on OBS PC, so I removed Global Desktop Audio from my Source. But, there is NOTHING audio originating on streaming PC that I want streamed (I'm not gaming.. only audio is 1 pre-recorded intro video and then external mixer).
As Aaron said, you need to map out audio or its real easy to cause problems (loops/echo). And if running that Beta OS Win11, all that much worse. And then there are audio drivers and more than can all 'complicate' matters. So, yes test after Windows Updates... and be prepared to fix device associations, and more.. the joy of the supposedly more user-friendly OS than Linux. For example, my Tier 1 business PC has sound software that adjusts incoming analog signals... and has caused issues on occasion.
Due to limitations of the Windows Audio sub-system (and some have indicated possible deficiencies in M$' associated audio APIs,) using Audio from a game, for example, is harder than it should be... but getting better in OBS (and Windows... ever so slowly). There are some things you'd like to do that simply aren't config options in Windows.
For reference, maybe some of these older articles (pre addition of Application Audio Capture feature in OBS v28) will help with overall audio understanding in OBS Studio
obsfanatic1979
Member
So you say :
1. Use headphones and the video audio will still be recorded in the recording?
With just that one change - open-air speakers to headphones - OBS doesn't know any different at all, and you've drastically shrunk the acoustic space that the "speakers" work in. From the entire room to just your ears. Hopefully, the bleed from that isn't enough for the mic to pick up.
Most of the time, bleed from headphones isn't a problem, but I *have* seen it happen, on stage, with the lead singer's click track (metronome) getting into his vocal mic. As long as you don't go crazy with the volume (don't hurt yourself), and you don't have earbuds half out, you should be fine.
obsfanatic1979
Member
where do I find the option of "open air speakers to headphones?"
It's not a software option. Physical wires and plugs...
obsfanatic1979
Member
OK thanks for replying so fast anyway!
I think I got it fixed by muting the audio for the videos on my end, but the audio/video appears on the recordings
Its not the best but its free, open source software -- good enough for a small-timer like me.
I think I got it fixed by muting the audio for the videos on my end, but the audio/video appears on the recordings
Its not the best but its free, open source software -- good enough for a small-timer like me.
That'll do it too.
Yeah, OBS's audio leaves a lot to be desired. I usually recommend that for serious work (doesn't take much, really), you pop out all of the audio to a DAW or physical console. Some sort of external tool, other than OBS. (There are some amazing free DAW's, by the way!)
Anyway, connect all of your audio stuff to the external tool - mics, speakers/headphones, etc. - not to OBS, do *all* of your audio work in the external tool, and then send the final finished result to OBS to pass through completely unchanged. OBS is completely silent now - no audio sources whatsoever - except for that one external feed.