Use a Rainbow Six Siege soundboard while keeping squad comms clear
Rainbow Six Siege voice depends on Windows recording state, the game Voice Chat Input Mode, a push-to-talk binding or open-mic sensitivity, Ubisoft privacy settings, teammate mutes, and the reputation system. BordQ combines a physical microphone with triggered clips before the signal reaches Rainbow Six Siege, so listeners receive one controlled voice feed instead of speaker audio leaking back into an open microphone.
CABLE Output can move in Windows but stay silent in Siege when the game cached an old default, input mode is disabled, sensitivity never opens, the push-to-talk key collides with an operator control, or account communication permissions restrict voice. 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.
Make CABLE Output the known input, then tune the gate for short clips.
BordQ mixes the physical microphone with clips before the signal reaches the game. Siege then applies its input mode, record level, threshold or push-to-talk behavior, account privacy state, and per-player moderation controls.
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.
Set CABLE Output as the Windows Default Device and Default Communication Device before launching when Siege follows system audio. Then open Options > Audio, verify voice chat input is enabled, select the intended mode, and restart the game after changing Windows endpoints.
- Virtual Cable (Output): VB-Cable Input
- Default recording device / Voice Chat Input: CABLE Output · Options > Audio > Voice Chat
Three places for audio during a Siege session
Choose the smallest audience and safest control method that leaves callouts understandable.
- BordQ into a private squad
Agreed reactions during warmup, custom games, or casual sessions.
The same input gate and sensitivity rules still shape clips.
Use this to validate the complete route before matchmaking.
- BordQ into Discord
Premade friends who want effects outside public team chat.
Solo teammates cannot hear the clips or your Discord-only speech.
Prefer it when public tactical voice should remain untouched.
- BordQ into match team voice
Occasional useful cues accepted by current teammates.
Disruption, harassment, and inappropriate audio affect reports and reputation.
Prioritize callouts; a working soundboard is never permission to spam.
Route BordQ into Rainbow Six Siege 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.
- 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.
- 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.
- Make CABLE Output the recording device Siege opens
Close Siege, set CABLE Output as both the Windows Default Device and Default Communication Device under Recording, then relaunch. In Options > Audio, enable Voice Chat Input and confirm the record level is not zero.
Siege may keep the device opened from startup; changing the Windows default mid-match can leave the old endpoint cached until relaunch.
- Choose push-to-talk or tune open-mic sensitivity
For precise clips, use push-to-talk and bind it away from lean, gadget, ping, movement, and BordQ trigger keys. If using open mic, tune sensitivity with speech plus the quietest clip so silence stays closed but intended audio opens.
An overly strict threshold clips quiet intros; an overly loose one broadcasts keyboard noise and accidental sounds.
- Use a custom game and one squad listener
Verify normal speech, one quiet clip, push-to-talk release, in-game mute, and round transitions. Ask the second player to confirm a single copy and then test whether changing squads or muting behaves as expected.
A custom game protects live tactical comms while exposing device caching, sensitivity, and permission failures.
Windows default, voice mode, and social permission are separate checks
Changing the cable cannot bypass an intentionally closed game or account control.
- Windows recording — CABLE Output default
Gives Siege the BordQ mix at launch.
- Input mode — PTT or tuned open mic
Determines when the game transmits.
- Privacy / reputation — May restrict communication
Must be resolved in Ubisoft account state.
Ubisoft treats toxic voice behavior as misconduct. Do not use clips to drown out calls, harass players, imitate staff, or bypass privacy, mute, or reputation controls.
Fix a Rainbow Six Siege 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 — Set CABLE Output as both Windows recording defaults before launch, enable Voice Chat Input, raise record level, lower an overly strict sensitivity, hold push-to-talk, and review Ubisoft privacy plus teammate mute state.
- 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.
- Voice works in Discord but Siege shows no transmission — Discord has its own explicit input, while Siege may follow the Windows default captured at launch. Set both recording defaults to CABLE Output, close the game fully, and reopen it before retesting.
Questions to settle before using it live
Which microphone should Rainbow Six Siege use?
Use CABLE Output. When Siege follows Windows rather than an explicit picker, make it both the Default Device and Default Communication Device before starting the game.
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 open mic for soundboard clips?
Push-to-talk is safer and more predictable for tactical play. Open mic can work, but its sensitivity must admit quiet clip intros without broadcasting keyboard noise or leaving the channel open.
Is a soundboard allowed here?
Follow Ubisoft's Code of Conduct and keep team communication useful. Use clips only with willing squadmates, avoid public spam and offensive content, and never attempt to evade a mute or reputation restriction.
Official references for Rainbow Six Siege
Menus, channel behavior, and moderation rules can change. These first-party pages are the review anchors for this setup.
Protect the callouts first, then add controlled audio.
Download BordQ, make CABLE Output the input Siege opens, reserve a clean push-to-talk bind, and test speech plus one short clip in a custom game. 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.
Use the same clean audio route in other apps and games
- Set up VB-Cable — Verify the endpoint Siege should open at launch.
- Use a soundboard in CS2 — Compare another tactical push-to-talk route.
- Use a soundboard in VALORANT — Separate party voice from team voice and trigger keys.
- Build a BordQ soundboard — Prepare low-volume clips and a dedicated Siege profile.