Jump to content

220b-winter-2021/hw0

From CCRMA Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Due Date

  • parts 1 + 2 on web portfolio + uploaded to canvas: 2021.1.19 11:59:59pm, Tuesday
  • in-class presentation of sound logo: 2021.1.15, Wednesday

Part 1: ChucKus

  • construct two chuckus, 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 chuckus should be standalone (i.e., no external audio or chuck files)
    • (thanks to Chris + kijjaz for the idea)

  • 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?
      • CCRMA?
      • yourself?
      • 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!!!

Deliverables

turn in all files by putting them in your 220b CCRMA web portfolio AND to Canvas (you will need a CCRMA account for this!)

  • 1) the reading response as a .txt, .pdf, .rtf, or .doc file (or as part of your web portfolio)
  • 2) a separate .ck file for each chucku
  • 3) title + clear description of the sound logo, who/what it's for, and how you deployed it
  • 4) your .ck file(s) for your sound logo
  • 5) an audio recording of your sound logo (hw0.wav and hw0.mp3)
  • 6) 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

Critique Doc

In class on Wednesday, January 19th; go to the Google doc...