Sonic Pi cannot feed the rig's 4-bin FFT bridge for audio-reactive visuals — it runs in its own IDE with a bundled SuperCollider server

Sonic Pi manages its own audio via a bundled SuperCollider server and outputs through its own IDE. It cannot feed the 4-bin FFT data that the rig’s Hydra/GLSL visuals read via the Strudel→Hydra bridge. There is no .analyze(‘hydra’) equivalent. This means audio-reactive visual programming that assumes a rig bridge is not possible with Sonic Pi as the audio source. Sonic Pi is useful for authoring and cross-framework concept transfer, but always carries runs_in_rig: null. Treat it as a standalone system or as a source of concepts portable to Strudel/Tidal.

Examples

Playing a pattern in Sonic Pi while Hydra visuals run in the browser: a.fft will remain 0 — there is no audio tap from Sonic Pi to the browser rig.

Assessment

Explain why reactive visuals built for Strudel (using .analyze(‘hydra’) + a.fft) cannot be directly replicated with Sonic Pi as the audio source in this rig.