START HERE
OBS Virtual Camera carries video. Choose a microphone separately in the receiving app. If you need audio from OBS media or filters, route the selected OBS sources through a virtual audio cable and choose its recording endpoint as the call’s microphone. Do not feed the call’s received audio back into that mix.
Decide whether the call needs an OBS audio mix
If OBS only supplies a scene layout or webcam picture, select your ordinary microphone directly in Zoom, Teams, Discord, or the browser meeting. This keeps the audio path simple. Start OBS Virtual Camera for the picture and select OBS Virtual Camera as the call’s camera; the microphone selector is a separate choice.
A separate audio mix is useful when a presentation includes an OBS Media Source, several microphones, or processing that must reach the call. The OBS developer’s video-only explanation confirms why selecting the virtual camera alone cannot deliver those sounds. A moving OBS meter does not show what the meeting’s microphone input is receiving.
Build a Windows VB-CABLE route
The following is one Windows route. macOS and Linux need an appropriate virtual audio device or graph for their platform; the Windows endpoint names below do not apply everywhere.
- Install VB-CABLE from its official site and restart when instructed. Follow the VB-CABLE setup guide if its devices are missing.
- In OBS Settings → Audio, set the Monitoring Device to CABLE Input. This playback endpoint receives the sound OBS sends.
- Enable monitoring for only the OBS sources the call should hear, such as your microphone and the presentation clip.
- In the meeting app, select CABLE Output as its microphone. Set its speakers to your physical headphones.
- Play a brief clip and speak separately. Check the meeting app’s input meter or test recording, then confirm with a second participant using headphones.
Do not select CABLE Output as an OBS input in this same route. That would bring the outbound mix back into the program that created it.
Know which mute controls the call
Recent OBS versions separate the source’s output-mute button from its monitoring button. In OBS 32.2, the redundant Monitor Only choice was removed from Advanced Audio Properties. If the call is listening to the monitoring mix, muting the source’s normal stream/recording output does not necessarily stop the call hearing it.
For a reliable emergency mute, use the meeting app’s microphone mute and verify it with the remote listener. Test individual OBS source controls if you need to mute just a presentation clip while continuing to speak. Older OBS screenshots use different monitoring labels, so judge the destination you are controlling, not merely whether a speaker icon looks muted.
Keep the return audio out of the send
Wear headphones and keep the meeting’s speaker output away from the virtual cable. If the call plays into CABLE Input, its participants can hear themselves coming back through CABLE Output. Likewise, monitoring a broad Desktop Audio source that already includes the call sends the return audio back into the meeting. You can double-check Windows virtual-cable endpoints in the Discord & OBS routing helper before joining a live call.
Prefer explicit sources for the material you need to share. Keep the meeting window’s audio out of that selection. If you intentionally capture a remote guest for a separate broadcast, build a distinct mix for the guest that excludes their own return. A single shared monitoring destination is not a complete multi-guest mixer.
A phone microphone can be another input, but it needs its own return path into OBS. Do not reuse the same cable for both the phone-to-OBS input and the OBS-to-call output.
Use a saved clip to narrow the fault
| What works? | Where to look |
|---|---|
| OBS recording works; call input meter stays still | OBS monitoring selection, CABLE Input destination, and the call’s CABLE Output selection. |
| Call meter moves; participants hear no sound | Meeting mute, input level, permissions, and the app’s own test/recording behavior. |
| Speech works; music disappears or pumps | The call app’s speech-oriented processing. Test its documented music/original-audio settings if appropriate. |
| Participants hear repeated voices | Their return audio is entering your outbound mix or an open speaker is feeding the microphone. |
Rehearse exactly what you will send
Test speech, a clip with audio, a scene change, and a deliberate mute. Ask the listener what they hear during each action instead of relying only on local playback. Check picture-to-sound alignment at the receiving end; a camera path and a separate audio path can have different delays.
When finished, turn off the relevant monitoring routes and restore OBS’s previous monitoring device if you use headphones for normal streams. Leave the next session with a named, documented destination so a future “monitor” click does not unexpectedly send private audio into a call.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.