Getting started#
VeeMeeter borrows Voicemeeter's vocabulary. Once you know four words (input, output, A bus, B bus) the whole window makes sense.
Strips#
Every column in the mixer is a strip. There are four kinds:
| Kind | Id | What it is | Example |
|---|---|---|---|
| Hardware input | hi1, hi2… |
A real capture device. | Your USB microphone |
| Virtual input | vi1, vi2… |
A virtual output device that applications play into. | Desktop, Voice chat |
| Hardware output | a1, a2… |
A real playback device: an A bus. | Speakers, headset |
| Virtual output | b1, b2… |
A virtual microphone that applications record from: a B bus. | Virtual Mic for Discord |
Virtual input = a fake speaker, virtual output = a fake mic
The naming follows the mixer's point of view: sound comes in through a virtual input (apps think it is a speaker) and goes out through a virtual output (apps think it is a microphone).
Hardware inputs are wrapped in an internal, hidden node. Moving the fader of
hi1 changes VeeMeeter's gain, never your system microphone volume.
Virtual cables#
A cable connects one program's output straight to another program's
input, like VB-Cable on Windows. Adding one (+ Add → Virtual cable, or
veemeeter ctl add c "OBS to Discord") creates two devices:
| Device | Kind | Use it as… |
|---|---|---|
| OBS to Discord | output (sink) | the output of the program that sends the audio |
| OBS to Discord (output) | input (virtual microphone) | the microphone of the program that receives it |
The cable has its own fader, mute, VU meter and effects, and its A/B buttons let you also listen to it (or mix it into a virtual mic). In the Applications panel, picking a cable sends a playing app into it and plugs a recording app onto its output side.
Routing#
Each input has one toggle button per output (A1, A2, B1…).
Turn a button on and that input is mixed into that output. An input can feed
any number of outputs, and an output sums every input routed to it.
The default first-run setup looks like this:
flowchart LR
subgraph Inputs
hi1["🎤 hi1 · Microphone"]
vi1["🖥️ vi1 · Desktop<br/>(default output)"]
vi2["💬 vi2 · Voice chat"]
end
subgraph Outputs
a1["🔊 A1 · Speakers"]
b1["🎙️ B1 · Virtual Mic<br/>(default input)"]
end
hi1 --> b1
vi1 --> a1
vi2 --> a1
- Apps play into Desktop by default (it carries the default-device star), and you hear it on A1.
- Point your voice app's output at Voice chat to give calls their own fader.
- Your microphone goes to B1; select Virtual Mic as the microphone in Discord, OBS, etc.
Classic recipes#
Let your friends hear your music
Turn on B1 on the Desktop strip. Desktop audio is now mixed into the
virtual mic, together with your microphone. Lower Desktop's fader so your
voice stays on top.
Stream audio without the call
Add a second virtual output (veemeeter ctl add b Stream), route
Microphone and Desktop to it but not Voice chat, and select it as the
audio source in OBS.
Headset and speakers at once
Add a hardware output for the headset
(veemeeter ctl add a Headset --device <node name>), then toggle A2 on
the inputs you want there.
Levels#
- Faders are in dB:
0 dBis unity,-60 dBmeans off, up to+12 dBof boost. - Mute silences a strip without losing its fader position.
- VU meters show the peak level per channel.
- Strips can be mono, stereo, quad, 5.1 or 7.1.
The default device star#
Any strip except a cable can be the system default — one default output and one default microphone at a time:
| Strip | Becomes | What apps see |
|---|---|---|
| virtual input | default output | the strip itself |
| hardware output | default output | " |
| virtual output | default microphone | the strip itself |
| hardware input | default microphone | " |
A hardware strip's own node stays hidden (so VeeMeeter never fights your sound settings); the "(VeeMeeter)" device only exists while the strip is the default. Volume keys and pavucontrol stay in sync with a default virtual input's fader, in both directions.
Daemon and window#
flowchart LR
gui["veemeeter<br/>(window)"] -- JSON lines --> sock(("$XDG_RUNTIME_DIR/<br/>veemeeter.sock"))
ctl["veemeeter ctl"] -- JSON lines --> sock
sock --> daemon["veemeeter daemon<br/>(systemd user service)"]
daemon -- libpipewire --> pw[("PipeWire graph")]
The daemon owns every node and link. The window and ctl are just
remote controls, so closing the window never cuts your audio. When the
daemon stops, all of its nodes and links disappear cleanly.
Next steps
Learn the window in the GUI guide, script it with the
CLI, or tweak config.toml by hand.