SoundLord
SoundLord / Guides / Play sounds through your mic

How to play sounds through your mic

You hit the key, you hear the sound, and everyone in the call hears nothing. This is the single most common soundboard problem, it is not a bug, and once you see why it happens the fix takes about five minutes and costs nothing.

Why nobody hears you

A microphone is an input device. It captures what reaches its capsule — your voice, your keyboard, your room. Your soundboard, meanwhile, plays into an output device: your headphones or speakers.

Those two never meet. Discord sends your microphone to the call, and your microphone has no idea your computer is playing an airhorn. Nothing is broken — the audio simply has no path from your output back into your input.

The exception that proves it: if you use open speakers loud enough, your mic will pick the sound up — as a thin, echoey, half-cancelled mess, because noise suppression is actively fighting it. That is the sound of doing it wrong.

What you actually need: a virtual audio cable

A virtual audio cable is a tiny free driver that creates a fake output and a matching fake input on your PC. Anything played into the fake output shows up on the fake input — so voice apps can “listen” to it as if it were a microphone.

The chain looks like this:

That last line is the whole difficulty. Naively pointing Discord at the cable means your friends hear your sounds and not your voice. You need both signals in the same stream, and there are two clean ways to do it.

Option A: let the soundboard forward your mic (easiest)

The simplest setup by far: the soundboard takes your real microphone, mixes it together with the sounds, and sends the combined signal into the cable. Discord then just listens to the cable and gets everything.

SoundLord does this with a single toggle — you pick your real mic once, enable mic forwarding, and set Discord's input to CABLE Output. No routing software, no mixer, no per-app juggling. There is also a bindable key to flip the forwarding on and off mid-call.

Option B: route it yourself

If you already run a full audio stack, you can keep your existing setup and just add the cable as another source. This gives you the most control and the most things to configure: you handle mixing and monitoring, the soundboard only plays into the cable.

Either way the step-by-step — install, device names, Windows settings, monitoring so you still hear yourself — is written out here: VB-CABLE setup, step by step.

Three settings that silently ruin it

  1. Noise suppression. Discord's Krisp removes anything that is not a human voice. Your music and effects are, by definition, not a human voice. Voice & Video → Noise Suppression → Off. This one setting explains most “I did everything right and it still doesn't work” cases.
  2. Automatic gain control. AGC constantly rebalances loudness, which makes a clip that was mixed to sit under your voice jump around at random. Turn it off and set levels once.
  3. Echo cancellation. Designed to remove audio that is playing on your machine — exactly what you are trying to send. If your sounds arrive gutted or half-there, this is why.

Does this work outside Discord?

Yes. The cable is a Windows-level device, so anything that lets you choose a microphone can use it: in-game voice chat, TeamSpeak, OBS, Zoom, Teams, Meet, browser calls, recording software. You set it up once and pick CABLE Output as the input wherever you need it. For meeting apps specifically, see Soundboard for Zoom, Teams & Meet.

Is it against Discord's rules?

No. Routing audio into your own microphone input is a normal, supported thing to do — streamers, podcasters and musicians all do it. What gets people in trouble is behaviour: blasting sounds to disrupt servers is harassment whether it comes from a soundboard, a bot or your actual voice. Read the room, keep the volume under your voice, and nobody will mind.

Quick checklist

Get SoundLord →