In this livecoding rig a file save is the performance action: Strudel hot-swaps gaplessly and Hydra re-evals on the same GL context

The rig is designed so that every file save is immediately heard and seen by the audience. Strudel’s evaluate() hot-swaps the running pattern gaplessly (no page reload). Hydra calls hush() then eval() on the same GL context, which may produce a one-frame flicker. Because each save is public, edit cadence is a performance variable — not a background bookkeeping concern — and determines how changes read to the audience.

Examples

A Strudel save that adds a .degradeBy(0.3) to one voice is heard immediately on the next cycle boundary. A Hydra eval can produce one frame of black on save.

Assessment

Explain why edit cadence is considered a performance variable in this rig, and describe the observable difference between a Strudel save and a Hydra save.