Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Web DSP audio editor

dsp.audio

Post reply on HN
Print view View original

21–30 of 49 posts

Re: Show HN: Web DSP audio editor

#21

Post by dkersten »

lloeki wrote: post #20
janesconference wrote: post #19

Earlier quoted context omitted.

As soon as browser support the standard, the message will be shown less and less. Chrome was an early adopter, but Audio Worklets are part of a W3C working draft, which is the de facto standard for web audio: https://www.w3.org/TR/webaudio/

Qualifying browsers that don't follow an early adopter in implementing a working draft of being "old" is kind of odd and disparaging. A simple message like "Sadly your browser does not seem to support spec foo yet, but you can try one of those: browser X v>42, Y, Z".

There’s an “or” in that sentence: “old or unsupported browser”

Re: Show HN: Web DSP audio editor

#22

Post by te_chris »

lloeki wrote: post #20
janesconference wrote: post #19

Earlier quoted context omitted.

As soon as browser support the standard, the message will be shown less and less. Chrome was an early adopter, but Audio Worklets are part of a W3C working draft, which is the de facto standard for web audio: https://www.w3.org/TR/webaudio/

Qualifying browsers that don't follow an early adopter in implementing a working draft of being "old" is kind of odd and disparaging. A simple message like "Sadly your browser does not seem to support spec foo yet, but you can try one of those: browser X v>42, Y, Z".

Nitpicking cool projects is also pretty disparaging.

Re: Show HN: Web DSP audio editor

#23

Post by tomduncalf »

janesconference wrote: post #15
mmjaa wrote: post #11

Nice. The only thing I don't like about it is that its browser based, because - as a musician with a room full of hardware - its hard to get over the conclusion that browser-based music tools are simply not ready for production - i.e. I would never use this on stage or in the studio. Cute experiment though...

I understand your point of view, although there are people I know who managed to run Web Audio API plugins as VSTs :) This particular app is meant more as a playground / sketch / sharing tool for DSP techniques, and imho it makes sense for it to be on the most immediately accessible platform, the Web. However, it's possible to add Faust or C support to it in the future (using WebAssembly), a feature which will allow…

> run Web Audio API plugins as VSTs

Nice, I have thought about this before! Got a link?

Re: Show HN: Web DSP audio editor

#24

Post by stuntkite »

janesconference wrote: post #6
WhyDoPeople wrote: post #4

Earlier quoted context omitted.

Sorry for the dumb question as I'm not in the field, but is this meant for actual midi/audio in? I tried clicking the keys on the midi to no avail, so I would assume I would use this with an actual midi (or midi file)?

Audio in is supported - it just uses your computer's audio in. Just press on the "Line In" checkbox on the left to allow your browser to access your audio. Alternatively, you can send a pre-set sample to the worklet by selecting it from the dropdown menu and pressing "Play" Midi in is not supported yet, i.e. you can't press a key on your connected MIDI keyboard to send a MIDI message to the worklet yet. You can simul…

Have you considered using Open Sound Control[0]? There is a nice JS package for it. I've put together a couple demo web apps using OSC as both client and server. Bonuses include that you get midi with it, it creates RESTful 2 way interfaces for your endpoints, can be shared over the internet (WebRTC), and it's universally easy to hook to other stuff! Also there is a FANTASTIC customizable interface app for iOS and Android called TouchOSC[1] that only costs $5. I use it for music and robotics.

[0] https://github.com/colinbdclark/osc.js/

[1] https://hexler.net/software/touchosc

BONUS OSC STUFF:

* https://github.com/sebpiq/rhizome

* https://github.com/attwad/python-osc

* https://github.com/thomasfredericks/UnityOSC

* https://github.com/automata/osc-web

* https://github.com/mhroth/tinyosc

Re: Show HN: Web DSP audio editor

#25

Post by giancarlostoro »

dkersten wrote: post #21
lloeki wrote: post #20

Earlier quoted context omitted.

Qualifying browsers that don't follow an early adopter in implementing a working draft of being "old" is kind of odd and disparaging. A simple message like "Sadly your browser does not seem to support spec foo yet, but you can try one of those: browser X v>42, Y, Z".

There’s an “or” in that sentence: “old or unsupported browser”

The term unsupported browser sounds like it's intentionally only for Chrome.

Re: Show HN: Web DSP audio editor

#26

Post by snarfy »

janesconference wrote: post #15
mmjaa wrote: post #11

Nice. The only thing I don't like about it is that its browser based, because - as a musician with a room full of hardware - its hard to get over the conclusion that browser-based music tools are simply not ready for production - i.e. I would never use this on stage or in the studio. Cute experiment though...

I understand your point of view, although there are people I know who managed to run Web Audio API plugins as VSTs :) This particular app is meant more as a playground / sketch / sharing tool for DSP techniques, and imho it makes sense for it to be on the most immediately accessible platform, the Web. However, it's possible to add Faust or C support to it in the future (using WebAssembly), a feature which will allow…

I think this is a good way to look at it. It reminds me of shadertoy except for dsp audio.

It could be compiled with a webassembly backend and loaded, but... you could almost copy/paste the process() js function into c++ and it would compile, almost.

Re: Show HN: Web DSP audio editor

#27

Post by janesconference »

giancarlostoro wrote: post #25
dkersten wrote: post #21

Earlier quoted context omitted.

There’s an “or” in that sentence: “old or unsupported browser”

The term unsupported browser sounds like it's intentionally only for Chrome.

That's true, that's inaccurate. I'll change the message with the next deploy.

Re: Show HN: Web DSP audio editor

#28

Post by janesconference »

lloeki wrote: post #20
janesconference wrote: post #19

Earlier quoted context omitted.

As soon as browser support the standard, the message will be shown less and less. Chrome was an early adopter, but Audio Worklets are part of a W3C working draft, which is the de facto standard for web audio: https://www.w3.org/TR/webaudio/

Qualifying browsers that don't follow an early adopter in implementing a working draft of being "old" is kind of odd and disparaging. A simple message like "Sadly your browser does not seem to support spec foo yet, but you can try one of those: browser X v>42, Y, Z".

Sorry if I hurt any browser's sensibility. Hope no browser was offended by my app :)

However, I didn't refer to "browsers that don't follow an early adopter in implementing a working draft" as "old", though; if you read the compatibility message carefully, you'll find I referred to them as "unsupported" (which might be a bit inexact but not disparaging).

Non-evergreen browsers, instead, are correctly referred to as "old", because they are.

Re: Show HN: Web DSP audio editor

#30

Post by janesconference »

tomduncalf wrote: post #23
janesconference wrote: post #15

Earlier quoted context omitted.

I understand your point of view, although there are people I know who managed to run Web Audio API plugins as VSTs :) This particular app is meant more as a playground / sketch / sharing tool for DSP techniques, and imho it makes sense for it to be on the most immediately accessible platform, the Web. However, it's possible to add Faust or C support to it in the future (using WebAssembly), a feature which will allow…

> run Web Audio API plugins as VSTs Nice, I have thought about this before! Got a link?

I don't have a public link to the method they used, but I heard of this technique on the Web Audio Slack channel, which you can join here: https://web-audio.slack.com/. Basically, as I understood it, they found a way to wrap the Chrome runtime in a VST plugin and load it in a DAW. I guess the process can be optimised, but I'm no browser internals expert. The community is quite friendly, so if you're interested you could join it and ask, I'm sure they'll be happy to share with you.
Post reply on HN