I don’t know who the Web Audio API is designed for
I&#x27;ve spent quite a lot of time working with the Web Audio API, and I strongly agree with the author.<p>I got pretty deep into building a modular synthesis environment using it (<a href="https:&#x2F;&#x2F;github.com&#x2F;rsimmons&#x2F;plinth" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rsimmons&#x2F;plinth</a>) before deciding that working within the constraints of the built-in nodes was ultimately futile.<p>Even building a well-behaved envelope generator (e.g. that handles retriggering correctly) is extremely tricky with what the API provides. How could such a basic use case have been overlooked? I made a library (<a href="https:&#x2F;&#x2F;github.com&#x2F;rsimmons&#x2F;fastidious-envelope-generator" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rsimmons&#x2F;fastidious-envelope-generator</a>) to solve that problem, but it&#x27;s silly to have to work around the API for basic use cases.<p>Ultimately we have to hold out for the AudioWorklet API (which itself seems potentially over-complicated) to finally get the ability to do &quot;raw&quot; output.