Helm Cues
Helm Cues is a desktop app for macOS and Windows. Build cue sequences, organise them into tracks, and fire them against live timecode — Cues is the show surface the rest of the rig hangs off.
What it does
Section titled “What it does”- Cue lists on timecode. Cues carry a time, a type, and outputs; when the clock hits the mark, they fire. Timecode can be generated internally (master) or chased from an external source (slave).
- LTC and MTC I/O. SMPTE LTC over audio and MIDI Timecode in both directions, with the frame rates and drop-frame handling live production expects.
- Session master on Helm Protocol. Cues hosts the show session: hardware like Helm Clock and other clients discover it on the network, join, receive the show state, and follow timecode with delta updates as the show changes. See the protocol spec.
- grandMA2 sync. A Lua plugin on the console polls Cues over HTTP (configurable port, default 8765) for bidirectional sync between the cue list and the desk — TimecodeMAte-style workflow without the DAW.
- MA3 track navigation. A companion grandMA3 plugin (
HelmTrackNav) keeps the console’s sequence in step with the active track; it ships via Helm App downloads. - MIDI and OSC outputs for everything else in the rig.
Tauri desktop app: SvelteKit + TypeScript frontend, Rust backend. The Rust core owns the protocol implementations (timecode, MIDI, OSC, the MA HTTP server) and the Helm Protocol session layer.
Status
Section titled “Status”Cues is being rebuilt. The overview above describes the product as designed and largely as implemented; detailed docs — technical architecture, timecode reference, and grandMA2 communication — are drafted and will publish here as the rebuild lands. Until then this page and the products overview are the canonical references.