Punctual edits quantize to the next cycle boundary with a short crossfade by default, so a change can take up to one cycle to land

When you re-evaluate a Punctual statement, the new definition does not switch in instantly. By default the change is quantized to the next cycle boundary and applied with a short crossfade, so an edit may take up to one full cycle to become audible or visible. This is deliberate — it keeps live changes musical and glitch-free — but it surprises performers expecting an immediate switch. Override the timing per statement with the crossfade operator: <> 0 gives a near-immediate switch, while <> n sets an n-second morph. Standalone cycles are 2 seconds (cps 0.5), so the default wait can feel long.

Examples

osc 220 >> audio; re-evaluated waits for the next cycle to swap. osc 220 >> audio <> 0; switches almost immediately. <> 4 morphs slowly over 4 seconds.

Assessment

A performer edits a Punctual line and the change lags by up to two seconds before appearing. Explain the default behaviour and show how to make the switch near-instant.