Another more DAW-esque pure HTML / js DAW in the browser: http://hya.io
Show HN: Wavepot – Digital audio workstation of the web
131–137 of 137 posts
Re: Show HN: Wavepot – Digital audio workstation of the web
#132what language is this ? i see it is not php ...
Re: Show HN: Wavepot – Digital audio workstation of the web
#133Earlier 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…
PD and Max-MSP are from the same stable, and PD is the poor man's Max-MSP. I feel that PD is an excellent learning tool if you want to learn about synthesis or DSP more generally, but as a musician's tool it's just not ready. A lot of the music made with PD is pure crap, or even a type of anti-music, or puts forward some kind of alternate musical theory of its own which nobody can understand. PD music is usually too detached from normal conventions such as 12 TET, harmonies and progressions to be listenable. Typically the PD user will produce something with weird bell sounds, stuttering percussive noises or massive pad washes going in and out. Not conventional music. The reason is that PD doesn't provide enough built-in function shortcuts. If you want to make music, PD is a practically useless interface. By the time you've programmed a very basic synth, any inspiration has long gone. An instrument is something that should need no foreplay beyond just turning it on and picking it up, before actually playing it. If you want to make something recognizable as music with PD, you will need to first download someone else's synth patch or copy a subtractive or FM synth from a book first. And then you'll find it has no patches you can modify (unless you make them yourself). The time between turning on the computer, setting up your synth and playing your piece is simply too long.
Re: Show HN: Wavepot – Digital audio workstation of the web
#134This 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…
This is awesome! I'll certainly contribute to this. Will the source be opened up? Here's a delay filter: var delay_array = []; var delay_length = 5; var delay_feedback = 0.6; var delay_volume = 0.4; function delay(x) { y = 0; if (delay_array.length Include this in the DSP return code, ie; return delay(synth);
Yes that's a good delay filter but it's also a good example why this type of user-programmable synth apparatus, which looks similar to CSound, won't catch on. There is much more going on in the typical delay sound itself than just a delayed iteration of a sample. A pure delay is boring. There is the possibility to model all kinds of analog and hardware digital delays with additional coding, but people have been doing that for years and it's no surprise really that commercial companies do it best (and they won't bother unless there's a way to protect proprietary code such as VST).
Re: Show HN: Wavepot – Digital audio workstation of the web
#135it's probably me, but I get nothing... - ff (latest beta) : waveform thingy works, no sound - chrome (latest beta) : no waveform, no sound - IE (11) : nothing
Linux Mint 14 (desktop) and CyanogenMod 10.2.1-flo (mobile, mod based on Android 4.3.1) user here.
For Mint: Firefox 29 - everything works; Chromium 34 - only grey background
For CyanogenMod: Chrome 35 - everything works; Dolphin 10.3.1 - only grey background
Re: Show HN: Wavepot – Digital audio workstation of the web
#136Earlier quoted context omitted.
This is awesome! I'll certainly contribute to this. Will the source be opened up? Here's a delay filter: var delay_array = []; var delay_length = 5; var delay_feedback = 0.6; var delay_volume = 0.4; function delay(x) { y = 0; if (delay_array.length Include this in the DSP return code, ie; return delay(synth);
Yes that's a good delay filter but it's also a good example why this type of user-programmable synth apparatus, which looks similar to CSound, won't catch on. There is much more going on in the typical delay sound itself than just a delayed iteration of a sample. A pure delay is boring. There is the possibility to model all kinds of analog and hardware digital delays with additional coding, but people have been doing…
There's more to digital audio processing than code? I don't get it. Once the collaborative module system is in place (see milestone I) it'll allow for more complex stuff, as you'd be joining components and moving upwards in the abstraction levels, I don't see how big companies can compete with that.
Re: Show HN: Wavepot – Digital audio workstation of the web
#137Earlier quoted context omitted.
Yes that's a good delay filter but it's also a good example why this type of user-programmable synth apparatus, which looks similar to CSound, won't catch on. There is much more going on in the typical delay sound itself than just a delayed iteration of a sample. A pure delay is boring. There is the possibility to model all kinds of analog and hardware digital delays with additional coding, but people have been doing…
There's more to digital audio processing than code? I don't get it. Once the collaborative module system is in place (see milestone I) it'll allow for more complex stuff, as you'd be joining components and moving upwards in the abstraction levels, I don't see how big companies can compete with that.
No that's not the point I was making. I was saying that to make a good delay in software it can't just be a delay. To sound good, it needs additional algorithms to carry out at least 2 other DSP functions on the return signal.