Deleting and disabling events
Sometimes an event is wrong — delete it. Sometimes it's right but shouldn't fire today — disable it. Disabling is non-destructive: the event stays in the list, ready to re-enable later.
Delete
Permanent removal. There's no Undo.
- Open the Event List.
- Swipe right on the event row, or long-tap and select Delete.
- Confirm.
Disable a Cut, Vamp, or Hold
There's no separate "disabled" button on Skip events. To disable a Cut, Vamp, or Hold, turn off its specific toggle in the event editor. The event stays in the list and acts like a regular Skip — playback runs through the time range normally, and the GO AHEAD button stays available during the event window so you can still tap to advance early if you need to.
Use this when a director is undecided about whether to cut a section, vamp through a transition, or hold for an applause break. Toggle off for tonight's run, toggle back on tomorrow.
Disable a MidiEvent
MidiEvents have a Disable toggle in their editor. It's designed for scene events that the operator fires manually: a disabled event stays in the list but isn't highlighted as the next active or "on-deck" cue, so the GO CUE / GO AHEAD sequence steps over it without firing.
Useful when a cue is wrong for tonight's run but you want to keep it around for tomorrow — toggling beats deleting and re-adding.
For partial disabling — stopping just the mic toggles, just the audio, or just the OSC payload of an event — see MIDI events.
Notes
- No Undo on delete. Use disable for temporary changes — directors change their minds, and it's faster to toggle than to re-add a deleted event.
- Disabled events are visible. A Cut, Vamp, or Hold with its toggle off shows a different visual state in the event list so it's clear at a glance which cues are active.