Create autopilot
create_autopilotCreate a beat-synced autopilot that randomizes a COMP's controls or cycles cues every N beats to keep visuals evolving automatically.
Instructions
Build a beat-driven auto-VJ: a Beat CHOP + a CHOP Execute DAT that, every N beats, either randomizes a target COMP's numeric controls (a hands-free drift, set by Amount) or cycles through its stored cues — so a set keeps evolving on its own. Creates a new baseCOMP under parent_path holding the Beat CHOP and the engine DAT; it modifies the target COMP at comp_path (its custom controls or stored cues) live at runtime. Live Active/Beats/Amount knobs let you pause or retune on stage. Reuses the tempo clock, randomize_controls and manage_cue mechanisms. Pair with a generated system (or a control panel) as the target. Returns a summary plus a JSON block with the container path, created node paths, the target, mode, beats, amount, engine path, any node errors, and warnings (no preview image — the output is a CHOP engine, not a TOP).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | 'randomize' nudges the COMP's numeric controls toward new random values each trigger (works on any COMP with controls). 'cue' cycles through the COMP's stored cues (needs cues from manage_cue). | randomize |
| beats | No | Fire an action every N beats (4 = once per bar at 4/4). | |
| amount | No | (randomize) How far to move toward random each trigger: 1 = full scramble, low = gentle drift. | |
| comp_path | No | COMP the autopilot drives — its numeric custom controls (randomize mode) or its stored cues (cue mode). Usually a generated system container or a control panel. | /project1 |
| parent_path | No | Where to create the autopilot engine. | /project1 |