From CCRMA Wiki
Homework #0: ChucKu's and Sound Logos
- parts 1 + 2 on web portfolio + uploaded to canvas: 2019.1.13 11:59:59pm, Sunday
- in-class presentation of sound logo: 2019.1.14, Monday
- Artful Design, Prelude + Chapter 4, "Programmability and Sound Design" (pp. 160-185)
Part 0: Reading Response
- draw on the discussion of computer music in Chapter 4 analyze some aspect of your own creative or academic work. you can respond to whatever aspect you like, but here are a couple of example prompts:
- discuss how computers contribute to your work and why they're necessary
- compare the way you're designing your work to the way ChucK is designed, especially with respect to control parameters like time, pitch/frequency, and so on
- be sure to connect your answer to the reading, and think outside the box!
- length: ~300 words, or 1 page
Part 1: 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)
Part 2: Design Your Sound Logo
- full instructions as Design Etude #4 from Artful Design
- design and create, using ChucK, your own sound logo
- 20-30 seconds in duration
- figure out what you are designing the logo for?
- an organization you belong to?
- have a narrative (e.g., beginning, middle, end—or...)!
- make it interesting!
- experiment with have MANY INSTANCES (e.g., like saw voices in the THX Deep Note) that are both independently controlled but also obey an overall plan!
- have fun with it!!!
turn in all files by putting them in your 220b CCRMA web portfolio AND to Canvas
- 1) the reading response as a .txt, .pdf, .rtf, or .doc file
- 2) a separate .ck file for each chucku
- 3) your .ck file(s) for your sound logo
- 4) an audio recording of your sound logo (hw0.wav and hw0.mp3)
- 5) 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