Difference between revisions of "220b-winter-2020/hw1"

From CCRMA Wiki
Jump to: navigation, search
 
Line 3: Line 3:
  
 
=== Due Dates ===
 
=== Due Dates ===
* milestone '''due 2020.1.22, Wednesday, in-class'''
+
* milestone '''due 2020.1.27, Monday, in-class'''
* final composition '''due 2020.1.26, Sunday, 11:59:59pm'''
+
* final composition '''due 2020.2.2, Sunday, 11:59:59pm'''
* in-class presentation + listening: '''2020.1.29'''
+
* presentation + listening: '''2020.2.3, Monday, in-class'''
  
  
 
=== Reading ===
 
=== Reading ===
* ''Artful Design'', Chapter 4, "Programmability and Sound Design" (pp. 186-205)
+
** [https://ccrma.stanford.edu/courses/220b-winter-2020/readings/comp-tactics.pdf "A Few Good Musical Parameters"]
* specifically, you might find the following useful for this project
+
** [https://ccrma.stanford.edu/courses/220b-winter-2020/readings/musical-filters.pdf "Elements for Creating Your Personal Musical Filter"]
** ''Artful Design'', p. 194 (as reference/starting point for process)
+
** [https://ccrma.stanford.edu/courses/220b-winter-2019/readings/comp-tactics.pdf "A Few Good Musical Parameters"]
+
** [https://ccrma.stanford.edu/courses/220b-winter-2019/readings/musical-filters.pdf "Elements for Creating Your Personal Musical Filter"]
+
 
+
=== Part 0: Reading Response ===
+
* respond to any single idea or aspect of the reading
+
* be sure to connect your answer to the reading
+
* length: ~300 words, or 1 page
+
  
  
Line 37: Line 29:
 
** important: they must be sounds from **EVERYDAY LIFE**
 
** important: they must be sounds from **EVERYDAY LIFE**
 
* 2) process/transform/arrange/compose.
 
* 2) process/transform/arrange/compose.
** check out the code examples from class in Coursework
+
** check out the code examples from class in Canvas
 
** figure out what you want to do, experiment, try a lot of stuff, have fun
 
** figure out what you want to do, experiment, try a lot of stuff, have fun
 
** use ChucK to process/transform the sounds
 
** use ChucK to process/transform the sounds
Line 60: Line 52:
 
=== Deliverables ===
 
=== Deliverables ===
  
'''turn in all files by putting them in your 220b web portfolio'''
+
'''turn in all files by putting them in your 220b web portfolio + submission to Canvas'''
  
* 1) reading response
+
* 1) project webpage + URL
 
* 2) title + clear description of your composition and what your inspiration was
 
* 2) title + clear description of your composition and what your inspiration was
 
* 3) all related source/sound files (.wav/.ck), as well as the final wave file
 
* 3) all related source/sound files (.wav/.ck), as well as the final wave file
Line 70: Line 62:
 
** gives credit, if needed, for the sounds you are using
 
** gives credit, if needed, for the sounds you are using
 
** describe any difficulties you encountered in the process
 
** describe any difficulties you encountered in the process
* 5) publish to web portfolio AND submit all files to Canvas!
 
  
 
Thanks and have fun!!!
 
Thanks and have fun!!!

Latest revision as of 13:48, 16 January 2020

Homework #1: "Homebrew"

Due Dates

  • milestone due 2020.1.27, Monday, in-class
  • final composition due 2020.2.2, Sunday, 11:59:59pm
  • presentation + listening: 2020.2.3, Monday, in-class


Reading


Part 1: Brewing Specifications

In this assignment, you are to record some "everyday" sounds, process/transform/arrange them, creating a composition that, in Paul Lansky's words, "views the mundane, everyday noise of daily life through a personal musical filter."

MacGyverBrew.jpg

Specification

What to do:

  • 0) spend some time planning things out in terms of the sounds you want to record, the transformations to perform, and how to put it all together.
    • As with everyday life, some things might not initially work out as planned/hoped: be resourceful (think MacGyver), and be willing to adapt.
  • 1) record a number of sounds around you
    • can be many different types of sounds, or many instances of a single type of sound (e.g., traffic)
    • note the origin of the sounds in your README
  • EDIT: also can find usable recordings, e.g., via FreeSound
    • important: they must be sounds from **EVERYDAY LIFE**
  • 2) process/transform/arrange/compose.
    • check out the code examples from class in Canvas
    • figure out what you want to do, experiment, try a lot of stuff, have fun
    • use ChucK to process/transform the sounds
    • the bulk of the arranging should be done in ChucK, with intermediate editing and late-stage assembly in Audacity
    • if helpful, record and edit intermediate sound clips from ChucK into Audacity (via Jack)


Tools at your disposal

(note: these are the only tools you are to use (but you don't have to use all of them) - you'll need to obtain permission to use other software or sound samples you didn't record)

  • any microphone (phone, laptop, hydrophone, studio, etc.) | something to record into (e.g., laptop/desktop)
  • EDIT: also can find usable recordings **of everyday sounds**, e.g., via FreeSound (please credit the source)
  • ChucK
  • Audacity/Ardour (for intermediate + final recording/assembly)

SoX

Example of how to change snd file sample rate:

[cmn##] sox <inputfilename> -r 44000 <outputfilename>


Deliverables

turn in all files by putting them in your 220b web portfolio + submission to Canvas

  • 1) project webpage + URL
  • 2) title + clear description of your composition and what your inspiration was
  • 3) all related source/sound files (.wav/.ck), as well as the final wave file
  • 4) a short README text (readme.txt) file that:
    • specifies instructions on running your programs
    • describes your process/adventure, and perhaps the ideas (technical/aesthetic) behind the composition
    • gives credit, if needed, for the sounds you are using
    • describe any difficulties you encountered in the process

Thanks and have fun!!!