Strudel audio requires a user gesture to unlock the AudioContext — code cannot force it

Web browsers block audio playback until the user has interacted with the page (clicked or pressed a key). Strudel’s AudioContext remains locked in a ‘suspended’ state until this user gesture occurs. If the start overlay is never clicked, no sound plays even if the code is correct and patterns are running. There is no error in #err and no console throw — silence is the only symptom. This cannot be bypassed in code; the only fix is to click the page (or the play button/overlay) once to unlock audio.

Examples

Load the Strudel rig, paste a valid pattern, and save without clicking — silence. Click anywhere on the page — audio starts immediately.

Assessment

Describe the symptom of a locked AudioContext in Strudel. Explain why it cannot be fixed in code and what the required user action is.