Soundboard

Switch from Voicemod to a local soundboard

You can move cue work from Voicemod into a GPL soundboard without burning the bridge on day one. Install Soundux from GitHub Releases, import files you already own, prove VB-CABLE or passthrough routing, and only then stop relying on freemium voice seats for simple pads.

Close detail of cue-grid geometry used as the soundboard mark.
Cue detail for the cue-grid used across this install guide. Cue Bind original cue-grid geometry (original geometry, not the upstream app icon).

What transfers and what does not

Your own WAV and MP3 files transfer. Marketplace voices, account seats, and Voicemod-specific boards do not magically become Soundux tabs. Plan a folder of cues with clear rights before you call the migration done.

Comparison context: vs Voicemod. Install doors: for this computer.

Side-by-side week

Keep Voicemod installed while you prove the local soundboard path. Use Voicemod only for effects you still need, and use Soundux for pads you already own. That split prevents a cold-turkey failure mid-stream.

  1. Install Soundux once. Prefer soundux-*-windows-setup.exe or Flatpak on Linux.
  2. Copy a small cue folder. Start with five short files, not a chaotic dump.
  3. Route output. VB-CABLE on Windows or application passthrough on Linux.
  4. Bind one hotkey. Match a muscle-memory key from Voicemod if you can.
  5. Run one real call. Prove friends hear the cue before you remove Voicemod.

Audio device habits

Voicemod often inserts its own virtual devices. Soundux on Windows expects VB-CABLE per upstream README. Do not stack three virtual cables without labels. Name devices clearly in the Windows sound panel so the call app picks the cable you intend for soundboard playback.

On Linux, pick one target application for passthrough and stick with it during the trial week. Switching Discord and Teamspeak mid-test makes failures look like Soundux bugs when they are session routing mistakes.

Library cleanup

Delete cues you cannot rediscover rights for. A local soundboard does not excuse a messy folder of scraped clips. Prefer short, loud-normalized files so pads feel responsive without slamming stream compression.

First-run tips: first run. Safety: is it safe.

When to keep Voicemod

Keep it if marketplace voices or realtime voice changers are still core to the show. The GPL soundboard path is for pads and local files. Honest tooling beats forcing one app to pretend it is the other.

Migration success is one routed cue from Soundux during a real call—not an empty Start-menu icon beside a still-open Voicemod seat.

Rollback plan

If routing fails, leave Voicemod as the fallback and revisit download safe to confirm you did not install a mirror binary. Re-check Releases filenames, then retry VB-CABLE selection. Update notes: update uninstall.

Document the final door on the machine card once the week succeeds. Future reimages should restore the soundboard path without rediscovering adware download portals that only rank for the head term.

Teams that share a booth should appoint one person to own the cue folder permissions. Migration fails socially when everyone dumps conflicting packs into Desktop shortcuts named “new soundboard final FINAL.”

Hotkey mapping tips

Pick keys far from push-to-talk. Many Voicemod users bind pads beside mute keys and then wonder why cues clip. On Soundux, bind after routing works, and test with headphones so you hear overlap before chat does.

Keep a paper map for the first week. Muscle memory from Voicemod will fight the new soundboard layout. A one-page legend beside the keyboard reduces dead air while you relearn the grid.

File format and loudness

Prefer short WAV or MP3 cues normalized to a consistent loudness. Wild peaks that worked inside Voicemod’s processing chain can slam a raw soundboard pad into stream limiters. Normalize once in a plain editor before import.

Avoid giant ambient beds as first test files. Two-second stingers prove routing faster and fail clearer when the cable is wrong. Expand the library after the soundboard path is boring and reliable.

Team communication

Tell moderators which tool is live tonight. Mixed signals—“play the Voicemod one” versus “hit the Soundux pad”—create double plays. A single written source of truth for the booth soundboard prevents comedy bits from colliding.

After the side-by-side week, uninstall with intent. Unwanted Voicemod devices can still appear in menus and confuse new operators even when the GPL soundboard is the real path. Cleanup guide energy lives in update uninstall.

Legal reminder: migrating tools does not migrate licences for clips you do not own. Keep the ethics boring and the soundboard library clean.