Prefer Flatpak when you want a current Linux soundboard install with a clear id. Run flatpak install flathub io.github.Soundux, or take .deb, .rpm, .flatpak, or .tar.gz assets from the same GitHub tag that ships the Windows setup.
Flatpak path
Enable Flathub if needed, install io.github.Soundux, launch from the menu, prove system audio, configure application passthrough, import one cue, and play into the call client. Updates stay boring with flatpak update.
Releases artifacts
Tag the current release lists deb, flatpak, rpm, and tar.gz names beginning with soundux-. Match them only from Soundux releases. Snap and AUR may lag; prefer Flathub or tag artifacts when version pins matter for a lab image.
Runtime expectations
PulseAudio or PipeWire, Xorg, Webkit2gtk, and related libraries appear in upstream README runtime notes. Fix session audio before declaring the soundboard broken. Passthrough replaces the Windows VB-CABLE story—pick one target application and stick with it during tests.
Next steps
/installed, /soundboard-first-run, /soundboard-download-safe, /install-soundboard-windows.
Fleet notes
Deb and rpm suit locked-down fleets that forbid Flatpak. Record the package name beside the OS version. Shared university booths should appoint one owner for the cue folder so the soundboard library does not become a Desktop junk drawer.
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 install soundboard linux
- 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.