After your soundboard is installed
The first hour after a Soundux install should prove routing, not decorate twenty tabs. Open the pad UI, import one local cue, route Windows VB-CABLE or Linux passthrough, play and stop once, then bind a single hotkey before you call the soundboard ready.
Eight first-hour steps
- Launch the app once. Confirm the window opens from the Start menu, portable folder, or Flatpak entry.
- Import one short file. Use a cue you already own so rights stay clear on this soundboard desk.
- Select output routing. Windows: VB-CABLE sink. Linux: application passthrough for your call client.
- Point the call app at the cable. Discord, Teamspeak, or OBS must listen to the same path.
- Play the cue. Hear it on headphones or through the call with a trusted friend.
- Stop or pause. Confirm silence returns without restarting the soundboard process.
- Bind one hotkey. Keep it far from push-to-talk and mute.
- Bookmark the update door. Releases, winget Portable, or Flatpak—write it on the machine card.
Windows-specific checks
Setup installs VB-CABLE per upstream README. Open Windows sound settings and confirm the cable devices exist before blaming Soundux. If you used portable or winget Portable, you may need to install VB-CABLE separately—another reason the setup exe is the preferred soundboard door in this guide.
WebView2 Runtime ships with the installer story; portable doors may assume it is present. If the UI fails to render, install WebView2 from Microsoft and relaunch.
Linux-specific checks
Prove system sounds under PipeWire or PulseAudio first. Then configure passthrough into the application you stream with. Flatpak permissions sometimes need attention for device access—adjust with Flatseal only after a basic play fails for clear permission reasons.
What not to do yet
- Do not download random cue packs from SEO blogs.
- Do not bind a full keyboard of hotkeys before one proof play.
- Do not stack Voicemod cables and VB-CABLE without labels.
- Do not fetch a second soundboard mirror because SmartScreen felt scary.
Related guides
first run, portable exe, update uninstall, is it safe, switch from Voicemod.
First-hour success is one heard cue and one clean stop. Everything else is decoration on top of a working soundboard path.
When the hour ends, jot the OS, the filename or package id, and the sink name in your show notes. Future reimages become a checklist instead of a scavenger hunt across adware sites that only rank for soundboard.
If proof fails twice, stop and re-read download safe plus for this computer. Most early failures are wrong binaries or wrong cables, not mysterious GPL bugs.
Stream teams should record a thirty-second loom of the proof play. New operators can watch that clip instead of inventing a second install door during a live incident when the soundboard must simply work.
Home desks can be looser, but the same order still saves time: route, prove, then decorate. Skip that order and you will tune hotkeys on a silent pad for longer than the install ever took.
Capture the baseline
Take one screenshot of the Windows sound panel or Linux routing UI after success. Store it with the machine card. When someone “helps” by installing a second soundboard mirror later, you will have a visual baseline for the working cable path.
Also store the Releases URL and the exact asset name. Those two lines turn a future panic into a five-minute restore for any soundboard desk that followed this first-hour script.
Optional: note whether winget Portable or Flatpak was involved so upgrades use the matching command. Mixing doors without notes is how desks collect duplicate Start-menu icons and conflicting hotkey layers.
Hand off to the next operator
If someone else runs the booth tomorrow, leave the machine card, the cue folder path, and the hotkey legend together. A soundboard that only lives in one person's head will be reinstalled from a random mirror the first night they are away.
Point them at guides and the soundboard home install panel so they reuse the same doors instead of inventing new ones under pressure.
Keep the first-hour script boring and repeatable so every soundboard reimage ends with the same proof play.
Shared soundboard desks thrive on checklists more than talent.
Keep proof recordings short so new operators learn the soundboard path without sitting through a long lecture.