Track Program

What it's for — The Track Program visualises your Auto Pilot fire plan against the loaded track's structure. Use it to review and tune the automation rules that govern when CueSync fires Looks and output actions across your show.

The automation lanes show the armed fire plan — what is actually going to fire on this track, after rule matching, the significance threshold and every rule you have switched off. A moment in the track that no rule matched does not appear.

The screen, region by region

Toolbar (top) — Contains the Show Program name, the planned-fire count ("N planned" — amber when nothing is planned), a Rules chip that collapses the sidebar, a Follow chip, the Auto Pilot state pill, and zoom in/out buttons. The playhead position and pixels-per-beat density are displayed on the right. Clicking a marker on an automation lane adds an inspector chip showing its type, bar and confidence.

Beat ruler lane — A horizontal ruler marking beat positions across the full track. Labels appear at regular beat intervals that adapt to the current zoom level.

Phrase lane — Colour-coded blocks representing the phrase structure of the loaded track (Intro, Verse, Chorus, Bridge, Break, Outro, etc.). The lane width matches the beat ruler so you can see exactly which phrases fall where.

Energy lane — A waveform-style curve showing the track's energy level beat-by-beat. Peaks correspond to high-energy moments such as drops and choruses; troughs correspond to breakdowns and outros. It is a read-only view of the analysed track — there is no envelope drawing here.

Lighting automation lane — Shows the entries in the armed fire plan that drive a lighting console or DMX (grandMA2/3, Avolites, ETC Eos, ChamSys, Art-Net, sACN). Each marker is a beat where something is queued to fire; it fills in and glows once it has fired.

Effects automation lane — Shows the entries that drive anything else — video servers, show control, laser, MIDI, OSC. An entry that drives both a console and a video server appears in both lanes, because it moves both. Small hollow rings are pre-roll fires: the preparatory actions that run N beats ahead of a moment.

Rules panel (right sidebar, 320 dp) — Collapse it with the toolbar's Rules chip when you want the full window for the lanes. Lists all rules in the active Show Program. With no Show Program active, it names the Auto Pilot profile driving the lanes instead. Each rule entry shows:

• Name and priority badge
• High-impact badge (if the rule affects prominent moments)
• Enable/disable toggle — turn individual rules on or off without deleting them
• Condition summary — a human-readable description of what triggers the rule (phrase type, energy threshold, BPM range, etc.)
• Intent count — how many output intents the rule carries
• Expandable detail — click a rule to see the full condition tree

Common tasks

1. Load a track to visualise its fire plan — Load a track on a connected Pioneer CDJ/XDJ, or from Local Audio. The timeline populates with that track's structure and Auto Pilot's planned fires.
2. Review the automation plan — Scan the Lighting and Effects lanes to see where Looks and actions will fire. Compare them against the Phrase and Energy lanes to confirm they land at the right musical moments.
3. Enable or disable a rule — In the Rules panel, click the toggle next to any rule. The plan rebuilds immediately against the currently playing track, and the lanes redraw to match: markers a disabled rule was responsible for disappear. Moments that have already fired stay fired — toggling a rule mid-track never re-fires them.
4. Select a rule to inspect its conditions — Click a rule row to expand it and read the full condition tree (phrase type, energy range, BPM window, etc.).
5. Zoom the timeline — Click the zoom buttons in the toolbar, or press = / - (with or without Cmd). Beat density adjusts so labels remain readable at every zoom level. Arrow keys scroll, Home jumps to the start, and F toggles playhead-follow.

Tips & gotchas

• The timeline reflects the current track. If no track is armed, the timeline shows an empty state with a prompt to load one. The fire plan updates automatically as you change tracks on the decks.

• The plan can change while the track plays. Rules with energy, trend, section or drop-count conditions are re-evaluated at every phrase boundary, so a rule that only applies to a peaking room joins the plan when the room peaks. Rules with journey conditions ("after 20% of the track") are resolved per moment when the track arms, so those do not move.

• "N planned" is not the rule count. It counts the fires scheduled for this track. A program with twelve rules that matches two moments reads "2 planned" — if that number is lower than you expect, or amber at zero, the rules are not matching this track's structure.

• Automation snaps to the beat grid. All planned fires are positioned at beat boundaries. The fire plan cannot place an action at a sub-beat position — that precision is handled by per-cue nudge offsets configured in the Cues screen.

• Disabling a rule here affects the whole show. A rule you disable in the Rules panel stays disabled for every track until you re-enable it. If you only want to suppress a rule for one moment, consider adjusting its conditions rather than toggling it off entirely.

• The Track Program is a read-and-tune view, not a clip editor. You cannot drag automation blocks to new positions here. To change what fires and when, edit the rules in the Rules panel or adjust the Look affinities in the Looks & Scenes screen.

Related

• Track Prep — Analyse the track structure that feeds the Track Program
• Looks & Scenes — Configure the Look affinities Auto Pilot uses to populate the Lighting lane
• Cues — Manual cues that fire alongside Auto Pilot's automation