Most early failures are environmental. Work the list in order before you reinstall from a random mirror.
Silent playback
- Confirm the file plays in a normal media player.
- Confirm Soundux output device or passthrough target.
- Confirm Discord/OBS listens to the same cable.
- Confirm system volume and call app input sensitivity.
UI will not open on Windows
Install or repair WebView2 Runtime. Portable doors assume it more often than setup. Re-launch after repair.
Flatpak cannot see devices
Adjust permissions only after proof fails for clear reasons. Record changes. Random permission widening creates inconsistent booths.
Double hotkeys
You probably have setup and portable both installed, or Voicemod still bound. Remove the loser. See /update-uninstall-soundboard.
Wrong binary suspicion
Re-read the filename. If it is not from Soundux/Soundux or verified package ids, uninstall and start at /soundboard-download-safe.
Still stuck
Gather OS version, door used, asset name, and a short note about devices. Upstream Discord/Matrix can help after those facts exist. Do not skip to cracked archives.
Prevention
First-hour script on /installed and routing on /soundboard-first-run prevent most tickets for shared soundboard desks.
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 troubleshooting
- 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.