Show HN: Wavepot – Digital audio workstation of the web

Post by montag » Wed, Jun 18, 2014, 7:53 AM UTC

CamperBob2 wrote: post #60

chrisdevereux wrote: post #37

Earlier quoted context omitted.

Realtime audio DSP seems like about the last thing that in-browser JavaScript was designed to do well. Janky audio is unnacceptable in a way that janky visuals aren't. It totally kills the experience. Without very strong guarantees about GC latency and thread scheduling that are neither available nor on the horizon for in-browser js, it won't work for anything beyond fun hacks.

If you don't care about latency, and in this "DSP sandbox" application you probably don't, JavaScript is fine for real-time DSP. JS under V8 and similar engines can be quite fast. You aren't going to digitize 100 MHz of RF spectrum and build an SDR in JavaScript, but for audio rendering work it'd be fine. Cool hack.

Post by stagas » Wed, Jun 18, 2014, 9:21 AM UTC

recursive wrote: post #73

Is there a way to contribute without using bitcoin? This is awesome and I want to support it, but I'm not really interested in getting involved in bitcoin.

Post by jarmitage » Wed, Jun 18, 2014, 9:39 AM UTC

zhodge wrote: post #98

As someone who's completely ignorant to the concepts behind algorave, could anyone more experienced outline the helpful prerequisites to know before I experiment with a tool like Wavepot? I assume it's mostly the (basic?) physics of sound waves that I'd need to understand?

Post by chrislo » Wed, Jun 18, 2014, 11:19 AM UTC

chrisdevereux wrote: post #106

notthetup wrote: post #82

Earlier quoted context omitted.

"The WebAudio API does provide a ScriptProcessorNode for JS processing, but it appears to suffer from the problems I described." Yup. That is being worked on by W3C and the WebAudio committee as we speak. WebWorker based JS processing is something being considered. https://github.com/WebAudio/web-audio-api/issues/113 http://lists.w3.org/Archives/Public/public-audio/2013OctDec/... I am expecting this to be resolved in…

Meeting real-time guarantees pretty well isn't good enough for a DAW. Not without a lot of buffering (and therefore latency), anyway. The WebWorker proposal is interesting. If the worker has its own heap and realtime scheduling with a correctly configured GC, it would be a big improvement. Getting the different implementations to work consistently enough will be challenging, though. Meeting realtime deadlines is diff…

Post by stagas » Wed, Jun 18, 2014, 12:16 PM UTC

yaxu wrote: post #59

stagas wrote: post #40

Earlier quoted context omitted.

This is really, really interesting.

come and do some wavepot at an algorave