A couple of weeks ago I posted a Show HN about Web Audio Studio (WAS) — a browser-based tool for exploring and debugging Web Audio API graphs through visualization. In WAS, you write code and generate a visual representation of the audio graph from it.
Show HN post: https://news.ycombinator.com/item?id=47216773
WAS: https://webaudio.studio
Example worklet graph (WhiteNoiseGenerator used as a foundation for percussion and complex sound effects): https://app.webaudio.studio/?s=DV3g9jCd
Since then, I've kept working on it and made a few updates:
— AudioWorkletNode support — you can now write and inspect custom DSP processors
— a mobile version
— graph sharing via links
Right now I'm more interested in understanding how people actually use the Web Audio API in practice, so I can better understand where WAS might actually be useful.
I'm trying to understand:
— how you write WAA code in real projects
— where you most often lose track of what's happening
— which debugging situations take the most time
— what tools you currently use
— and whether you see situations where WAS could be useful in your real workflows (if any)
If you've worked with Web Audio, I'd really appreciate hearing:
— what you were building
— what was hardest to understand
— how you ended up solving it
Real scenarios and concrete stories are much more helpful to me right now than feature ideas.
Thanks!