Strudel re-evaluates on save without cutting audio — a syntax error keeps the previous pattern playing while the edit is not applied

When you save (or manually evaluate) a Strudel file, it calls evaluate(code) internally, which reloads the pattern gaplessly — the audio never cuts out. If the new code contains a syntax error, the previous valid pattern continues to play unchanged; the error is shown in the #err display. This means a performer can edit code freely: bad syntax does not silence the music, it just prevents the update from applying. The corollary: if you edit and hear no change, check #err for a syntax error. Individual $: voices are independent — commenting one out mutes just that voice on the next save.

Examples

Introduce an unbalanced bracket in one voice; audio continues with the last valid version while #err shows the parse error.

Assessment

A performer edits a Strudel pattern but hears no change in the audio. List the two most likely causes and the diagnostic step to distinguish them.