VoiceMeeter / Documentation / Discord and calls
Discord, Zoom and Teams
A call application needs two things from VoiceMeeter: a microphone to read and somewhere to send its own audio. Get the direction right and everything else is faders.
The two device assignments
| In the call app | Device | Direction |
|---|---|---|
| Microphone / Input | VoiceMeeter Output | The app listens to bus B1. |
| Speaker / Output | VoiceMeeter Input | The app's audio comes back into the mixer on the VAIO strip. |
With those two set, call audio is a strip you can hear on A1, and your voice is whatever you routed to B1. Nothing else changes at the Windows level.
If the call app is set to your physical microphone directly, it bypasses the mixer entirely — no gate, no EQ, no music. That is the single most common "VoiceMeeter does nothing" report.
Discord
- Set the input
Discord → User Settings → Voice & Video → Input Device →
VoiceMeeter Output. - Set the output
Same panel → Output Device →
VoiceMeeter Input. If you keep call audio separate, useVoiceMeeter AUX Inputinstead and it gets its own strip. - Turn off noise suppression Voice & Video → Advanced: disable Echo Cancellation, Noise Suppression and Automatic Gain Control. VoiceMeeter's gate already handles the room; a second suppressor eats consonants and makes you sound robotic.
- Disable "Let's Check" auto-tuning Discord's input sensitivity wizard will set thresholds against an already-processed signal. Set input sensitivity manually or use voice activity with a low threshold.
- Route the mic to B1 In VoiceMeeter, microphone strip → B1. Add A1 only if you want to hear yourself.
Playing music into a call without your voice carrying it
- Put the music player on
VoiceMeeter InputorVoiceMeeter AUX Inputso it becomes its own strip. - Route the music strip to B1 so the other people hear it.
- Keep the microphone on B1 as well — that is the point, both should be heard.
- The separate control you want is usually the opposite case: music you hear but the call does not. Route music to A1 only, and leave the music strip off B1.
Echo: the person on the other end hears themselves
Their voice is coming out of your speakers, your microphone picks it up, and it goes back. Two fixes, in order of preference:
- Headphones. Ends the problem completely.
- Take the call bus off your monitor. If speakers are unavoidable, route the call's audio to A1 for you and make sure your microphone is not on a bus that also carries the call output going back to them. In practice this means the microphone goes to B1, and B1 must not be fed back into the call's own output path.
Zoom
- Settings → Audio → Speaker →
VoiceMeeter Input; Microphone →VoiceMeeter Output. - Uncheck Automatically adjust microphone volume and set Background noise suppression to Low or Off.
- Turn off Original sound unless you are sending music; it disables Zoom's processing and is usually the better choice when VoiceMeeter already shapes the signal.
- Zoom keeps its own device list cached. If a device change does not appear, restart Zoom.
Microsoft Teams
- Settings → Devices → Speaker →
VoiceMeeter Input; Microphone →VoiceMeeter Output. - Teams applies its own noise suppression by default. Set it to Low or Off to stop it fighting the VoiceMeeter gate.
- Teams sometimes overrides the selected device on join. Verify inside the call's device menu, not only in settings.
Common mistakes
| What you see | What is wrong |
|---|---|
| Nobody hears you | Call app input is the physical microphone, not VoiceMeeter Output |
| You hear yourself with a delay | Microphone routed to A1 and monitoring through speakers |
| Call audio is missing from your headphones | Call app output is the hardware device, not VoiceMeeter Input |
| Voice sounds thin or chipped | Two noise suppressors in series — disable the one in the call app |
| Music not audible to others | Music strip is not routed to B1 |
| Voice audible to the stream but not the call | Microphone routed to B1 but call app reading B2 |