Use a TeamSpeak soundboard with a controlled microphone route and talk mode

TeamSpeak separates the input device from its voice mode: Push-To-Talk transmits while a chosen key is held, while Voice Activity Detection opens transmission when the client detects speech. The modern client tunes that detection automatically; TeamSpeak 3 also offers a manual activation threshold. BordQ combines a physical microphone with triggered clips before the signal reaches TeamSpeak, so listeners receive one controlled voice feed instead of speaker audio leaking back into an open microphone.

A valid clip can appear on the Windows meter yet stay silent when the wrong capture profile is active, push-to-talk is not held, Voice Activity Detection misses a quiet intro, or the server channel restricts speaking. This guide covers the exact input route, the channel or mode that controls delivery, a low-risk test, and the failure that is most often mistaken for a broken virtual cable.

Download BordQ free

Prove the cable locally, then prove permission and timing on the server.

TeamSpeak must receive CABLE Output through the capture device selected by the active profile. After that, Push-To-Talk, Voice Activity Detection, mute state, channel moderation, and server permissions decide whether another client receives the clip.

Keep incoming call or game audio out of VB-Cable. Only the BordQ microphone-and-clip mix should enter CABLE Input; routing both directions through the same cable creates echo, delayed duplicates, or a feedback loop.

In the newer TeamSpeak client, open Options > Audio; in TeamSpeak 3, use Tools > Options > Capture. Select CABLE Output as the capture or input device in the profile used by the current connection, then run the available microphone test before joining a busy channel.

• Virtual Cable (Output): VB-Cable Input
• Capture Device: CABLE Output · Options > Audio or Tools > Options > Capture

Three ways to control a TeamSpeak soundboard transmission

Choose the mode that gives a clip a predictable start and leaves normal conversation understandable.

• BordQ plus Push-To-Talk

  Exact timing for short clips in a private or coordinated channel.

  The talk key must remain held for the complete clip, including its quiet opening and tail.

  Use a dedicated key and press it just before triggering BordQ.

• BordQ plus Voice Activity Detection

  Hands-free speech with occasional louder, normalized clips.

  Automatic detection can miss a quiet clip opening; a poorly set TeamSpeak 3 threshold can also stay open on noise.

  Use Auto Settings in the modern client, or tune the manual threshold in TeamSpeak 3, then test both speech and the quietest approved clip.

• Continuous transmission

  A tightly controlled recording or rehearsal channel.

  Room noise and accidental audio remain live, increasing disruption and privacy risk.

  Avoid it in public or everyday channels.

Route BordQ into TeamSpeak in five steps

Configure the path from source to destination, then prove the complete route with one short clip before a real call, match, or public room.

1. Install BordQ and expose both VB-Cable endpoints

   Install BordQ on Windows and let its audio-driver setup finish. Restart Windows if CABLE Input and CABLE Output do not appear in the device lists.

   CABLE Input is the playback endpoint BordQ sends to; CABLE Output is the recording endpoint the destination hears.

2. Build one clean mic-and-clip mix

   In BordQ Audio Setup, select the physical microphone as Microphone Input and VB-Cable Input as Virtual Cable (Output). Trigger a short, normalized clip and confirm the BordQ and Windows recording meters move.

   Leave headphones as the playback device. Do not route the destination output back into the cable.

3. Select CABLE Output in the active TeamSpeak audio settings

   Open Options > Audio in the modern TeamSpeak client, or Tools > Options > Capture in TeamSpeak 3. Choose CABLE Output as the microphone or capture device. In TeamSpeak 3, also confirm that the capture profile assigned to the current connection is the one you edited.

   TeamSpeak 3 bookmarks can select a different capture profile even when Windows shows the cable working; the modern client exposes the microphone in its Audio settings.

4. Choose Push-To-Talk or configure Voice Activity Detection for your client

   For exact clip timing, select Push-To-Talk and hold the assigned key from just before playback until the clip ends. For Voice Activity Detection in the modern client, speak in the microphone test and use Auto Settings. In TeamSpeak 3, use the local test to place the manual activation threshold below normal speech and quiet clip openings but above room noise.

   A transmission mode can block a healthy input; device meters alone do not prove that TeamSpeak has opened the voice stream.

5. Test the profile locally and in a private server channel

   Run the TeamSpeak microphone test, speak, and trigger one normalized clip. Then join a private channel with a second listener, verify the talk indicator opens for the full clip, and confirm the channel grants you permission to speak.

   If the local test passes but the remote test fails, keep the proven cable route and inspect mute, channel moderation, talk power, and connection-specific profiles.

Capture profile, transmission mode, and channel permission are independent checkpoints

A clean cable signal reaches listeners only when all three checkpoints agree.

• Active capture profile — CABLE Output

  Confirms the current connection uses the virtual microphone.

• Voice mode — PTT or verified VAD

  Must open for the entire clip.

• Server channel — Permission to speak

  Moderation or talk power can block a correct input.

Use short clips only where participants and server rules permit them; TeamSpeak channel permissions are not an invitation to interrupt other speakers.

Fix a TeamSpeak soundboard that is silent, doubled, or in the wrong place

Follow the signal from left to right and change one setting at a time. A local monitor is useful, but only a remote listener proves the final channel.

• CABLE Output shows no recording activity — Return to BordQ and confirm Virtual Cable (Output) is VB-Cable Input. Check Windows microphone privacy permissions, driver installation, device mute, and the BordQ output meter.
• The meter moves, but listeners hear nothing — Select CABLE Output in the active capture profile, clear capture mute, run the local test, and confirm Push-To-Talk is held or Voice Activity Detection opens. If local audio works, check the current channel for moderation, talk-power requirements, or silence status.
• Listeners hear themselves or a delayed duplicate — Incoming audio is entering the cable, or speakers are feeding an open physical microphone. Use headphones, remove loopback or monitoring routes, and monitor the BordQ mix in only one place.
• The local microphone test works, but the server channel is silent — The cable and capture device are already proven. Check whether the connection loaded another capture profile, whether you joined a moderated channel, and whether your client has enough talk power or has been silenced.

Questions to settle before using it live

Which microphone should TeamSpeak use?

Choose CABLE Output as the TeamSpeak capture or input device. BordQ sends your physical microphone and clips into CABLE Input; TeamSpeak records the cable's CABLE Output endpoint.

Can I keep speaking while a clip plays?

Yes. BordQ mixes the selected physical microphone and clips into CABLE Output. Balance clip gain below normal speech and use ducking or short clips when intelligibility matters.

Why can I hear a clip that nobody else hears?

Local monitoring proves only the playback side. Check CABLE Output activity, the destination input, active channel, mute or push-to-talk state, permissions, and a remote listener.

Should I use Push-To-Talk or Voice Activity Detection?

Push-To-Talk gives clips the most predictable start and stop. Voice Activity Detection is convenient for speech, but test that the modern client's automatic detection opens for quiet clip intros. In TeamSpeak 3, adjust the manual activation threshold if those intros are clipped or room noise keeps transmission open.

Is a soundboard allowed here?

Follow the server and channel rules, ask before using effects, keep clips short, and never imitate administrators, drown out conversation, or evade a silence or moderation action. Keep a physical-microphone profile ready for normal communication.

Official references for TeamSpeak

Menus, channel behavior, and moderation rules can change. These first-party pages are the review anchors for this setup.

• TeamSpeak Support: Push-To-Talk and Voice Activity Detection
• TeamSpeak Support: Configure voice activation

Make the active TeamSpeak microphone setting your verified checkpoint.

Download BordQ, select CABLE Output in TeamSpeak, choose a predictable talk mode, and verify one quiet clip in a private channel before using the profile live. BordQ's full soundboard, Live Audio, Mobile Remote, and native Stream Deck integration remain free; Pro adds expanded limits, Voice Personas, and Voice Changer without a subscription.

Download BordQ free — See Pro

Use the same clean audio route in other apps and games

• Set up VB-Cable — Understand the playback and recording endpoints behind the route.
• Use a soundboard in Steam — Compare TeamSpeak profiles with Steam and per-game input overrides.
• Use a soundboard in Discord — Apply the same cable route to Discord input and processing controls.
• Build a BordQ soundboard — Prepare normalized clips, hotkeys, gains, and fallback microphone profiles.