Live data from Hacker News

Show HN: Wavepot – Digital audio workstation of the web

wavepot.com

61–70 of 137 posts

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

#61
can you tell more about how you coded the fundraiser modal? is it just checking the balances on those addresses then converting them to USD? im sure its a simple solution but i'd be happy to hear more about it - i was thinking of making a similar one for my own project, but it would be good if it displayed different addresses per visitor for better obfuscation...lets say have half of a wallet full of addresses, then also check server side whether the displayed is a valid one

[edit: using something like coinbase would solve this, but how could you work it out without a 3rd party and any fees?]

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

#62

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.

I'm assuming that a full-fledged DAW cares a lot about latency. Live performance becomes difficult when latency creeps much above 5ms, for example. A lot of things that you normally don't think about (like when to allocate a buffer of memory) become critically important with low latency requirements.

That isn't an issue for the demoed app, but it is for the hypothetical longer-term goal under discussion.

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

#64
This is amazing, but I wish there was a clear way of knowing when there is an error causing your changes to not be output.

I fiddled for a couple of minutes without any changes before realizing i had forgotten to initialize a variable. (the x checkmarks don't seem to work for unassignad variables..)

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

#66

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, can't wait to check it out. Would love to see deeper support for programming and mastering

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

#67

Earlier quoted context omitted.

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.

I'm assuming that a full-fledged DAW cares a lot about latency. Live performance becomes difficult when latency creeps much above 5ms, for example. A lot of things that you normally don't think about (like when to allocate a buffer of memory) become critically important with low latency requirements. That isn't an issue for the demoed app, but it is for the hypothetical longer-term goal under discussion.

Yeah, I think they're making a mistake by using the term DAW. That term already means something, and this isn't it.

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

#68

This isn't really a DAW. For those unfamiliar, a DAW is a fully-featured music creation environment including sound design, composition, recording, arrangement and mixing in one interface. Examples include logic, cubase and ableton. While I suppose this does allow for all of those things, as much as any programming language with access to an audio API does, this would be better described as a web-based DSP livecoding…

> I'm aware of the oscillator/filter primitives in the HTML5 audio API from the minimoog google doodle, but this seems more elaborate than that.

An oscillator and a filter modulator are pretty much all you need to create this particular app. There's no reverb, and any delay effects are being "hard-coded" with simple degrading velocities. All synthesizers are built from these ultra-simple components, maybe 2 or 3 more and you have everything you need to build a digital synth purely with web technologies.

Post reply on HN