Tidal evaluates a block on the editor's eval keystroke, not on file-save like the rig hot-reload

Tidal’s evaluation model differs from the livecoding rig’s hot-reload workflow. In Tidal, a block is evaluated with the editor’s eval keystroke (Ctrl/Shift-Enter in the standard Tidal editor) rather than automatically on file-save. Each d1..d16 channel is edited and evaluated independently; re-evaluating d1 swaps just that channel gaplessly without touching the others. This is distinct from Strudel in the rig, which hot-reloads on every file-save. The eval-per-block model gives finer control but requires an explicit keystroke per edit.

Examples

— In Tidal: press Ctrl-Enter on this block to evaluate it live: d1 $ s “bd sn” # room 0.3 — Strudel rig: just save the file, hot-reload fires automatically

Assessment

Describe how Tidal evaluation differs from the rig hot-reload. What happens when you re-evaluate d1 while d2 is playing?