Difference between revisions of "220b-winter-2008/hw0"
From CCRMA Wiki
| Line 1: | Line 1: | ||
= Homework #0: Computational (An)aesthetics = | = Homework #0: Computational (An)aesthetics = | ||
| − | === Specification === | + | === Reading === |
| + | * first, read [http://ccrma.stanford.edu/courses/220b-winter-2008/readings/cslifeuniverseeverything.pdf this paper] | ||
| + | ** no need to worry about the details for now, just get a sense of what it's about, and think about the ideas | ||
| + | ** in fact, try spending no more than 20 minutes total on the paper | ||
| + | |||
| + | |||
| + | === Specification (part 1 of 2) === | ||
| + | * respond to the reading assignment in '''one''' of the following ways: | ||
| + | *** '''either''' a chuck program (of any desired length) that makes sound | ||
| + | *** '''or''' a brief written/textual response (can be as short as a paragraph, or as long as uh two paragraphs, or more) | ||
| + | *** '''or''' a drawing / image, or something else graphical | ||
| + | *** '''or''' a combination of above | ||
| + | * this can be to something directly in the paper, or indirectly from the ideas | ||
| + | |||
| + | |||
| + | === Specification (part 2 of 2) === | ||
* construct two chucku's, according to the following specifications | * 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 | ** like a [http://en.wikipedia.org/wiki/Haiku haiku], a ''chucku'' should contain exactly 3 lines of code | ||
| Line 8: | Line 23: | ||
** the chucku's should be standalone (i.e., no external audio or chuck files) | ** the chucku's should be standalone (i.e., no external audio or chuck files) | ||
** (thanks to Chris + kijjaz for the idea) | ** (thanks to Chris + kijjaz for the idea) | ||
| + | |||
=== Deliverables === | === Deliverables === | ||
| Line 13: | Line 29: | ||
'''turn in all files by putting them in your Library/Web/220b/hw0/ directory.''' | '''turn in all files by putting them in your Library/Web/220b/hw0/ directory.''' | ||
| − | * 1) a separate .ck file for each chucku | + | * 1) your responses to the reading, as .ck or .txt or .jpg files |
| − | * | + | * 2) a separate .ck file for each chucku |
| − | + | * 3) an audio recording of one or more of the programs (hw0.wav) | |
* 4) a short README text ('''readme.txt''') file that: | * 4) a short README text ('''readme.txt''') file that: | ||
** explains your ideas in constructing each program | ** explains your ideas in constructing each program | ||
Revision as of 17:49, 12 January 2008
Contents
Homework #0: Computational (An)aesthetics
Reading
- first, read this paper
- no need to worry about the details for now, just get a sense of what it's about, and think about the ideas
- in fact, try spending no more than 20 minutes total on the paper
Specification (part 1 of 2)
- respond to the reading assignment in one of the following ways:
- either a chuck program (of any desired length) that makes sound
- or a brief written/textual response (can be as short as a paragraph, or as long as uh two paragraphs, or more)
- or a drawing / image, or something else graphical
- or a combination of above
- this can be to something directly in the paper, or indirectly from the ideas
Specification (part 2 of 2)
- construct two chucku's, according to the following specifications
- like a haiku, a chucku should contain exactly 3 lines of code
- each chucku should generate sound
- check out one line chuck crazy to see similarly compact examples
- the chucku's should be standalone (i.e., no external audio or chuck files)
- (thanks to Chris + kijjaz for the idea)
Deliverables
turn in all files by putting them in your Library/Web/220b/hw0/ directory.
- 1) your responses to the reading, as .ck or .txt or .jpg files
- 2) a separate .ck file for each chucku
- 3) an audio recording of one or more of the programs (hw0.wav)
- 4) a short README text (readme.txt) file that:
- explains your ideas in constructing each program
- contains instructions on running your programs
- any comments about each program / musical statement
- describe any difficulties you encountered in the process
Thanks!!!
