Geometric three-by-three pad grid with umber and ink tiles on cool grey paper.
Cue grid: flat ink cue pads with one sand tile for a local soundboard install. Cue Bind original cue-grid geometry (original geometry, not the upstream app icon).

Prefer the Windows setup exe when you want a normal soundboard install on a 64-bit PC. Open Soundux releases and match soundux-*-windows-setup.exe on the current release tag that still lists Windows assets.

Steps

  1. Open the current Windows-bearing tag on GitHub Releases for Soundux/Soundux.
  2. Download soundux-*-windows-setup.exe rather than a Softonic rename.
  3. Run the setup so VB-CABLE and WebView2 Runtime can install with the app per upstream README.
  4. Launch Soundux from the Start menu and confirm the pad UI appears.
  5. Import one local cue you already own, route output to VB-CABLE, and play once.
  6. Keep GitHub Releases or winget Portable as the single update door you write down.

winget portable alternate

winget install -e --id Soundux.Soundux.Portable is YAML-verified in microsoft/winget-pkgs under the Portable manifest family. It installs the portable exe only. Do not invent a Soundux.Soundux full-installer id. Label portable honestly on the machine card so the next operator knows what they inherited for this soundboard desk.

Portable exe on the same tag

soundux-*-windows-portable.exe ships beside the setup file. Use it for folder-style runs when policy blocks installers. You may need WebView2 and VB-CABLE already present. That gap is why this soundboard guide still prefers setup for most desks.

SmartScreen and mirrors

SmartScreen may warn on niche open-source exes. Confirm the URL host is github.com and the filename matches before overriding. Never solve a warning by downloading a second soundboard binary from a ranking portal. Unwanted adware arrives through that shortcut more often than through GitHub itself.

VB-CABLE proof

Open Windows sound settings after setup and confirm cable devices exist. Point Discord, Teamspeak, or OBS at the cable Soundux is playing into. Prove with headphones first, then with a trusted friend on a call. Stop the cue and confirm silence. Only then bind a hotkey far from push-to-talk.

Next pages

First hour: /installed. Portable deep dive: /soundboard-portable. Linux twin: /install-soundboard-linux. Updates: /update-uninstall-soundboard. Compare: /vs-voicemod.

Why desks document the door

Shared booths fail when the install story lives only in chat scrollback. Write the filename or package id on a machine card beside the OS version. Prefer GitHub Releases for Soundux/Soundux or Flathub id io.github.Soundux when someone asks where the binary came from for this soundboard.

If a helper proposes a faster mirror, ask for the exact asset name. Decline anything that cannot show soundux-*-windows-setup.exe, the portable exe, or a verified package id. That single question prevents most unwanted adware incidents on booth PCs that only needed a local soundboard.

Proof before decoration

Import one short cue you already own. Route Windows VB-CABLE or Linux application passthrough. Play once into a monitor or trusted call. Stop and confirm silence. Only then bind a hotkey far from push-to-talk. Skins and multi-tab libraries can wait until the soundboard path is boring and reliable on the machine you actually stream from.

Rehearse the stop key as carefully as the play key. A cue that cannot silence cleanly will embarrass a booth faster than a missing laugh track. Keep headphones on during the first proof so you hear overlap before chat does.

Update rhythm

Return to the same door for bumps: Releases setup, winget Portable, or Flatpak. Mixing doors without notes creates duplicate Start-menu icons and confused uninstalls after a reimage. Keep the Releases URL bookmarked so the next soundboard update does not begin with a fresh web search for the head keyword alone.

When a newer tag omits an OS asset you rely on, stay on the last tag that still lists it until you confirm replacements. Rewrite chatter upstream is interesting, but production desks need filenames more than roadmaps.

Teaching the next operator

Walk a new teammate through one Releases download while they watch the filename. Have them read the setup or Flatpak id aloud. Finish with one proof cue through the sink. That thirty-second habit prevents a season of Softonic clutter on shared stream PCs.

Print a hotkey legend beside the keyboard for the first week after any migration. Muscle memory from Voicemod will fight a new soundboard layout until the paper map becomes unnecessary.

Home install panel: /. Safe download checklist: /soundboard-download-safe. First hour: /installed. Releases filenames: /soundboard-releases. GitHub map: /soundboard-github. Machine chooser: /soundboard-for-this-computer. Compare: /vs-voicemod. Switch: /switch-from-voicemod.

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.