Tidal does not run in this rig; every Tidal pattern must be compiled to Strudel to be heard

TidalCycles requires GHC (Haskell), SuperCollider, and the SuperDirt Quark — none of which are installed in this rig. Every Tidal corpus record is runs_in_rig: null; none was executed here. The value of the Tidal layer is portability and conceptual reasoning: Strudel is a JavaScript port of Tidal, so a Tidal idea maps to Strudel by the shared concept-id. The correct workflow is to reason in Tidal idioms then emit Strudel for the rig’s actual audio engine. Offering to run a Tidal patch directly in the rig is always wrong.

Examples

// Tidal (not runnable here): d1 $ s “bd sn” # speed 2 // Compiled to Strudel (rig-runnable): s(“bd sn”).speed(2)

Assessment

A learner asks you to run a Tidal pattern in the rig. What is the correct response and workflow?