220b-winter-2018/hw0

Homework #0: Computational (An)aesthetics

Due date: 2018.1.15 11:59:59pm, Monday.

Reading

• first, peruse CA article and this paper
  • no need to worry about the details for now, it's more important to get a sense of the ideas of cellular automata and the paper
  • in fact, try spending no more than 30 minutes total on the wikipedia article and paper combined

Specification (part 1 of 3): Response

• respond to the reading assignment in one of the following ways:
  • either a chuck program (of any 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 a response to something in the paper, or indirectly from the ideas in CA/paper/life/universe/everything

Specification (part 2 of 3): ChucKu's

• construct two chucku's, according to the following specifications:
  • like a haiku, a chucku should contain exactly 3 lines of code (each less than 80 characters)
  • each chucku should generate sound
  • 5/7/5 pattern optional, but try to make the code "pretty"
  • 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)

Musical Statement (part 3 of 3): Design Your Sound Logo

• design and create, using ChucK, your own sound logo
  • 15-30 seconds in duration
  • figure out what you are designing the logo for?
    • CCRMA?
    • yourself?
    • an organization you belong to?
    •  ???
  • make it interesting!

Note

• Have fun with it!!!

Deliverables

turn in all files by putting them in your Library/Web/220b/hw0/ directory AND to Canvas

• 1) your responses to the reading, as .ck or .txt or .jpg files
• 2) a separate .ck file for each chucku
• 3) your .ck file(s) for your sound logo
• 3) an audio recording of your sound logo (hw0.wav)
• 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