171 karma · joined November 21, 2012
The blog is a WIP, I would like to blog about Audio DSP with maybe code examples hosted on the worklet editor. I just need to find the time.
My GitHub repo is cristiano.belloni, but I don't really use it - I normally use GitLab these days, and most of my repos are private for one reason or another. I'll probably open some of them, but only if I know there is interest and I can maintain them properly.
For anyone interested on the stack, the visual part is React / Redux SPA. I use Firebase's Firestore as a DB (I wanted to try it and so far it's really cool) and Google Cloud Functions for the APIs. The repo is hosted on Gitlab and is a Lerna monorepo, which is amazing.
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.
> — Please note that the app runs only on Chrome > v66, for
> now, because Chrome is the only browser implementing the
> Audio Worklet[1] spec. Other browser will follow suit
> (hopefully) soon
[1] https://developers.google.com/web/updates/2017/12/audio-work...
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 exporting your snippets directly to executable / VST.
These are a bunch of demos: https://googlechromelabs.github.io/web-audio-samples/audio-w...
This application allows you to write, test and save / share them. The idea is to have an online playground to share DSP code, like a sort of JSFiddle, but for audio.
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 simulate it with the keyboard on the left. Quoting the Help page (accessible with the "?" button on the top right):
"The MIDI IN keyboard will send MIDI messages to the worklet's MessagePort. Messages are objects of the form {type: ['noteon' | 'noteoff'], value: { note, octave, midi, frequency } }"
Using physical MIDI controls will be supported in future releases, though.
— Please note that the app runs only on Chrome > v66, for now, because Chrome is the only browser implementing the Audio Worklet[1] spec. Other browser will follow suit (hopefully) soon
[1] https://developers.google.com/web/updates/2017/12/audio-work...
Please feel free to use the tool to prototype or show your creations around.
— Please note that the app runs only on Chrome > v66, for now, because Chrome is the only browser implementing the Audio Worklet[1] spec. Other browser will follow suit (hopefully) soon
[1] https://developers.google.com/web/updates/2017/12/audio-work...
Don't forget unhappy paths both in the UI wireframes and UX interactions, because they'll absorb most of the development process (sad but true).
Ensure you have a contract draft ready for the web dev to sign. Ensure you're prepared to pay in line with the current industry rates.