5 ms·
React is actually really ideal for web audio components. The web audio api is quite easy to use for the most part. The hard part tends to be building usable u
by joshontheweb 10y ago
React is actually really ideal for web audio components. The web audio api is quite easy to use for the most part. The hard part tends to be building usable ui on top of it. I've tried in the past to bundle up modular audio components in a way that they can be used in a package manager. It is hard to do well since you also need css and html to go along with the js. With react, all that stuff is already together in one modular piece that is easy to install in your audio chain.
I've worked on building some audio stuff before using backbone. I might restart with React. In the very least, I will try and implement the redux pattern.
My pet project: http://robotaudio.com/ http://robotaudio.com/
more full featured synthesizer: https://github.com/joshontheweb/synth https://github.com/joshontheweb/synth
Edit: Looks like the layout is bonkered for some reason. It normally looks better :D
- david-given 10y agoThat's really cool! How much of the audio processing is software DSP in Javascript, and how much is wiring together API components?
- joshontheweb 10y agoIdeally none of it. In this app I don't believe that I used any scriptProcessorNodes. I can't remember though. The general idea is that you are connecting nodes into an audio grid but all of the dsp is happening natively. You can process the audio manually in js but it isn't as fast and is generally frowned upon. I believe that they are deprecating the scriptProcessorNodes and providing a way for you to define dspin js but have it run on the system level.