Square cue-grid panel with nine cue tiles framed in ink on cool paper.
Cue panel diagram: a framed three-by-three cue grid for local playback. Cue Bind original cue-grid geometry (original geometry, not the upstream app icon).

First run is where soundboard installs succeed or quietly fail. Skip decoration until routing works. The goal is one heard cue and one clean stop.

Order of operations

  1. Launch Soundux and confirm the UI renders (WebView2 on Windows matters here).
  2. Import a two-second file you own.
  3. Select VB-CABLE on Windows or application passthrough on Linux.
  4. Align the call app or OBS input with that path.
  5. Play, listen, stop.
  6. Bind one hotkey far from mute and push-to-talk.

Windows routing detail

Setup should have installed VB-CABLE. If you used portable or winget Portable, install the cable yourself before blaming the pad UI. Name devices clearly in the Windows sound panel so overnight helpers do not pick the wrong endpoint.

Linux routing detail

Prove system sounds under PipeWire or PulseAudio. Choose one target application for passthrough during the trial. Switching Discord and Teamspeak mid-test makes failures look like Soundux bugs.

Hotkey discipline

Bind after proof. Map keys on paper for the first week if you switched from Voicemod. Avoid overlapping booth bindings on shared couches.

Next

/installed, /switch-from-voicemod, /soundboard-portable, /update-uninstall-soundboard.

Operator notes

Write the install door on the machine card beside the OS version. Prefer GitHub Releases filenames or Flathub id io.github.Soundux when teammates ask where the binary came from. Skip ranking portals that cannot show those names.

Prove one routed cue after every change. Hotkeys and skins can wait until playback is boring and reliable on the desk you actually stream from.

If a helper proposes a faster mirror, ask for the exact asset name. Decline anything that is not on Soundux/Soundux Releases or a verified package id. That habit keeps unwanted adware off booth PCs.

Booth checklist

Confirm the binary name, the sink or passthrough target, and one proof play before showtime. Keep Voicemod only if marketplace voices remain required; otherwise let the GPL path own simple pads.

Desk reminder

  • Keep the soundboard install door written beside the OS version.
  • Prefer Soundux/Soundux Releases or Flathub io.github.Soundux.
  • Prove one routed cue after every change before you trust hotkeys on stream night.

Reimage notes

  • Store the Releases URL beside the cue folder path.
  • Survive Windows feature updates without a frantic search for the soundboard binary.

Notes for soundboard first run

  • Document the install door beside the OS version.
  • Prefer Soundux/Soundux Releases filenames or Flathub id io.github.Soundux.
  • Prove one routed cue after every change so the soundboard path stays trustworthy on shared desks.

Show-night checklist

  • Confirm the soundboard binary name still matches Releases or Flathub before doors open.
  • Confirm the cable or passthrough target.
  • Play one two-second cue into headphones, then into the call app, then stop it.
  • Hand the booth to talent only after that proof.

If anything fails, do not download a random mirror. Return to /soundboard-download-safe and /soundboard-for-this-computer.

Voicemod coexistence

Keep Voicemod available only when marketplace voices remain part of the show. For simple pads, let the GPL soundboard own the grid and retire duplicate hotkeys after the side-by-side week documented on /switch-from-voicemod.

Update rehearsal

  • Rehearse updates with the same door used at install time.
  • Do not invent a new download under pressure for the next soundboard bump.

Frequently asked questions

Is this soundboard guide free to follow?

Yes. Cue Bind publishes soundboard install steps without a paywall so anyone can follow the path. Soundux itself ships under GPL-3.0. Audio files you import remain your responsibility and stay separate from the program licence.

Where should I download this soundboard app?

Prefer soundux-*-windows-setup.exe from GitHub Releases for Soundux/Soundux on Windows, or use winget id Soundux.Soundux.Portable for the portable exe, or Flatpak io.github.Soundux on Linux when you already trust those managers.

Does this soundboard work offline after install?

Yes for local pads and playback after the program is installed on the machine. You still need network access for the first setup, portable, Flatpak, or package download from the trusted door.