How is Voicemeeter organized (Strip & BUS)

All Guides to explain how to do everything with Voicemeeter...
Locked
Vincent Burel
Site Admin
Posts: 2237
Joined: Sun Jan 17, 2010 12:01 pm

How is Voicemeeter organized (Strip & BUS)

Post by Vincent Burel »

Voicemeeter is designed as a mixer, with audio inputs and outputs. The inputs are managed by STRIP, the outputs are managed by BUS.

The input strip is there to process sound sources such as a recording audio device (microphone), or an audio application (Spotify, YouTube, Netflix, Discord...) or possibly an incoming VBAN stream.

The output BUS is there to process the mixes of the sources assigned to it and output them to an audio playback device (speaker), or an audio application (Audacity, OBS, Teams, Discord, etc.) or possibly an outgoing VBAN stream.
VoicemeeterBananaExplodedView.png
VoicemeeterBananaExplodedView.png (569.26 KiB) Viewed 44 times

BUS Assignation buttons (A1, A2, A3... B1, B2...) allow sending a source (Strip) to a BUS. In other words the BUS is the output MIX containing the assigned audio sources.

VoicemeeterInternalRoutingDiagram.jpg
VoicemeeterInternalRoutingDiagram.jpg (125.32 KiB) Viewed 44 times

Voicemeeter Potato is just providing more Strips and BUS... and more processing again per Strip and BUS.

Audio processing offered in strip are made to manage and transform sound sources (EQ, Color panel, Compressor, Gate, Denoiser, Voice Modeler, Limiter...) While Audio processing offered on BUS are made to manage the sound of the mix and consequently the final output sound.
VoicemeeterPotatoExplodedView2.png
VoicemeeterPotatoExplodedView2.png (740.32 KiB) Viewed 44 times
Locked