Difference between revisions of "220b-winter-2019/hw0"

From CCRMA Wiki
Jump to: navigation, search
(Homework #0: ChucKu's and Sound Logos)
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= Homework #0: ChucKu's and Sound Logos =
 
= Homework #0: ChucKu's and Sound Logos =
  
Due date: 2019.1.13 11:59:59pm, Sunday.
+
=== Due Date ===
 +
* parts 0 + 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
  
 
=== Reading ===
 
=== Reading ===
* Read ''Artful Design''
+
* ''Artful Design'', Prelude + Chapter 4, "Programmability and Sound Design" (pp. 160-185)
** 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 to the extent 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 (either on your webpage or as PDF)
  
 
=== Part 1: ChucKu's ===
 
=== Part 1: ChucKu's ===
Line 17: 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)
 
  
 
=== Part 2: Design Your Sound Logo ===
 
=== Part 2: Design Your Sound Logo ===
Line 37: Line 42:
 
'''turn in all files by putting them in your 220b CCRMA web portfolio AND to Canvas'''
 
'''turn in all files by putting them in your 220b CCRMA web portfolio AND to Canvas'''
  
* 1) a separate .ck file for each chucku
+
* 1) the reading response as a .txt, .pdf, .rtf, or .doc file (or as part of your web portfolio)
* 2) your .ck file(s) for your sound logo
+
* 2) a separate .ck file for each chucku
* 3) an audio recording of your sound logo (hw0.wav and hw0.mp3)  
+
* 3) title + clear description of the sound logo, who/what it's for, and how you deployed it
* 4) a short README text ('''readme.txt''') file that:
+
* 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  
 
** conveys your ideas/comments in constructing each program  
 
** contains instructions on running your programs
 
** contains instructions on running your programs
 
** describes any difficulties you encountered in the process
 
** describes any difficulties you encountered in the process
 +
 +
=== Critique Doc ===
 +
 +
In class on Wednesday, January 16th, go to the Google doc: [https://docs.google.com/document/d/1Bd-n1mhwmyj9h4QVFY-f9_sTLaqOxeLUP_-l11vRbK8/edit?usp=sharing]

Latest revision as of 12:48, 16 January 2019

Homework #0: ChucKu's and Sound Logos

Due Date

  • parts 0 + 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

Reading

  • 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 to the extent 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 (either on your webpage or as PDF)

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)

  • 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

  • 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 16th, go to the Google doc: [1]