Creator here, happy to answer any questions! Here's an example delay effect: <a href="https://dsp.audio/editor/QbQuSG8sMKsMnrqgf7NB/1" rel="nofollow">https://dsp.audio/editor/QbQuSG8sMKsMnrqgf7NB/1</a>
Please feel free to use the tool to prototype or show your creations around.<p>— Please note that the app runs only on Chrome > v66, for now, because Chrome is the only browser implementing the Audio Worklet[1] spec. Other browser will follow suit (hopefully) soon<p>[1] <a href="https://developers.google.com/web/updates/2017/12/audio-worklet" rel="nofollow">https://developers.google.com/web/updates/2017/12/audio-work...</a>
Creator here - thanks for the feedback!<p>For anyone interested on the stack, the visual part is React / Redux SPA. I use Firebase's Firestore as a DB (I wanted to try it and so far it's really cool) and Google Cloud Functions for the APIs. The repo is hosted on Gitlab and is a Lerna monorepo, which is amazing.
This is great! I really hope developers keep pushing the webAudioApi. Its not hard to imagine serious browser based DAWs within 5yrs. I've been doing my webaudio experiments here: <a href="http://treblemaker.ai" rel="nofollow">http://treblemaker.ai</a>
This is cool and looks promising! If you want some DSP functions in JS, I had made some[0] in the past. They're all MIT licensed and sometimes you would need to adapt the code a bit because of the imports and globals that are implicit as these were domain specific.<p>[0]: <a href="https://github.com/opendsp" rel="nofollow">https://github.com/opendsp</a>
You may like too this single file midi player that comes with a one line synthesizer<p><a href="https://github.com/aguaviva/SimpleMidi" rel="nofollow">https://github.com/aguaviva/SimpleMidi</a>
This is great!<p>I especially like that you've included a share mechanism. I built an audio dsp playground before, but didn't spend enough time on it to provide that.<p>Are you going to add a discovery page to browse people's creations?
Nice. The only thing I don't like about it is that its browser based, because - as a musician with a room full of hardware - its hard to get over the conclusion that browser-based music tools are simply not ready for production - i.e. I would never use this on stage or in the studio. Cute experiment though...
A sound engineering illiterate here. But, both the project and the new API from chrome looks like something very interesting that I'd not want to miss.<p>Can somebody ELI5 to me, what this is about? Or point me in the right direction perhaps.