In development

A MIDI soundboard built by someone who has actually been on air.

Low-latency playback, record-to-pad sampling, LED feedback and one bridge for every controller on your desk. Made for live radio and streaming, where dead air is the only real mistake.

Node.js + Electron Native audio engine Voicemeeter Potato control Multi-controller MIDI
DEMO SURFACE // PROFILE 1
SHIFT REC ARM PANIC
READY. HIT A PAD.

Tap the pads, or use your keyboard (1-4, Q-R, A-F, Z-V). Hold SHIFT for the second layer. These are browser bleeps standing in for the real engine.

What it is

One surface for your clips, your controllers and your mix.

Soundboard Solutions is a desktop soundboard for people who run a live show by hand. Every pad on every controller you own can fire a clip, start a recording, flip a Voicemeeter route, send MIDI, run a keyboard macro or launch a program.

It is built in Node.js and Electron, with a native audio engine doing the real-time work so the interface never gets between your finger and the sound. Windows first, because that is where the studio lives.

Controller AController BController C
↓ ↓ ↓ MIDI in, source identity kept
MIDI bridge→Profile + Shift layer
↓ action
Audio engineVoicemeeterMIDI out
↑ LED feedback back to the right device
Two identical controllers stay two separate controllers. A mute you press on one lights up on all of them.

Features

What a live board actually needs.

No pretty pads wired to nothing. Every feature below came from a real problem during a real broadcast.

Layering

Up to eight voices at once, so the bed keeps rolling under the drop under the sound effect. Daisy-chain clips to play one into the next.

8 voices // clip chains

Stutter, tap, hold

Pick how each pad behaves: one-shot tap, play-while-held, or stutter retrigger for the "w-w-w-what" moments. Preview a clip before it goes anywhere near air.

per-pad trigger modes // preview

Record to pad

Cassette-style capture from your Voicemeeter sources. Grab the caller's best line, preview it, drop it on a pad. Or arm a pad and record straight onto it. Cleared a slot by accident? Undo.

buffer-then-assign // direct-to-pad // undo

LED customization

Colors and flash patterns per button, up to four-color sequences, so the siren cue looks like a siren and the anthem cue looks like an anthem. Lights follow real state: playing, queued, armed, muted.

LED editor // state feedback

MIDI bridge

Merge several controllers into one virtual MIDI port while keeping track of which box each press came from. Feedback goes back to the right device, without loops or double-fires.

multi-controller // one virtual port

Voicemeeter Potato control

Mute strips and switch A1 through A5 routes from your controller's bottom row, with the LEDs showing what Voicemeeter is really doing.

strip mute // A1-A5 routing

Four profiles, two layers

Four global pages, each with its own normal and shift layer. Shift plus a profile button flips the whole desk at once.

4 profiles x normal/shift

Panic button

One press kills every playing voice and clears the queue. Separate from mute, because "stop everything" and "shut up for a second" are two different emergencies.

panic // output mute

Queue, gain, limiter

A first-in, first-out clip queue with scheduled delays. Peak-normalize clips to your target level, override gain per pad, and keep a limiter on the master.

FIFO queue // normalization // limiter

Plays well with

Built to sit beside the tools already on your screen.

It doesn't try to replace your DJ software or your DAW. It runs next to them and keeps your hands on one surface.

Voicemeeter PotatoStrip mutes and A1-A5 routing from the pads
Virtual DJRuns alongside for music and mixing
ReasonRuns alongside for production and beds

Independent project. Not affiliated with or endorsed by VB-Audio, Atomix Productions or Reason Studios. Product names belong to their owners.

Being built against a real desk

The mapping system is designed around the actual controllers in the studio, each with its own pad layout and LED quirks:

  • Numark Party Mix II
  • Numark Mixtrack
  • Akai APC Key 25 Mk2
  • Akai APC Mini Mk2
  • Akai LPD8
  • M-Audio Trigger Finger
  • Alesis QX49
  • M-Wave Chocolate Plus (x2, Bluetooth)

This is the test bench, not a compatibility promise. Hardware support gets confirmed device by device, and LED effects a controller can't physically show won't be faked.

Built for live radio

Born in cable spaghetti.

This started in the Lotion Room, a back-room studio in Aurora, Colorado, home of the Sandwich Lotion Show. The desk holds more MIDI controllers than any one person needs, all plugged into one machine, and none of them agreed on anything.

The guy writing it spent years on DFW radio and in strip club DJ booths, plus 18 years in military telecom, and holds an amateur extra class ham license. He has run live audio where a missed cue is heard by everybody. Off-the-shelf soundboards kept doing things that work in a demo and fall apart on air, so he started writing his own.

The rule: if it can't be done one-handed while a caller is talking, it isn't done yet.

"I asked for one soundboard. He built a bridge so nine of them could argue at once. It works. Don't touch anything."

Eddie, the show's reluctant sound engineer

Status

In development. No release date yet.

It's being built and tested in the studio now. There's no download, no price and no date, and we'd rather tell you that than make one up. Here's the build order:

  1. 01
    Audio engine + one controllerProve the latency before building anything on top of it.
  2. 02
    Mapping, profiles and shiftMIDI learn, four pages, two layers, every device kept separate.
  3. 03
    Playback and recordingVoices, chains, queue, record-to-pad, undo.
  4. 04
    MIDI bridge + VoicemeeterOne virtual port, synced mutes, A1-A5 routes.
  5. 05
    LED adaptersPer-device feedback, tested on the actual hardware.
LATENCY TARGET
< 10 ms

Pad press to sound, under real playback and recording load. That's a target, not a promise. When it's measured, the numbers get published with the driver, sample rate, buffer size and method, so you can check the work.

Engineers don't trust a latency number without a buffer size next to it. Neither do we.

Follow development

Watch it get built. Live, probably.

Progress, test clips and the occasional on-air meltdown go up on TikTok first. Follow along there to hear when it's ready.