Helm DJ
The decks drive the show.
Helm DJ sits quietly next to your normal DJ setup and listens. Everything it hears — the track, the beat, the energy in the room — becomes something the rest of your rig can follow. Lighting picks up the cue. Video lands on the beat. Nobody scrambles.
What it does
Nothing you have to think about.
Helm DJ is a tool for people who shouldn’t be looking at a laptop during the set. It runs in the background, reads the booth, and tells the rest of your rig what it needs to know.
- Reads every deck on the network automatically
- Drives lighting, video and timecode from what's playing
- Fires cues on track load, on-air, or on a timeline
- Per-deck routing so each player can drive its own destination
- Migrate cues between tracks with one click
How it fits
Quiet plumbing, loud effect.
It finds your decks
Plug Helm DJ into the same network your CDJs are on, and it picks them up. No drivers. No fiddling. It works with the players you already own.
It reads what’s playing
Title, tempo, position in the track, which deck is live — all of it, in real time. The same information the DJ sees on the platter, now available to the rest of the room.
You say what to do with it
Bind a cue to a track. Fire lighting on the drop. Send timecode to the video server. You decide the rules once, and Helm runs them every night without being asked.
The rig follows
Lighting console, media server, timecode box — they all get what they need in the language they already speak. No weird middleware. No extra boxes in the chain.
The parts that matter
Look at the actual app.
These are the screens you spend most of your time in. No decoration — this is what Helm DJ puts in front of you.
Deck row
The deck you actually watch.
One row per deck. Title, waveform with numbered cue markers, LIVE/ON AIR pill, BPM, SMPTE timecode and the timecode route it’s feeding. Glance at it, leave.
Deck 3
CDJ-3000Cue editor
One cue, four decks, per-deck payload.
Name it, set the trigger, pick MIDI Note or CC. Type * in any field to vary it by deck — the per-deck grid lights up so you can send Ch1 to Deck 1, Ch2 to Deck 2, and so on. Velocity accepts 127[1] for a one-second fade.
Edit Cue
✕One cue, per-deck payload. The base fields above marked with * pull their value from the matching row here. Leave blank to fall back to the base value.
Setlist migration
Branch a setlist, keep the cues.
Duplicate a setlist for tomorrow’s venue. Import tracks from last month’s show. Copy cues, labels or timecode from one track onto several. All the plumbing, none of the rebuild.
Track Migration
Source Setlist
Pick which setlist to clone. The original won’t be touched.
New Setlist Name
Track list
Capture from the booth, pick from the list.
The active setlist lives on the left. Select a track to edit its cues; hit Capture to snapshot whatever the deck is holding into the current list. Labels, notes and reference audio all travel with it.
Under the hood
Built for the pressure of show time.
- Runs native on macOSTiny native OS X app — not a browser, not an Electron shell.
- Reads the booth directlyTalks to your CDJs over the network. No adapters in the audio path.
- Clean, sample-accurate timecodeGenerates LTC through your audio interface — no third-party drivers.
Join the beta
We’ll send you a build.
Beta is invite-only while we ramp. Tell us a little about your rig and your upcoming shows — we prioritise operators who can give us real feedback from real nights.