Using Voicemeeter Banana for Advanced Audio Routing in Streams: A Comprehensive Guide

You're a streamer, and your audio setup feels like a tangled mess of wires, virtual or otherwise. You want game audio for your viewers, Discord chat only for you (or for everyone, sometimes), background music that doesn't trigger DMCA strikes, and your microphone to always sound pristine. But Windows default audio routing? It's just not cutting it.

You've heard whispers of "Voicemeeter Banana" – a powerful, free virtual audio mixer that promises ultimate control. But diving in can feel like learning a new language. This guide is for you: the creator who's ready to take charge of their audio, understand the core logic, and build a reliable sound blueprint for their stream.

The Pain Point: Why Basic Audio Just Isn't Enough

Most streamers start with a simple setup: mic into PC, headphones on, game audio plays. As you grow, complexity escalates. You add:

• Voice chat (Discord, Teamspeak)
• Background music (Spotify, browser tabs)
• Alerts and sound effects
• Dedicated VOD tracks (to exclude music)
• Multiple monitors or headphones

Suddenly, you're wrestling with Windows sound settings, trying to send specific application audio to different places. Can your viewers hear your music but not your private Discord call? Can you hear your game, but your viewers only hear your commentary? Without granular control, these scenarios become frustratingly difficult to manage.

Voicemeeter Banana (VMB) steps in as a software solution to this very real problem. It acts as a virtual mixing console, allowing you to route audio from any application or physical input to any output — including virtual outputs that other software (like OBS Studio) can then pick up.

Voicemeeter Banana's Core Logic: Inputs, Outputs, and Busses

To demystify VMB, think of it like a traditional hardware mixer, but all inside your computer. It operates on a straightforward principle of inputs and outputs, connected via "busses."

Hardware Inputs (Physical)

These are your real-world audio sources plugged into your computer. In VMB, you'll see three "Hardware Input" strips on the left:

• Mic: Your XLR or USB microphone.
• Aux Input: Often used for a secondary physical input, like a console capture card's audio output or a dedicated music player.

Virtual Inputs (Software)

These are the magic of VMB. They allow applications to send their audio directly into VMB, instead of straight to your speakers. VMB provides two primary virtual inputs:

• Voicemeeter VAIO: A general-purpose virtual input where you'd direct most applications (games, browser, Spotify).
• Voicemeeter AUX VAIO: A secondary virtual input, perfect for isolating specific audio like Discord or a browser tab you want separate control over.

These virtual inputs appear as standard audio devices in your Windows Sound Settings, allowing you to choose them as output devices for individual applications.

Busses (Outputs)

This is where VMB shines. Audio from your inputs gets routed to one or more "busses." Each bus can then be sent to a physical output (like your headphones) or a virtual output (like the audio track OBS picks up).

• A1, A2, A3: Hardware Out: These correspond to your physical audio output devices. A1 is typically your main listening device (your headphones or speakers). A2 and A3 can be used for secondary monitors, a dedicated stream deck speaker, or even sending audio back into a physical mixer.
• B1, B2: Virtual Out: These are crucial for streaming. B1 is your primary "Stream Mix" — OBS Studio (or other streaming software) will listen to this. B2 can be used for a separate VOD track, a "clean" audio mix without music, or specific routing for other software.

The key is that for each input, you can toggle which 'A' and 'B' busses it sends its audio to. Want your mic to go to your headphones (A1) and the stream (B1)? Enable A1 and B1 on your mic input strip.

Building Your Audio Blueprint: A Practical Streaming Scenario

Let's set up a common, yet powerful, audio routing configuration for a streamer using Voicemeeter Banana. Our goal:

• Microphone: Heard by you, Discord, and the stream.
• Game Audio: Heard by you and the stream.
• Discord Chat: Heard by you, but *not* the stream.
• Background Music (Spotify/Browser): Heard by you and the stream, but with an easy mute for DMCA-sensitive moments.

Initial Setup Checklist

1. Download & Install Voicemeeter Banana: Get it from the official VB-Audio website.
2. Reboot: Crucial after installation for the virtual devices to appear correctly.
3. Set Windows Default Devices:
   • Playback Default: Set to Voicemeeter Input (VB-Audio Voicemeeter VAIO). This sends all general Windows audio (games, browser default) into VMB's VAIO input.
   • Recording Default: Set to Voicemeeter Output (VB-Audio Voicemeeter VAIO). This is what applications like Discord will try to use as your microphone, which we'll override.
4. Identify Your Hardware: Know your physical microphone and your headphones/speakers in Windows Sound Settings.

VMB Configuration Steps

1. Set Your Hardware Out (A1):
   • In the top right, click "A1" under "Hardware Out."
   • Select your primary listening device (e.g., WDM: Headset Earphone (Your Device Name)). Use WDM for lower latency where available.
2. Route Your Microphone:
   • On the first "Hardware Input" strip (leftmost), click "Select Input."
   • Choose your physical microphone (e.g., WDM: Microphone (Your Device Name)).
   • Enable "A1" (so you can hear yourself, if desired, or for monitoring).
   • Enable "B1" (to send your mic to the stream).
   • In Discord, set your Input Device to Voicemeeter Output (VB-Audio Voicemeeter VAIO). This sends your mic (which is routed to VAIO via 'B1' on its strip) directly to Discord.
3. Route Game Audio:
   • Since we set Voicemeeter Input as the default playback device, game audio will automatically go to the "Virtual Input (Voicemeeter VAIO)" strip in VMB.
   • On this strip, enable "A1" (so you hear the game).
   • Enable "B1" (so the stream hears the game).
4. Route Discord Chat (Isolate from Stream):
   • In Discord's Audio Settings, set its Output Device to Voicemeeter Aux Input (VB-Audio Voicemeeter AUX VAIO).
   • In VMB, on the "Virtual Input (Voicemeeter AUX VAIO)" strip, enable only "A1" (so you hear Discord).
   • Crucially, DO NOT enable "B1" on this strip. This ensures your stream does NOT hear Discord chat.
5. Route Background Music (Spotify/Browser Tab):
   • Open Spotify or your browser. In Windows Sound Settings -> App volume and device preferences, find Spotify/your browser.
   • Set its output to Voicemeeter Input (VB-Audio Voicemeeter VAIO) (the same as your game, or you could use AUX VAIO if you want more dedicated control).
   • On the "Virtual Input (Voicemeeter VAIO)" strip (or AUX VAIO, depending on your choice), ensure "A1" is enabled (so you hear the music) and "B1" is enabled (so the stream hears the music).
   • You can use the fader on this strip to adjust music volume relative to your mic/game. Consider adding a Macro Button to mute this strip's B1 output for quick DMCA muting.
6. OBS Studio Setup:
   • In OBS, go to Settings -> Audio.
   • Set your Desktop Audio to "Disabled."
   • Add an "Audio Input Capture" source. In its properties, select Voicemeeter Output (VB-Audio Voicemeeter VAIO). This picks up everything routed to B1.
   • This single source now contains your mic, game, and music — everything you've sent to B1.

What This Looks Like in Practice: The "Stream Mix"

With this setup, your OBS audio input (Voicemeeter Output) will contain a perfectly balanced mix of your microphone, game audio, and background music, all controlled by VMB's faders and mute buttons. Your Discord chat is present in your headphones (A1) but entirely absent from the stream's audio (B1).

Community Pulse: Navigating the Learning Curve

For many new users, Voicemeeter Banana can feel like a labyrinth initially. Common feedback patterns often revolve around:

• Overwhelm: The sheer number of buttons, faders, and options can be daunting. "Where do I even start?" is a frequent sentiment.
• Driver Confusion: Understanding the difference between WDM, MME, KS, and ASIO drivers, and which to select for optimal performance (generally WDM for outputs, but sometimes MME for inputs to avoid issues) is a hurdle.
• Windows Sound Settings Interaction: Realizing that VMB doesn't exist in a vacuum, and proper configuration in Windows Sound Settings (default playback/recording devices, app-specific outputs) is critical for VMB to function as intended.
• Troubleshooting Woes: "Why can't I hear anything?" or "Why can't my viewers hear X?" often leads to deep dives into individual application settings, VMB routing, and Windows defaults. It's a process of elimination.
• The "Aha!" Moment: Despite the initial struggles, there's a recurring theme of satisfaction once VMB "clicks." Streamers describe it as unlocking a new level of audio control they didn't know was possible, making the effort worthwhile.

The key takeaway from the community is patience. VMB has a steep learning curve, but the investment pays off with unparalleled audio flexibility.

Maintaining Your Advanced Audio Setup

Once you've got your Voicemeeter Banana setup dialled in, it's not a "set it and forget it" solution, although it can be quite stable. Regular checks and knowing what to look for will keep your audio pristine.

What to Review Regularly:

1. Windows Sound Settings:
   • Default Playback/Recording: Accidentally changing these (e.g., plugging in new headphones) can break your VMB routing. Periodically confirm Voicemeeter Input is your default playback and Voicemeeter Output is your default recording.
   • App Volume and Device Preferences: Verify that specific applications (Discord, Spotify) are still routed to their intended VMB virtual inputs. Windows updates or application reinstalls can sometimes reset these.
2. Voicemeeter Banana Settings:
   • A1 Output Device: Ensure your main listening device is still correctly selected in the Hardware Out A1 slot. Driver updates can sometimes cause this to revert.
   • Input/Output Levels: Check your gain staging. Are your microphone levels healthy without clipping? Is your game/music audio balanced against your voice?
   • Bus Routing (A1/B1/B2): Briefly review each input strip to confirm it's sending audio to the correct busses (e.g., Discord still only to A1, not B1).
3. OBS Studio Audio Sources:
   • Audio Input Capture: Ensure OBS is still listening to the correct VMB virtual output (e.g., Voicemeeter Output (VB-Audio Voicemeeter VAIO)).
   • Monitor Audio: If you use OBS's monitor features, ensure they aren't creating unwanted feedback loops with VMB.
4. Software Updates:
   • Voicemeeter Banana: Keep an eye out for VMB updates, as these can bring bug fixes or new features. Install them carefully, usually requiring a reboot.
   • Audio Drivers: Update your physical audio interface/headset drivers from the manufacturer's website. Sometimes, these updates can affect how VMB interacts with your hardware.
5. Test Your Mix: Before going live, do a quick sound check. Record a short clip of yourself talking, playing a game, and listening to Discord/music. Play it back to confirm everything is routed correctly and balanced. Use the streamhub.shop soundboard if you need some quick audio tests.

By regularly reviewing these points, you can proactively catch potential audio issues before they impact your stream quality and viewer experience.

2026-03-04