In loop-based rigs the tension arc is a staircase of discrete section states, not a continuous automation curve

In the loop-based rig (Strudel, Glicol), tension-arc and density-curve are expressed as a discrete sequence of section states — stepping from one section’s material to the next using arrange() or ribbon, not drawing a smooth continuous ramp. A ‘gradual build’ is therefore approximated as a staircase of section states plus per-section filter and density moves. True continuous long-form automation is blocked-on-L4 because the rig has no session-timeline mechanism. By contrast, imperative strongly-timed engines (ChucK, Sonic Pi, SuperCollider) advance a clock continuously and can ramp tension-arc and density-curve as true continuous automation. Tension-arc and density-curve are therefore approximate in Strudel and Glicol for this structural reason.

Examples

Strudel arrange: arrange([4, ~intro], [8, ~build], [16, ~main]) — discrete section steps ChucK: continuously ramp filter cutoff over 32 bars via now arithmetic

Assessment

Why is a ‘gradual build’ in Strudel approximate rather than truly continuous, and which engines support true continuous tension-arc automation?