Audio Routing for Streaming: Using Voicemeeter Banana and OBS

You've been there: struggling to balance game audio, Discord chat, background music, and your microphone, all while trying to keep it consistent for your viewers. Maybe your game's cutscenes blast viewers' ears while your voice is barely a whisper. Or perhaps you want to listen to private music without it broadcasting to the stream. Standard Windows audio settings and basic OBS inputs often hit a wall when you need granular control, leading to frustration and an unprofessional-sounding stream.

This is where tools like Voicemeeter Banana (VB) step in. VB isn't just an audio mixer; it's a virtual audio device matrix that can receive audio from multiple physical and virtual sources, mix them, apply effects, and send them out to multiple physical and virtual destinations. For streamers, this means the power to route specific audio channels to OBS, to your headphones, and even to a separate recording track, all independently.

Voicemeeter Banana: Your Virtual Mixing Desk Unpacked

Think of Voicemeeter Banana as a sophisticated virtual soundboard. It sits between your applications and your physical audio devices, giving you unprecedented control. Before diving into OBS, understanding VB's core components is crucial.

Core Concepts: Inputs, Buses, and Virtual Cables

• Hardware Inputs (MIC, AUX): These are where your physical microphones, capture cards, or other hardware audio devices connect. VB allows you to manage up to three hardware inputs.
• Virtual Inputs (Voicemeeter VAIO, Voicemeeter AUX VAIO): These are software inputs where applications can send their audio. Windows sees these as playback devices. You'll typically set specific applications (like your game, browser, or music player) to output to one of these virtual inputs. VB has two main virtual inputs.
• Buses (A1, A2, A3, B1, B2, B3): These are your output channels.
  • Hardware Out (A1, A2, A3): These are connected to your physical audio outputs (e.g., your headphones, speakers). You define which physical device corresponds to A1, A2, etc.
  • Virtual Out (B1, B2, B3): These are virtual outputs that other applications (like OBS) can "listen" to. Windows sees these as recording devices.

Initial Setup: Getting Sound In and Out

The first hurdle is getting sound into VB and then out to your ears. Here's a simplified path:

1. Install Voicemeeter Banana: Download and install it. A restart might be required.
2. Set Your Hardware Outputs (A1, A2, A3):
   • Open VB. On the far right, under "Hardware Out," click the "A1" button. Select your primary listening device (e.g., "WDM: Your Headset Name").
   • If you have secondary outputs (like speakers), you can assign them to A2, A3.
3. Route Your Microphone:
   • Under "Hardware Input 1" (or 2, 3), click "Select Input" and choose your microphone (e.g., "WDM: Your Mic Name").
   • Ensure the "A1" button under your mic input is active. This sends your mic audio to your headphones.
   • Also, activate "B1" or "B2" under your mic. This will create a virtual output that OBS can later capture for your mic.
4. Route System Sounds & Applications:
   • In Windows Sound Settings, go to "Sound Control Panel." Under the "Playback" tab, set "Voicemeeter Input (VB-Audio Voicemeeter VAIO)" as your default device. This sends most Windows sounds and applications to VB's "Virtual Input 1."
   • Ensure "A1" is active under "Virtual Input 1" in VB, so you hear these sounds.
   • To separate specific applications (like game vs. music): Use Windows "App volume and device preferences" (Windows 10/11 settings > System > Sound). Here, you can tell specific apps to output to "Voicemeeter Aux Input (VB-Audio Voicemeeter AUX VAIO)," which corresponds to VB's "Virtual Input 2."
   • Activate "A1" for "Virtual Input 2" as well, so you hear these sounds.
   • For OBS, you'll likely want to activate "B1" or "B2" (or both, depending on your OBS setup) for these virtual inputs.

2026-04-21

Integrating with OBS: Precision Control

Once VB is routing audio to your satisfaction, bringing it into OBS is the next step. The goal here is usually multi-track recording/streaming, allowing you to adjust levels post-stream or mute specific elements for VODs.

1. Add Audio Inputs in OBS: In OBS, under "Sources," add "Audio Input Capture" for each virtual output you want to use.
   • For your microphone, select "Voicemeeter Output (VB-Audio Voicemeeter VAIO)" if you sent your mic to B1.
   • For game/system audio, select "Voicemeeter Aux Output (VB-Audio Voicemeeter AUX VAIO)" if you sent game audio to B2.
   • You can also send a mix of everything to a single output like "Voicemeeter VAIO" (B1) and capture that in OBS.
2. OBS Audio Mixer Configuration:
   • In the OBS Audio Mixer, right-click any source and select "Advanced Audio Properties."
   • Here, you'll see a list of your audio sources and "Tracks 1-6."
   • For Streaming: Ensure all sources you want your audience to hear are checked under "Track 1" (this is your live stream mix).
   • For Recording/VODs: Assign different sources to different tracks (e.g., Mic on Track 2, Game on Track 3, Discord on Track 4). This lets you isolate audio for editing or to mute specific tracks from VODs (OBS Settings > Output > Recording > Audio Tracks).

Practical Scenario: The "Private Music" Setup

One of the most common requests is playing background music for yourself that doesn't go to stream, or music for stream that you can't hear. Here’s how VB handles the "private music" scenario:

1. Dedicated Music Player: Use a separate music player (like Spotify, VLC, a browser tab) just for your private music.
2. Route Music to a Specific Virtual Input: In Windows "App volume and device preferences," set this music player to output to "Voicemeeter Aux Input (VB-Audio Voicemeeter AUX VAIO)."
3. VB Routing:
   • In VB, under "Virtual Input 2 (Voicemeeter AUX VAIO)," ensure "A1" (your headphones) is active. This lets YOU hear the music.
   • CRITICALLY, ensure that "B1" or "B2" (your virtual outputs to OBS) are NOT active for this "Virtual Input 2." This prevents the music from going to OBS.
4. Stream Music: If you wanted *stream* music separate, you'd route that to "Virtual Input 1 (Voicemeeter VAIO)," ensure its "A1" is active (for you to hear), AND activate "B1" (or whichever virtual output you send to OBS).

This setup allows you to control exactly who hears what, giving you a private audio experience alongside your broadcast.

Community Corner: Navigating the Voicemeeter Maze

Voicemeeter Banana, while powerful, often presents a steep learning curve. Recurring feedback from streamers in forums and communities points to several common pain points:

• "My Audio Disappeared!": A frequent issue arises when default Windows devices are incorrectly set or changed, causing sound to vanish. Remembering to set VB as your default playback device in Windows, and selecting the correct physical output in VB's A1, is key.
• "It's Too Complicated!": The sheer number of inputs, outputs, and routing options can be overwhelming. Many advise new users to start with a basic setup (mic to B1, system sounds to B2) and gradually add complexity rather than trying to map everything at once.
• "Latency Issues": While VB itself is optimized, sometimes high buffer sizes or conflicting audio drivers can introduce latency. Users often find success by experimenting with VB's "System Settings / Options" (specifically the buffer settings for WDM, KS, and MME drivers) and ensuring their physical audio drivers are up to date.
• "Save My Settings!": Forgetting to save settings after a perfect configuration is a common mistake. VB doesn't automatically save on exit. Always use "Menu > Save Settings" to avoid redoing your work after a restart.

The Ongoing Mix: What to Review and Adjust

Your audio setup isn't a "set it and forget it" task. Changes in Windows updates, new hardware, or even new games can throw off your carefully calibrated mix. Regular checks ensure your stream's audio quality remains top-notch.

1. Windows Sound Settings: Periodically check your default playback and recording devices in Windows. Updates can sometimes revert these. Also, re-verify "App volume and device preferences" if you're experiencing unexpected routing.
2. Voicemeeter Banana Settings: Confirm your A1/A2 hardware outputs are still correctly assigned to your headphones/speakers. Review your input routing (A1/B1, A2/B2, etc.) to ensure applications are still going to the desired virtual inputs and outputs.
3. OBS Audio Mixer: Double-check "Advanced Audio Properties" in OBS. Are all the right sources enabled for Track 1 (stream)? Are your multi-track recordings still configured as intended? Ensure no unwanted sources are accidentally active on your main stream track.
4. Driver Updates: Keep your audio interface and other hardware audio drivers updated. Sometimes, an outdated driver can cause conflicts or introduce latency.
5. Test, Test, Test: Before going live, always perform a quick test stream or local recording. Listen back critically. Does everything sound balanced? Are there any unexpected echoes or missing audio?