Migration is a week, not a minute. Keep Voicemod available until the GPL soundboard path proves itself on a real call.
What to copy
Copy WAV/MP3 files you have rights to. Marketplace voices stay behind. Normalize loudness before import so raw pads do not slam stream limiters.
Side-by-side script
Install Soundux from the proper door, import five short cues, route cables, bind one key, and run a real conversation. Only then remove Voicemod pads you replaced. Full narrative: /switch-from-voicemod.
Failure handling
If routing fails, check filenames via /soundboard-download-safe, then OS devices, then upstream docs. Do not add a third mirror binary mid-incident.
Team habits
Tell moderators which tool is live. Print a hotkey legend. Appoint a cue-folder owner. Social clarity prevents double plays more than any advanced setting.
After success
Uninstall with intent using /update-uninstall-soundboard. Update the machine card. Celebrate boredom: a predictable soundboard is the goal.
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 switch voicemod to soundboard
- 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.
Final migration gate
- One real call heard the Soundux cue.
- Hotkey legend printed.
- Voicemod retained only for marketplace voices still required.
- Machine card updated with the surviving soundboard door.
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.