Posts Tagged ‘ableton live’

orange clouds (no. 13)

Wednesday, January 6th, 2010

an IDM track put together on the day in mid-december when this photo was taken.

#13 Orange Clouds (7.6MB mp3)

composed with monome 64 and ableton 8 using stretta’s polygome (for max for live).

your future, mule armadillo (no. 10)

Tuesday, March 3rd, 2009

Here’s one using Stretta’s inspirational polygomé on the monome as an arpeggiator for both the bass synth and the vibraphone. 

#10 “Your Future, Mule Armadillo” (7:05, 9.7MB mp3)

monome fun, part one.

Friday, January 30th, 2009

here’s a video of me having fun with the monome. i am using a Max patch called boiinngg to trigger the drums in Ableton Live, using the Impulse plugin.

 
monome 64 + boiinngg from aleatoric on Vimeo.

can a video be “song of the week”? sure!

monome.

Thursday, January 29th, 2009

… how can something that has no capability to make sound on its own be so inspiring and useful to a musician?

above: the monome64, a totally configurable input/output light/button box that works with Max/MSP, chucK, OSC (Open Sound Control) and MIDI. 

designed and built by hand by a couple in the catskills who are committed to open-source and sustainability (as well as a refreshing minimalistic aesthetic). with a really friendly and creative user community, there are loads of free applications for it that you can edit or add to. search vimeo for “monome” on to see what i mean.  

image from monome.org.

In C.

Wednesday, January 14th, 2009

I’ve  been working on this one for awhile, but I finally got it to a point where I can post it.

It’s an adaptation of Terry Riley’s famous 1964 composition In C, which instead of having a completely static arrangement is a score sheet of 53 looping phrases that each musician plays one-by-one, at her own pace, until she feels like progressing to the next phrase.

 

 

"In C" score by Terry Riley

"In C" score by Terry Riley

 

 

A few years ago when version 6 of Ableton Live came out, I read about the new “Follow Action” feature which allows for the user to introduce a certain amount of randomness to the arrangement. I immediately thought of In C and that if I could each phrase into a separate MIDI clip, I could arrange it so that it would play much as Riley directed. The only problem was that my music-reading skills were pretty limited, my last formal music lesson having been in 4th grade. A short book called Learn To Read Music (of all things) and the Wikipedia entry on modern musical symbols got me over that hurdle.

I decided to make 8 instruments, even though Riley suggests more, because the amount of synchronicity that occurs with human players is less likely to happen with a computer. Each of the 8 computer instruments isn’t listening to the other 7, so there’s no natural temptation to fall into sync with the others. In addition there’s the pulse on the eighth notes as Riley suggests.

I have set it up so that each instrument will play each phrase 4 times, then after the 4th time there is a 1:3 (or 25%) chance it will play the next phrase; otherwise it will loop once more on the current phrase. At the end of each phrase, the computer throws the dice again. There may be better ways to experiment with the probabilities to get it to play closer to Riley’s very general direction that players not get more than 3 or 4 phrases ahead or behind of each other; the computer does not take this into account. (It would be feasible with Max but not Ableton Live).

Each time the piece is played by the computer, it should be a completely different arrangement (although computer random numbers are really pseudo-random, and I don’t know how Live picks random numbers), but contain all the patterns and polyrhythms of patterns intersecting that is the hallmark of In C.

Ableton Live playing "In C" by Terry Riley
Ableton Live playing “In C” by Terry Riley

 

Chances are good you don’t have Ableton Live 6 (or later), but if you are interested in the Live set, let me know and I will send it to you or post it here. However, below I have posted several mp3s representing performances of the piece:

Performance #1: In C #1 (23:09, 31.8MB)

Performance #2: In C #2 (19:30, 26.8MB)

UPDATE: I added one more. Skipped #3, it wasn’t interesting enough. This might be the best so far. It’s also the shortest.

Performance #4*: In C (#4) (16:35, 23.4 Mb)