CueCart
Instant audio cartwall for radio, stage & screen
6 followers
Instant audio cartwall for radio, stage & screen
6 followers
CueCart is a broadcast-grade audio cartwall: a grid of pads that fire preloaded audio with sub-6 ms latency. Built-in DJ deck, cue editor, broadcast processing, QWERTY & MIDI triggering (note + CC, per-pad learn). Windows. One-time licence.
Pads feel instant, which is exactly what I needed for live work. The QWERTY triggering setup was painless and the cue editor handled my usual mess of pre-rolls without any fuss.
@abdurrahmaaz1o Thanks Abdurrahman — that's exactly the reaction I was chasing. The instant-fire behaviour is the whole reason the engine is built the way it is: every cue in the set is decoded and held ready before you ever touch a pad, so there's no disk hit at trigger time and no spin-up.
Curious what you're running it for — radio, live events, theatre? And if the pre-roll handling has any rough edges, I'd like to hear it. The cue editor is where I most want feedback right now.
One thing that would make this a no-brainer upgrade for me is native MIDI controller mapping, with per-pad learn and saveable layouts. Right now the QWERTY triggering is fine for tight budgets, but a real broadcast or club workflow usually runs off a fader or grid controller, and without MIDI you end up fighting the software instead of playing it.
@miratngl8j5s This is already in — and CC as well as notes, so a fader works, not just pads. Right-click a pad → Cue Settings → Triggers → MIDI → Learn, move the fader or hit the key, bound. You can pin it to a channel or leave it omni, and bindings save with the set, so each show carries its own mapping.
Fair confusion though — my Product Hunt description only mentions QWERTY triggering and never says MIDI is in there. That's on me, fixing it now.
"Fighting the software instead of playing it" is still the right bar, and there's more to do: grid-positional mapping so a controller follows the active bank, and LED feedback back to the hardware. What are you running — faders, a grid, or both?
Would love to see native MIDI controller mapping so the pads respond to hardware controllers like the Akai MPK or Novation Launchpad out of the box. Right now it seems like you have to rely on third-party tools to get tactile button feedback during live shows, which adds friction for broadcast workflows where reliability is everything. A simple learn-mode where you click a pad and hit a MIDI note to bind it would go a long way.
@aryajvjs The learn-mode you're describing is exactly what's in there — click a pad, hit a note, bound. Cue Settings → Triggers → MIDI → Learn. Notes and CC both, any channel or omni, no third-party bridge; CueCart talks to the controller directly.
Fair confusion — my Product Hunt description only mentions QWERTY triggering and doesn't say MIDI is supported. My fault, fixing it now.
Where you're genuinely ahead of me: a binding currently fires that specific cue in any bank, so an MPK works well but a Launchpad doesn't re-point its grid when you switch banks. Grid-positional mapping plus LED feedback so the pads light with cue state is what I'm looking at next. Which of the two are you on?