START HERE
In Voicemeeter Banana, A1 is a physical listening output and B1/B2 are virtual mixes other apps can record. Send the intended stream sources to B1 and select Voicemeeter Out B1 in OBS. For voice chat, send your mic to B2 while leaving B2 off on the chat-return strip.
Use Banana and match the current device names
This recipe is for Voicemeeter Banana on Windows, not Standard or Potato. Install from VB-Audio and restart Windows as the installer instructs. Save your current Windows and app device choices before rerouting them, so you can restore a direct microphone/headphone path if needed.
Newer drivers call the recording endpoints Voicemeeter Out B1 and Voicemeeter Out B2. Older guides call them Voicemeeter Output and Voicemeeter Aux Output. The playback endpoints Voicemeeter Input and Voicemeeter Aux Input feed sound into the mixer. Do not choose an Input device when OBS is asking which recording device to capture.
Choose the devices before enabling routes
- Open Banana. Set A1 under Hardware Out to your physical headphones or interface output.
- Choose the physical microphone on Hardware Input 1. Speak and verify that strip’s meter.
- Set the game’s playback device, or the Windows playback default if that is your intended scope, to Voicemeeter Input. Its sound should reach the VAIO virtual-input strip.
- In Discord or your call app, choose Voicemeeter Aux Input as speakers/output and Voicemeeter Out B2 as microphone/input.
- In OBS, capture Voicemeeter Out B1 once with an Audio Input Capture source. Disable other captures of sound that this mix already contains.
Choosing the Windows default affects apps that follow that default; it is not a promise that every already-running game will switch. Reopen or reselect output in a stubborn application, then check the expected strip before continuing.
Apply this routing table
| Input strip | A1 headphones | B1 OBS | B2 chat mic |
|---|---|---|---|
| Hardware Input 1: microphone | Off initially | On | On |
| VAIO: game/PC playback | On | On | Off |
| AUX: friends’ voices | On | On if the stream should hear them | Off |
The B2 button on the AUX return must stay off in this recipe: that prevents friends’ voices being sent back as your microphone. B1 controls the broadcast mix independently. Turn B1 off on AUX if a conversation should stay off stream, then verify that no separate OBS desktop capture is still recording it.
Leave OBS monitoring off for this mixed input while establishing the route. You already hear game and chat through A1; returning the OBS mix to a device being captured again can create a loop.
Prove the buses one sound at a time
First speak without a game or call running. Hardware Input 1, B1, B2, and OBS should respond; your headphones need not play your own voice. Next stay silent and play the game. VAIO and B1 should respond while B2 stays quiet. Finally have a friend speak: AUX and A1 should carry the voice, and B1 should follow your chosen stream setting.
Record that three-part sequence in OBS. Use the call app’s own microphone test to confirm it receives only your voice. A B1 meter proves a mix exists, but not that OBS selected B1. A moving AUX meter proves a friend reached Banana, but not that the friend should be in the recording. Each checkpoint has a specific purpose.
Recover from silence, doubling, or device changes
- No headphones: verify A1 still names the connected physical output and that A1 is enabled on the relevant strip.
- OBS silent: verify the source is Out B1, the intended strips feed B1, and OBS’s recording track includes that source.
- Friends hear themselves: check AUX-to-B2 first, then look for other return capture or open speakers.
- Audio doubled: compare the B1 mix with OBS global Desktop Audio, a second mic source, and any monitoring return.
- Problems after a driver update: reselect named devices in each app; saved selections may point at replaced endpoints.
Keep initial levels conservative and verify the combined mix stays below clipping—follow how to balance your mic, game, Discord, and alerts in OBS and verify headroom in the live stream LUFS loudness checker. Do not lower every buffer value while diagnosing a routing error. Once the table works, adjust performance separately and keep a saved working configuration. For a simpler single-cable setup or sending an OBS scene mix into a voice call, compare the Windows & OBS routing helper and the OBS Virtual Camera audio guide.
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.