Hello,
I'm really happy to announce a beta of gibberwocky, a free, open-source live-coding plugin for Ableton Live. You can see a demo performance here:
https://vimeo.com/187702511
The video starts off slow but (arguably) gets interesting after a couple of minutes, with various polyrhythms and audio-rate modulations running.
The plugin lets you run a live-coding environment in your browser to sequence and control Live. One nice feature is the ability to easily modulate any parameter in Ableton at audio rate using gen~ graphs, and to quickly sequence changes to parameters of that graph. Other features include some fancy code annotations / visualizations to display the state of algorithms and modulations, a Score object for scheduling function executions over time, advanced functions for generating and manipulating Euclidean rhythms, and more.
The project is a joint creation with Graham Wakefield (one of the two primary authors/designers of gen~); we presented it at the International Conference of Live Coding last week. We're hoping it will help introduce musicians to the possibilities of algorithmic music and are excited to get feedback. You can find instructions for downloading the plugin and using it here:
https://github.com/charlieroberts/gibberwocky
I know there were some presentations about live coding at Loop last year, but for those unfamiliar with the performance practice: https://en.wikipedia.org/wiki/Live_coding
We're also hoping this can be more generally useful for algorithmic composition. - Charlie
announcing gibberwocky: JavaScript live-coding for Live
-
- Posts: 836
- Joined: Fri May 30, 2003 10:31 pm
- Location: rochester, ny
- Contact:
-
- Posts: 1807
- Joined: Tue Nov 16, 2004 6:27 pm
- Location: Here and There
- Contact:
Re: announcing gibberwocky: JavaScript live-coding for Live
Pretty crazy stuff.
U had me at rotate.seq
U had me at rotate.seq
-
- Posts: 836
- Joined: Fri May 30, 2003 10:31 pm
- Location: rochester, ny
- Contact:
Re: announcing gibberwocky: JavaScript live-coding for Live
Thanks!
Unfortunately on the next line I ran reverse.seq on what was almost a palindrome... not quite as impressive looking :)
Unfortunately on the next line I ran reverse.seq on what was almost a palindrome... not quite as impressive looking :)