Create beat-grid sequencer
create_beat_grid_sequencerCreates a beat-synced step-grid sequencer in TouchDesigner, using a Table DAT for per-step patterns and firing parameter or cue actions on each beat boundary for rhythmic automation.
Instructions
Build a programmable step-grid sequencer driven by a Beat CHOP on the global TD tempo: a Table DAT holds the per-step pattern (values or 1/0 flags), and a CHOP Execute DAT fires on every beat boundary, reads the current step (count % steps) from the table, and dispatches — action=param sets a custom parameter to the step value; action=cue recalls the cue for active steps (cues stored with manage_cue). The deterministic, repeating-rhythm instrument between create_autopilot (random drift) and create_cue_sequencer (linear list): program a strobe on beats 1+3, a hue shift on the bar, etc. Reprogramme the grid live by editing the step_table DAT. NOTE: beat-callback timing is UNVERIFIED offline — check op().time.play if steps don't fire when the TD timeline is paused.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Name for the sequencer COMP. | beat_grid |
| param | No | (action=param) The custom-parameter name on the target COMP to set on each active step. | |
| steps | No | Number of steps in the grid (e.g. 16 = one bar of 16th notes at 4/4). | |
| action | No | param: set a target custom-parameter value per active step; cue: recall a named cue per active step (cues stored with manage_cue). | param |
| target | Yes | COMP whose parameter or cue each active step fires on a beat boundary. | |
| pattern | No | Per-step values (action=param) or 1/0 active flags (action=cue); length should match 'steps'. Omit to auto-generate an example pattern. | |
| bpm_source | No | Path to an existing Beat CHOP or tempo source. Omit to create a new Beat CHOP (on the global TD tempo). | |
| parent_path | No | Parent COMP path to create the sequencer inside. | /project1 |