Stepping kaleidoscope symmetry up on a downbeat gives a visual drop paired with an audio peak

The kaleido-open visual transition is triggered at a drop or peak, where the visual field suddenly gains symmetry and complexity. Adding .kaleid(n) with a higher n is saved exactly on a bar line so the 1-frame flicker of Hydra’s hush+eval reads as a cut rather than a glitch. For a gradual build version, the kaleid count can be driven reactively from the bass bin. This move should be coordinated with the audio drop on the same downbeat, which requires the two saves to land on the same bar line.

Examples

osc(30, 0.05, 1).color(1,0.4,0.7).kaleid(6).out() landed on a drop downbeat. Reactive ramp: .kaleid(() => 2 + a.fft[0] * 6) grows the symmetry during the audio build.

Assessment

Why must the kaleido save land on a bar line? How does the bass-driven reactive ramp differ in purpose from the static step-up?