Strudel produces no sound until the first user click unlocks the browser AudioContext — silence at startup is autoplay policy, not a bug

Browsers suspend the Web Audio AudioContext until a user gesture occurs, per autoplay policy. In this rig a Strudel pattern will play no sound at all until you click once on the page, which unlocks audio. Nothing is broken — the pattern is running silently. Separately, drum sample voices stay silent until the dirt-sample bank finishes downloading on startup, whereas synth voices (sawtooth, etc.) sound immediately because they need no network load. A performer who hears nothing at launch should click once and wait for samples to finish loading before diagnosing further.

Examples

Load a Strudel patch and it stays silent; one click on the page starts the audio. s("sawtooth") sounds instantly; s("bd*4") waits for dirt-samples to load.

Assessment

A performer loads a Strudel patch and hears nothing. Name the two startup-timing causes (one gesture-related, one loading-related) and how to resolve each.