Tracks & shows
Once a paired Helm Cues app syncs a project, its tracks (sequences) appear in the cloud — complete with master audio, cue lists, and configuration. The cloud renders them read-only: you review and comment here; programming happens on the desktop. On top of that, the cloud owns shows (setlists) — ordered runs of tracks that Cues syncs back down.
Track pages
Section titled “Track pages”Open a track from the project overview’s Tracks / Sequences tab. Each track page gives you:
Waveform player. The master audio renders as a scrubbable waveform with a transport bar. The time display is SMPTE-first — current position shown as timecode using the project frame rate and the track’s start offset, with clock time underneath. Cue markers overlay the waveform; click one to jump there.
Transport toggles:
- Cues on/off — show or hide the cue markers on the waveform.
- Follow on/off — auto-scroll the cue list so the currently “live” cue (last cue at or before the playhead) stays centred during playback.
- LTC routing — if the master audio carries LTC on one channel, the audio-config popover sets which channel is LTC, whether to mute it, and whether to duplicate the programme channel to both ears. Playback in the browser honours it, so you never blast timecode into your headphones.
- Comment at [time] — drop a timestamped comment at the playhead.
Track configuration. Read-only blocks showing what the desktop has set: audio routing (LTC channel, playback routing, device), timecode config (LTC/MTC devices, frame rate, offset), grandMA2 config (page, executors, sequence start, TC pool, sync status), and the show’s team/roles sheet.
Cue list. Every cue with number, time, label, department, stack, and trigger type. Search by label/number/notes and filter by stack, department, or trigger. Click a row to seek the audio there and expand full detail (sector, fades, pre/post waits, notes). Comment on this cue pins a comment to the cue’s timestamp, pre-filled with its name.
Track media. Files referenced by this track (stems, video content, documents), each linking into the file viewer.
Comments panel. Timestamped threads down the right side — click a thread to seek to its moment; numbered markers on the waveform match the thread numbers.
Shows / setlists
Section titled “Shows / setlists”The Shows / Setlists panel on the project overview builds ordered runs of tracks in the cloud:
- Click + New show and name it (e.g. “Sunday night setlist”).
- Expand the show and add sequences from the dropdown — it only offers tracks not already in the list.
- Drag rows to reorder; remove with ×.
Cues pulls these on every sync and mirrors them in the desktop UI, so the running order you agree in the browser is what the operator sees. For v1 the direction is one-way: shows are edited in the cloud only, Cues reads them.
Setlists can also be attached to calendar events and published on the public page as track-list or track-pack blocks.
Ordering, totals, and audio preview
Section titled “Ordering, totals, and audio preview”Wherever tracks are listed on the public page, the block’s Order setting controls sequence:
| Mode | Behaviour |
|---|---|
| Show order | The track order from the synced Cues show (default) |
| A → Z | Alphabetical by name |
| Duration | Longest/shortest by track length |
| Manual | Your own order, set with ↑↓ in the builder |
Track-list and track-pack blocks also show a total running time badge in their header — the summed duration of every track in the block.
Inline audio previews use the shared waveform player: play/pause, scrub, a channel selector (L / R / L&R — for stems or LTC-carrying files where you only want one channel, folded to both ears), and a volume slider that goes to 200%. Above 100% the player routes through Web Audio gain to genuinely boost quiet reference bounces.
How DJ setlist bundles relate
Section titled “How DJ setlist bundles relate”Helm DJ’s unit of handover is the .helm bundle — a folder holding a setlist, its cues, and reference audio (see Tracks & setlists in the DJ docs). The cloud speaks the same per-product data protocol Cues uses, and the v1 API reserves a data slot per product per project — DJ setlist data lands there as it comes online. Today the browser-rendered track experience described above is driven by Cues sync; DJ’s cloud sync is part of the same integration surface and is being wired up against it.