This is just an outline off the top of my head of all the cool stuff that happened at the 1st WAC at IRCAM and Mozilla Paris.
- Distributed performance
-
- talk / demo
- Lissijous –> distributed
- Technical questions
- Compositional questsion—maybe latency is something to be embraced by the composer.
-
- how much control to give the audience, when they are performers, how much room to allow for improvisation?
- Design questions:
-
- phone as an interface – do you want people to interact with each other?
- Port DSP to Web
-
- 3D audio custom HRTF (IRCAM)
- Meyda – audio feature extraction library – inspired by the Yaffa library (Python / C++)
-
- using jsfft library to do fft themselves
- various environments for running / optimizing C++ code
-
- asm.js (Jari Kleimola DAW plugins for web browsers)
- AudioWorker will make this all much more accessible and standardized.
- Port frameworks to the web
-
- Csound and Faust with emscripten and potable data client
- Tone.JS inspired by Ableton, Max/MSP etc but built with the web in mind
- WebPD – two separate projects
- Recently converted to Web Audio:
-
- Earsketch – more powerful than Reaper, transitioned 1 year ago
-
- reference DAW paradigm while learning Python and JS
- MOOC
- Why is web better? No installation hurdles. Essential for education. Plus, accessible from anywhere!
- Sonoport
- Cool Hacks to get things to work:
-
- Sonoport
- Tone.js
- Chris Lowis’ keynote on the original of computer music at Bell Labs half a century ago, really hasn’t evolved that much. Simple principles:
-
- flexible building blocks
- allow extension
- separate orchestra from score
- Q: What about the web makes it different?
-
- challenges described by Paul Adenot
- Modular resources
-
- IRCAM’s WAVES – common.js
- BRAID – Web Audio UI builder, uses canvas.
-
- idea: share instruments via central database
- modular with npm
- Open Music – not talked about