Sequences are reusable JSONC workflows for coordinated camera, light, GPIO, and timing operations. Open the Sequences page to create, edit, validate, run, duplicate, or delete them.

Start with an example

Camera Server seeds the Examples list with workflows for common setups. Restore an example to return it to its shipped content. Duplicating an example is a useful starting point because it preserves the structure while giving you a separate sequence to edit.

The shipped examples include:

• Timelapse repeat: warm up once, then capture a fixed number of frames at a configurable interval.
• Burst then single photo: switch image modes, capture a burst, switch back, and take a final single shot.
• Staggered groups: warm up and capture several camera groups at precise offsets on one shared timeline.
• Two groups with delayed trigger: warm up and capture two groups with a delay between them.
• Setting two shots: change image quality between two captures, with warmup and transfer pauses.
• Light sequences: broadcast white, blue, and off states, run an effects show, or play and pause a light preset.
• GPIO sequences: blink a pin or broadcast a set and pulse pattern to GPIO nodes.

The examples use placeholder camera groups, node targets, light groups, and preset IDs where your installation needs local values. Update those references before relying on an example at an event.

Sequence structure

A sequence has an ID, name, optional description, and an ordered steps array. Each step has a type and parameters. The editor accepts JSONC, so comments and trailing commas are allowed.

Common step types include:

• Trigger: warm up, capture, or run another camera trigger phase.
• Set setting: change a camera setting for selected groups.
• Shot: place several camera actions on one shared clock using atMs offsets.
• Repeat: repeat a group of steps a chosen number of times.
• Light: set or animate light output, including brightness, color, and effects.
• Light preset: play, pause, resume, or stop a configured light preset.
• GPIO: set or pulse a pin on selected nodes or all available GPIO nodes.
• Log: write a useful marker to the run log.

A step's duration is the pause after that step. It defaults to 500 ms when omitted and can be set to 0 to continue immediately. In a shot block, use each action's atMs offset for precise shared timing instead of relying on step duration.

Validate and run

Use Validate before saving a larger edit. Validation checks the document structure, supported step types, required fields, target shape, and limits. Run a sequence from the page and watch the run log. You can run an individual light step from the visual preview when checking light timing.

Bind a sequence to the main trigger from the trigger binding control when it should replace the normal capture action. For event-based automation that should start the sequence only in specific circumstances, use a rule instead.

Keep a working copy of a known-good sequence before changing camera settings or timing. Test with the actual camera groups and nodes, then confirm the resulting files and transfer timing before using the sequence during a live session.