Global audio devices and scene-specific audio sources have different scopes. Use one intentional route per device, then record every transition to confirm the microphone and other sounds appear only where planned.
Plan which sounds belong in each scene, choose global or scene-specific device capture, and verify the transitions in a saved recording.
In this guide
Before you start
- A duplicate scene collection and a written scene-by-scene audio plan.
- A microphone or other device with a recognizable harmless test sound.
Write the scene audio plan before moving sources
List the scenes and the sounds each should contain. For example, a talking scene may need the microphone, a break scene may need only a permitted music source, and a demonstration may need microphone plus app audio. Do not assume that hiding the camera also changes the microphone.
OBS offers device capture through global Audio settings and through audio sources inside scenes. Its documentation warns that capturing the same device both ways can cause echo. Decide which scope serves the plan before adding another copy of a microphone source.
Identify every route for the device
Speak into the microphone and note which mixer entries respond. Inspect global Audio settings and the sources in each affected scene, including nested scenes. The same physical device can be present through more than one route, so a source name alone is not a complete inventory.
Keep the original configuration available. If you remove a global microphone route, make sure the intended speaking scenes receive the replacement before using the setup. A transition that accidentally loses speech can be as disruptive as one that keeps a microphone audible during a break.
Build and test the scene-specific route
Choose one capture scope
For a device that should exist only in selected scenes, configure the appropriate Audio Input or Output Capture source there and avoid capturing that same device globally as well.
Look for: The device has one explainable path into the planned scenes.
Check every scene in the plan
Visit the speaking, break and presentation scenes while making a harmless test sound. Inspect their sources and mixer behavior, including any shared nested scene.
Look for: Each scene contains the audio routes described in the plan.
Record the transitions
Make a local recording while speaking a scene label before and after each change. Include a pause in the break scene, then play the whole file.
Look for: The saved output confirms where the device is audible and whether any transition duplicates or loses it.
Use a reliable mute for a genuinely private moment
A scene arrangement is something to verify, not a substitute for an immediately available microphone mute. If you need to hold a private conversation, use the known mute control and confirm the output state. Keep that action simple enough to perform even when a scene transition behaves unexpectedly.
Do not infer silence solely from a hidden source icon or from what you hear in your headphones. Monitoring and output are separate paths in OBS. A source can be heard locally for a reason that differs from the recording, so the saved sample remains an important check.
Revisit the plan after sharing or nesting sources
Adding a shared overlay scene that contains audio can change the route into its parents. After a structural layout edit, repeat the scene-labeled recording rather than assuming the old audio plan still holds. Keep visual components free of accidental audio when their purpose is purely decorative.
Save the final scene audio plan with the collection. When another person adds a scene, they should know whether a microphone is global, reused from an existing source or intentionally absent. This makes the next change a clear routing decision instead of another round of unexplained mixer entries.
Still stuck?
The microphone remains audible on BRB.
Trace global devices, scene-specific sources and nested scenes, then use the known mute control while correcting the unintended route.
Sources & references
Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.
- OBS — Audio Sources ↗Checked 2026-11-04
- OBS — Audio Mixer Guide ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗