Difference between revisions of "220b-winter-2008/hw1"

From CCRMA Wiki
Jump to: navigation, search
Line 1: Line 1:
= Homework #1: Timbre Studies =
+
= Homework #1: Timbre-scapes =
  
 
Due date: 2008.1.30 11:59:59pm (or thereabout), Wednesday.
 
Due date: 2008.1.30 11:59:59pm (or thereabout), Wednesday.
Line 10: Line 10:
  
  
=== Specification (part 1 of 2): Crafting Timbre's with FM ===
+
=== Specification (part 1 of 3): Crafting Timbre's with FM ===
 +
* using FM synthesis in ChucK, create the following:
 +
** 3 different "static" timbres
 +
*** building blocks: oscillators, filters, etc.
 +
*** experiment with various parameters such as carrier frequency, modulator frequency, index of modulation, etc.
 +
** 3 time-varying timbres
 +
*** building blocks: oscillators, filters, time-based control code
 +
*** can be a "drone" (but doesn't have to be)
 +
*** the time-varying process(s) should be somehow coupled to one or more of the FM/filter parameters
 +
** next, take a timbre from above, and apply an ADSR envelope to "carve" out an attack, decay, sustain, and release
 +
*** test this by making some bleeps and bloops
  
  
=== Specification (part 2 of 2): Musical Statement ===
+
=== Specification (part 2 of 3): Algorithmic Sectionals ===
* construct two chucku's, according to the following specifications:
+
 
** like a [http://en.wikipedia.org/wiki/Haiku haiku], a ''chucku'' should contain exactly 3 lines of code (each less than 80 characters)
+
 
** each chucku should generate sound
+
=== Specification (part 3 of 3): Brainstormin' ===
** 5/7/5 pattern optional, but try to make the code "pretty"
+
* without writing any code, imagine and think through how you might map a cellular automata to:
** check out [http://electro-music.com/forum/topic-13512.html one line chuck crazy] to see similarly compact examples
+
** create/help create a piece of music
** the chucku's should be standalone (i.e., no external audio or chuck files)
+
** control timbre
** (thanks to Chris + kijjaz for the idea)
+
* no right/wrong answers - but try to think it through
 +
* convey what you come up with in word, diagrams, etc.
  
  

Revision as of 18:23, 20 January 2008

Homework #1: Timbre-scapes

Due date: 2008.1.30 11:59:59pm (or thereabout), Wednesday.

Reading

  • Real-Sound-Synthesis:
    • chapter 3
    • sections 4.0, 4.1, and 4.2
    • chapter 10


Specification (part 1 of 3): Crafting Timbre's with FM

  • using FM synthesis in ChucK, create the following:
    • 3 different "static" timbres
      • building blocks: oscillators, filters, etc.
      • experiment with various parameters such as carrier frequency, modulator frequency, index of modulation, etc.
    • 3 time-varying timbres
      • building blocks: oscillators, filters, time-based control code
      • can be a "drone" (but doesn't have to be)
      • the time-varying process(s) should be somehow coupled to one or more of the FM/filter parameters
    • next, take a timbre from above, and apply an ADSR envelope to "carve" out an attack, decay, sustain, and release
      • test this by making some bleeps and bloops


Specification (part 2 of 3): Algorithmic Sectionals

Specification (part 3 of 3): Brainstormin'

  • without writing any code, imagine and think through how you might map a cellular automata to:
    • create/help create a piece of music
    • control timbre
  • no right/wrong answers - but try to think it through
  • convey what you come up with in word, diagrams, etc.


Note

  • Have fun with it!!!


Deliverables

turn in all files by putting them in your Library/Web/220b/hw1/ directory, and then linking to them from your Library/Web/220b/hw1.html

  • 1)
  • 4) a short README text (readme.txt) file that:
    • conveys your ideas/comments in constructing each program
    • contains instructions on running your programs
    • describes any difficulties you encountered in the process