Basic Electroacoustics II: Music-Making Systems

Music G6602Y
TueThu 3:10-5:00pm
Spring 2004
Professor: Douglas Repetto [douglas at music columbia edu]
TA: James Fei [jamesfei at music columbia edu]
Our Motto: "Why, then how."
syllabus | lectures




January 22

What is an algorithm?

What is an algorithm, a system, or a process? And what do they have to do with making music and art? There's a lot to talk about here! In fact, we're going to spend the entire term talking about these questions.

We're going to start off with some quick examples of algorithmic/process/system-based work:

Josh Nimoy: balldroppings (interactive sound application, physical simulation)
Larry Polansky: Four Voice Canons (a compositional strategy)
Ross Craig: Barbie's Phone Canon (a realization of Polansky's FVC idea)
Douglas Repetto: SineClock (software sound installation/physical sound sculpture, sonification)
Jason Freeman: N.A.G. (Network Auralization for Gnutella) (MP3 search engine + auto audio collage maker)
Robert Ashley: String Quartet Describing the Motion of Large, Real Bodies (unpredictable human/electronic hybrid system)
Dick Raaijmakers: Canons
Alvin Lucier: Music on a Long Thin Wire (physical system)
Steve Reich: Come Out (tape phasing as a compositional strategy)

As the examples above demonstrate, working with algorithms/systems/processes doesn't imply any particular aesthetic or stylistic bias. The only thing these pieces have in common is their reliance, to varying degrees, on an algorithm, system, or process.

What's the difference between an algorithm, a system, and a process? These are all somewhat interchangable, although here's my informal scheme: an algorithm is a low level, highly specified set of instructions. Computer code tends to be algorithmic. A system is a higher level entity that works as a unit, but that is probably made up of a number of lower level units, or algorithms. A process is a somewhat simple, informal, and usually repetitious algorithm, such as some action done by a human using a written set of instructions.


Below is an unordered list of questions and comments; we'll use these in class to drive the discussion as we talk about algorithms, systems, and processes, and how and why they're often used in making electronic art.


What is an algorithm/system/process? *****

If a recipe is an algorithm, what are ingredients? *

Is a musical score an algorithm?

Is a map an algorithm?

How does the idea of data reduction fit in to all of this?

How is a loaf of bread different from the instructions for making a loaf of bread?

Who is the good cook? The person who wrote the recipe, or the person who follows it?

What about if a computer bakes your bread or plays your score? *

What if it's not played at all? What about an impossible algorithm? *

Sometimes you know the result of a system before running it, sometimes you don't.

Some systems give the same output every time, others don't.

Some systems finish running, others don't.

Some systems are used to create other algorithms.

What's a deterministic algorithm?

Are we all just lazy?

How does entropy figure in?

What's creative about random numbers? What if they're not even really random? *

What does non-linear mean?

Nature loves algorithms. *

Some people argue that nature is an algorithm. *

What does it mean to "discover" an algorithm? *

If you make art using algorithms, does your audience need to know that?

Do they need to understand the specifics of the algorithm?

Do you need to understand the specifics of the algorithm? *

What does it mean if you're not sure whether a work is algorithmic or not? Does the meaning of the work change?

You make a non-algorithmic piece and someone comes up to you and says, "What's your algorithm?" *

"Generative Art" *

"Algorithmic Art"

Is all "Computer Music" algorithmic?

"Through-composed."

Is it fair to tweak the output of a process in a piece? Do you have to admit it?

Christian Wolff's text pieces. *

Yoko Ono's instruction paintings. *

"Generative Psychogeography." *

The ubiquitous "Game of Life." *

"Serial Music."

What's an "interactive system?"

What's a system with no inputs? *

What's an system with no outputs?

Algorithms make the infinite seem close.

Or really far away.

The ubiquitous "Monkeys Typing Shakespeare." *

Algorithms as time savers.

Algorithms as creative crutches.

Happy Chinese New Year. *

Algorithms can be used at many different levels, from generating sound samples to creating large-scale forms.

What's the interesting part? The final product? Several iterations of the algorithm? The process itself?

Who wants to watch a wheel turn?

Who wants to read a computer-generated poem? *

What's the difference between the output from a really complex, difficult to understand algorithm and a bunch of random gunk?

If we can't perceive it, does it matter? *

What's the difference between pressing Play on a CD player and pressing Play on an algorithmic composition?

Can an algorithm tell a story?

Can a system be expressive?

Can a process be a work of art?

Larry Polansky's Four Voice Cannons. *

Alvin Lucier's I Am Sitting in a Room. *

Sol LeWitt. *

The proof is in the pudding.


Your assignment:

Pick one of the questions/comments above. Do some thinking. Do some research. Tell us about it.

(10 minute presentation)