Live data from Hacker News

Show HN: Wavepot – Digital audio workstation of the web

wavepot.com

51–60 of 137 posts

Re: Show HN: Wavepot – Digital audio workstation of the web

#51
post #6

Earlier quoted context omitted.

It seems their goal is to make a full-fledged DAW in the browser, but they are not there yet (and far from it from what I can tell). How they would be able to fund all that for $2k is beyond me. That said, it's a really clever idea to have all the source editable, since js is an interpreted language anyway. One can imagine a future where the community not only shares songs and sounds, but the DSP units themselves. Un…

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.

Are you aware of the Web Audio API? It's an API designed especially to address those concerns, and achieves low latency and high performance where it is available (Chrome, Firefox and some versions of Safari currently).

https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specifica...

Re: Show HN: Wavepot – Digital audio workstation of the web

#53
post #36

Wavepot team: really awesome stuff! love it. At Bandhub ( http://bandhub.us ) we are looking for ways to integrate programmed music into our web DAW. If you guys are up for a collaboration or want to discuss ideas, ping me osi (at) getbandhub (dot) com

Cool site. You need more genre categories however; Synth and/or Electronic would be a good start since you are missing anything along those lines. Probably a EDM category as well otherwise that's what either electronic and/or synth will end up being. Also, Find Musicians doesn't seem to be working, at least not in Chrome on osx.

what do you see? can you send me the console output too?

Re: Show HN: Wavepot – Digital audio workstation of the web

#54
post #51

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.

Are you aware of the Web Audio API? It's an API designed especially to address those concerns, and achieves low latency and high performance where it is available (Chrome, Firefox and some versions of Safari currently). https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specifica...

Yes, and it works by mostly avoiding realtime DSP in javascript. It provides a high-level API for wiring together prebuilt audio processing nodes. Much like using browser animation APIs vs programatic animation. My point is about the feasibility of JS signal processing, not the feasibility of using JS to glue together signal processors.

The WebAudio API does provide a ScriptProcessorNode for JS processing, but it appears to suffer from the problems I described. The spec seems to warn against using this for realtime processing, fwiw.

Re: Show HN: Wavepot – Digital audio workstation of the web

#56
post #50
post #48

Earlier quoted context omitted.

yea want to try it but i'm stuck on max 5... max upgrades are more expensive than they're worth & now its splitting into multiple products (max4live,gen) so i'm kindof on an every other generation plan unfortunately. especially annoying when features you like get deprecated (pluggo, ms. pinky) though i understand gen & max4live both kinda serve as pluggo replacements. all in all its just hard for me to pull the trigg…

And I should point out that I personally feel kinda guilty... I met Miller Puckette and he was so enthusiastic about PureData and how much more the community could grow. I realize the biggest reason Max is thriving is because of marketing and now integration with Ableton. I feel like if something were done to prevent Pd from being wiped off the map we could have had an open source community by now rather than Cycling…

There's a reasonably active community around PD, but it has the same problem as a lot of other open source software - it's hideously ugly. IIRC the user interface is done with TCL/TK. Given the large number of competing products in the same space, people who are not heavily committed to open source have little incentive to use it, unfortunately. I'd say a visual/UI makeover is a higher priority right now than extending the PD library or other tasks.

Re: Show HN: Wavepot – Digital audio workstation of the web

#57

Holy crap! This is great!

Would someone kindly explain why I and two other users (msane and jrlocke) were downvoted for simply expressing delight? Is that somehow unwelcome? I don't see anything against that in the guidelines: http://ycombinator.com/newsguidelines.html Note, this isn't a complaint , it's merely a request to understand why my comment is inappropriate and to understand how I can express my approval of a submission without losin…

It's not against the guidelines, but it doesn't create conversation. Many people find that fairly useless, and prefer comments with substance that advance the community.

The best way to express your approval of a submission? Upvote it.

Re: Show HN: Wavepot – Digital audio workstation of the web

#59
post #40

A scene has sprung up around music based on algorithms, called Algorave http://en.wikipedia.org/wiki/Algorave Vice did an article on the subject a few months back which gives an overview of the scene (from a layman's view) http://www.vice.com/en_uk/read/algorave-is-the-future-of-dan...

This is really, really interesting.

come and do some wavepot at an algorave

Re: Show HN: Wavepot – Digital audio workstation of the web

#60
post #6

Earlier quoted context omitted.

It seems their goal is to make a full-fledged DAW in the browser, but they are not there yet (and far from it from what I can tell). How they would be able to fund all that for $2k is beyond me. That said, it's a really clever idea to have all the source editable, since js is an interpreted language anyway. One can imagine a future where the community not only shares songs and sounds, but the DSP units themselves. Un…

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 reply on HN