9 ms·

Show HN: Web Audio DSP Playground

126 points by acarabott 8y ago

deleted 8y ago
[deleted]
zeth___ 8y ago
In the year 2018 of our lord requiring that a specific version of a single browser being installed to see a website should earn you a special place in hell.
- pmx 8y ago
  Its an experimental playground. I think you may be overreacting slightly.
- zeroxfe 8y ago
  AudioWorklet is part of the proposed W3C Web Audio API standard.
- mcgoooo 8y ago
  What does that comment add? Someone hacked something off a relatively fresh API and done something cool with it, the hint is in the name, hacker news.
  - zeth___ 8y ago
    Hackernews, not "install proprietary software to have a peak at a walled garden" + "news".
    - jhoh 8y ago
      So every Show HN Post hast to run on open source software or else it isn't hacker news worthy? That doesn't sound right to me.
      - anonlastname 8y ago
        That is not as far fetched as you make it seem
    - scrollaway 8y ago
      Chromium isn't proprietary software. HN is though. Your rant is misguided and pointless.
      - zeth___ 8y ago
        https://github.com/wting/hackernews https://github.com/wting/hackernews Sure.
        scrollaway 8y ago
        That's [old, outdated] source available. Not non-proprietary software. If you're going to rant, you might want to at least be accurate?
kevincennis 8y ago
Would be a cool addition to let users upload an mp3 and then act on it with the AudioWorklet to do stuff like bit crushing.
- acarabott 8y ago
  Great idea! Have implemented it, refresh and check it out.
  - detaro 8y ago
    Could you also try adding a polyfill for non-Chrome browsers? e.g. https://github.com/jariseon/audioworklet-polyfill https://github.com/jariseon/audioworklet-polyfill
    - acarabott 8y ago
      Had a crack at it but it throws NotSupportedException in both Firefox and Safari. There are also some parts that don't conform to the spec and break. Filing an issue...
droidist2 8y ago
This is pretty sweet. It'd be cool to have more examples though like square wave, triangle wave, etc. and maybe some simple effects like tremolo.
- nabla9 8y ago
  let amp = 0; const maxamp = 0.5; const freq = 880; function loop(numFrames, outL, outR, sampleRate) { const steps = sampleRate / freq; const delta = maxamp/steps; for (let i = 0; i < numFrames; i++) { amp += delta; outL[i] = amp; outR[i] = amp; if (amp > maxamp) amp = 0.0; } }
- homero 8y ago
  This would be cool http://superdupercollider.blogspot.com/2009/05/crushing-bits-for-fun-and-profit.html http://superdupercollider.blogspot.com/2009/05/crushing-bits...
jtbayly 8y ago
Only available on Chrome and only versions 66 and up.
- sgt 8y ago
  Just relaunch your browser, it should update automatically.
  - jstimpfle 8y ago
    To state the obvious, not everybody has Chrome, and not everybody has or wants the newest version. That's how it should be. By implying that it's ok to assume otherwise, you're (probably unknowingly) harming the community.
    - elvinyung 8y ago
      Dumb (but genuine) question: why is it good that not everyone wants to be in the new version?
      - jstimpfle 8y ago
        Just try not to presuppose more than is required. I might be unhappy with the newest version. Or, my device can't be updated due to technical or polital reasons. Or, the newer version does not work or is not available for my hardware or operating system. Or, I might actually be on a fork (or fake) of the software that isn't up-to-date yet. You see, there are tons of reasons...
        sgt 8y ago
        In Chrome's case, I believe it auto updates. So you don't really have a choice unless you actively try to disallow it or switch of auto-updates.
        jstimpfle 8y ago
        So I do have a choice, right? HN is a pretty technical forum -- not normally a place for ignorant-consumer type viewpoints (no offense intended). Case in point, my version of "Chrome" (chromium on Debian) does not auto-update (I think so - It's the normal way on Debian, although I don't really use chromium but firefox).
indescions_2018 8y ago
This is awesome. Sounds quite in tune at 440 Hz (A4). Could be the beginning of a DAW for Chrome ;)
- josteink 8y ago
  Why for Chrome? Why not for the web? Let’s not walk into the old MSIE trap all over again.
  - nkristoffersen 8y ago
    Need to convince the remaining browsers to implement more audio APIs.
    - josteink 8y ago
      Firefox plans to implement it last I checked[1]. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1062849 https://bugzilla.mozilla.org/show_bug.cgi?id=1062849
  - pjmlp 8y ago
    We are already there.
- 33degrees 8y ago
  There are several online DAWs: a friend works on this one https://skytracks.io/ https://skytracks.io/ and a google search will turn up many others
- droidist2 8y ago
  Requires Flash, but AudioTool has always been absolutely amazing to me: https://audiotool.com/app https://audiotool.com/app
wi24rd 8y ago
Only available in Chrome 66+, and why do you submit it twice in a week?
emilfihlman 8y ago
Getting an error of "The AudioContext was not allowed to start. It must be resume (or created) after a user gesture on the page. https://goo.gl/7K7WLu" https://goo.gl/7K7WLu".
- acarabott 8y ago
  Strange, as this is accounted for: https://github.com/acarabott/audio-dsp-playground/blob/master/livecode.js#L87 https://github.com/acarabott/audio-dsp-playground/blob/maste... OS / Chrome version? Were you clicking the start button or using the key command?
btown 8y ago
Audio Worklet https://developers.google.com/web/updates/2017/12/audio-worklet https://developers.google.com/web/updates/2017/12/audio-work... is way, way cooler than these demos imply, as it actually gives you a high-priority digital signal processing thread separate from the UI thread. And because it can benefit from WebAssembly, it's only a matter of time before the power of native audio applications is ported to the browser. This thread https://forum.juce.com/t/juce-plugins-in-webassembly/25255 https://forum.juce.com/t/juce-plugins-in-webassembly/25255 , particularly the demo here https://webaudiomodules.org/demos/wasm/dexed.html https://webaudiomodules.org/demos/wasm/dexed.html (try using the ZXCV row on your keyboard) are incredibly promising, as they're straightforward ports of real synthesizers. Other comments have mentioned that this is coming to Firefox as well; core contributors on the media team have been discussing how it's a priority as recently as two days ago: https://bugzilla.mozilla.org/show_bug.cgi?id=1062849 https://bugzilla.mozilla.org/show_bug.cgi?id=1062849 Really exciting times for the web audio space!

126 points by acarabott 8y ago

deleted 8y ago

[deleted]

In the year 2018 of our lord requiring that a specific version of a single browser being installed to see a website should earn you a special place in hell.

pmx 8y ago
Its an experimental playground. I think you may be overreacting slightly.
zeroxfe 8y ago
AudioWorklet is part of the proposed W3C Web Audio API standard.
mcgoooo 8y ago
What does that comment add? Someone hacked something off a relatively fresh API and done something cool with it, the hint is in the name, hacker news.
- zeth___ 8y ago
  Hackernews, not "install proprietary software to have a peak at a walled garden" + "news".
  - jhoh 8y ago
    So every Show HN Post hast to run on open source software or else it isn't hacker news worthy? That doesn't sound right to me.
    - anonlastname 8y ago
      That is not as far fetched as you make it seem
  - scrollaway 8y ago
    Chromium isn't proprietary software. HN is though. Your rant is misguided and pointless.
    - zeth___ 8y ago
      https://github.com/wting/hackernews https://github.com/wting/hackernews Sure.
      - scrollaway 8y ago
        That's [old, outdated] source available. Not non-proprietary software. If you're going to rant, you might want to at least be accurate?

kevincennis 8y ago

Would be a cool addition to let users upload an mp3 and then act on it with the AudioWorklet to do stuff like bit crushing.

acarabott 8y ago
Great idea! Have implemented it, refresh and check it out.
- detaro 8y ago
  Could you also try adding a polyfill for non-Chrome browsers? e.g. https://github.com/jariseon/audioworklet-polyfill https://github.com/jariseon/audioworklet-polyfill
  - acarabott 8y ago
    Had a crack at it but it throws NotSupportedException in both Firefox and Safari. There are also some parts that don't conform to the spec and break. Filing an issue...

droidist2 8y ago

This is pretty sweet. It'd be cool to have more examples though like square wave, triangle wave, etc. and maybe some simple effects like tremolo.

nabla9 8y ago
let amp = 0; const maxamp = 0.5; const freq = 880; function loop(numFrames, outL, outR, sampleRate) { const steps = sampleRate / freq; const delta = maxamp/steps; for (let i = 0; i < numFrames; i++) { amp += delta; outL[i] = amp; outR[i] = amp; if (amp > maxamp) amp = 0.0; } }
homero 8y ago
This would be cool http://superdupercollider.blogspot.com/2009/05/crushing-bits-for-fun-and-profit.html http://superdupercollider.blogspot.com/2009/05/crushing-bits...

jtbayly 8y ago

Only available on Chrome and only versions 66 and up.

sgt 8y ago
Just relaunch your browser, it should update automatically.
- jstimpfle 8y ago
  To state the obvious, not everybody has Chrome, and not everybody has or wants the newest version. That's how it should be. By implying that it's ok to assume otherwise, you're (probably unknowingly) harming the community.
  - elvinyung 8y ago
    Dumb (but genuine) question: why is it good that not everyone wants to be in the new version?
    - jstimpfle 8y ago
      Just try not to presuppose more than is required. I might be unhappy with the newest version. Or, my device can't be updated due to technical or polital reasons. Or, the newer version does not work or is not available for my hardware or operating system. Or, I might actually be on a fork (or fake) of the software that isn't up-to-date yet. You see, there are tons of reasons...
      - sgt 8y ago
        In Chrome's case, I believe it auto updates. So you don't really have a choice unless you actively try to disallow it or switch of auto-updates.
        jstimpfle 8y ago
        So I do have a choice, right? HN is a pretty technical forum -- not normally a place for ignorant-consumer type viewpoints (no offense intended). Case in point, my version of "Chrome" (chromium on Debian) does not auto-update (I think so - It's the normal way on Debian, although I don't really use chromium but firefox).

indescions_2018 8y ago

This is awesome. Sounds quite in tune at 440 Hz (A4). Could be the beginning of a DAW for Chrome ;)

josteink 8y ago
Why for Chrome? Why not for the web? Let’s not walk into the old MSIE trap all over again.
- nkristoffersen 8y ago
  Need to convince the remaining browsers to implement more audio APIs.
  - josteink 8y ago
    Firefox plans to implement it last I checked[1]. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1062849 https://bugzilla.mozilla.org/show_bug.cgi?id=1062849
- pjmlp 8y ago
  We are already there.
33degrees 8y ago
There are several online DAWs: a friend works on this one https://skytracks.io/ https://skytracks.io/ and a google search will turn up many others
droidist2 8y ago
Requires Flash, but AudioTool has always been absolutely amazing to me: https://audiotool.com/app https://audiotool.com/app

wi24rd 8y ago

Only available in Chrome 66+, and why do you submit it twice in a week?

emilfihlman 8y ago

Getting an error of "The AudioContext was not allowed to start. It must be resume (or created) after a user gesture on the page. https://goo.gl/7K7WLu" https://goo.gl/7K7WLu".

acarabott 8y ago
Strange, as this is accounted for: https://github.com/acarabott/audio-dsp-playground/blob/master/livecode.js#L87 https://github.com/acarabott/audio-dsp-playground/blob/maste... OS / Chrome version? Were you clicking the start button or using the key command?

btown 8y ago

Audio Worklet https://developers.google.com/web/updates/2017/12/audio-worklet https://developers.google.com/web/updates/2017/12/audio-work... is way, way cooler than these demos imply, as it actually gives you a high-priority digital signal processing thread separate from the UI thread. And because it can benefit from WebAssembly, it's only a matter of time before the power of native audio applications is ported to the browser. This thread https://forum.juce.com/t/juce-plugins-in-webassembly/25255 https://forum.juce.com/t/juce-plugins-in-webassembly/25255 , particularly the demo here https://webaudiomodules.org/demos/wasm/dexed.html https://webaudiomodules.org/demos/wasm/dexed.html (try using the ZXCV row on your keyboard) are incredibly promising, as they're straightforward ports of real synthesizers. Other comments have mentioned that this is coming to Firefox as well; core contributors on the media team have been discussing how it's a priority as recently as two days ago: https://bugzilla.mozilla.org/show_bug.cgi?id=1062849 https://bugzilla.mozilla.org/show_bug.cgi?id=1062849 Really exciting times for the web audio space!