Difference between revisions of "220a-fall-2007/hw6"

From CCRMA Wiki
Jump to: navigation, search
Line 5: Line 5:
  
 
<div style="text-align: left;">[[Image:OrionNebula.jpg]]</div>
 
<div style="text-align: left;">[[Image:OrionNebula.jpg]]</div>
 +
  
 
=== Tools at your disposal ===
 
=== Tools at your disposal ===
Line 10: Line 11:
 
* ChucK
 
* ChucK
 
* Audacity/Ardour (for intermediate + final recording/assembly)
 
* Audacity/Ardour (for intermediate + final recording/assembly)
* optional: keyboard, mouse, joystick, and other sensors as input device
+
* optional: keyboard, mouse, joystick, and/or other sensors as input device
  
  
Line 16: Line 17:
  
 
What to do:
 
What to do:
 +
* create one or more ChucK programs that generates music "automatically" (i.e., with minimal or no human intervention) or "semi-automatically" (i.e., with limited "high-level" human interaction)
 +
* here are some example ideas (you can use, combine, extend these, or go with something else altogether)
 +
** modeling playing style of a particular instrument, or a group of instruments ("real" and/or imagined)
 +
** model a particular compositional style (e.g., "classic" Musique Concrete, a certain approach to minimalism)
 +
** the '''o-matic''' approach: model some aspect of a composer
 +
** leverage or musically sonify a mathematical model or a computer algorithm
  
 
=== Deliverables ===
 
=== Deliverables ===

Revision as of 01:00, 21 November 2007

Homework #6: "Generative Clouds"

In this assignment, you are to create a generative musical system in ChucK, defining its parameters and creating a piece of music using the system (either automatically, or via real-time high-level input).


OrionNebula.jpg


Tools at your disposal

  • ChucK
  • Audacity/Ardour (for intermediate + final recording/assembly)
  • optional: keyboard, mouse, joystick, and/or other sensors as input device


Specification

What to do:

  • create one or more ChucK programs that generates music "automatically" (i.e., with minimal or no human intervention) or "semi-automatically" (i.e., with limited "high-level" human interaction)
  • here are some example ideas (you can use, combine, extend these, or go with something else altogether)
    • modeling playing style of a particular instrument, or a group of instruments ("real" and/or imagined)
    • model a particular compositional style (e.g., "classic" Musique Concrete, a certain approach to minimalism)
    • the o-matic approach: model some aspect of a composer
    • leverage or musically sonify a mathematical model or a computer algorithm

Deliverables

As usual, turn in all files by putting them in your Library/Web/220a/ directory.

  • 1) hw6.wav should go into the 220a directory
  • 2) create a hw6/ directory, and put all the stuff below in there:
  • 3) all related source/sound files (.wav/.ck)
  • 4) a short README text (readme.txt) file that:
    • specifies instructions on running your programs
    • describes your process/adventure, and perhaps the ideas (technical/aesthetic) behind the composition
    • gives credit, if needed, for the sounds you are using
    • describe any difficulties you encountered in the process


Thanks!!!