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

From CCRMA Wiki
Jump to: navigation, search
Line 10: Line 10:
 
* specifically, you might find the following useful for this project
 
* specifically, you might find the following useful for this project
 
** ''Artful Design'', p. 194
 
** ''Artful Design'', p. 194
** "[A Few Good Musical Parameters https://ccrma.stanford.edu/courses/220b-winter-2019/readings/comp-tactics.pdf]"
+
** [https://ccrma.stanford.edu/courses/220b-winter-2019/readings/comp-tactics.pdf "A Few Good Musical Parameters"]
** "[Elements for Creating Your Personal Musical Filter https://ccrma.stanford.edu/couress/220b-winter-2019/readings/musical-filters.pdf]"
+
** [https://ccrma.stanford.edu/couress/220b-winter-2019/readings/musical-filters.pdf "Elements for Creating Your Personal Musical Filter"]
  
 
=== Part 0: Reading Response ===
 
=== Part 0: Reading Response ===

Revision as of 01:09, 14 January 2019

Homework #1: "Homebrew"

Due Dates

  • milestone due 2019.1.23, Wednesday, in-class
  • final composition due 2019.1.27, Sunday, 11:59:59pm
  • in-class presentation + listening: 2019.1.28

Reading

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:
    • reflect on your process of working on this assignment
  • be sure to connect your answer to the reading, and think outside the box!
  • length: ~300 words, or 1 page

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

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
  • ChucK
  • Audacity/Ardour (for intermediate + final recording/assembly)


SoX

Example of how to change snd file sample rate:

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

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 Coursework
    • 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)

Deliverables

turn in all files by putting them in your Library/Web/220b/hw1/ directory.

  • 1) create a hw1/ directory, and put all the stuff below in there:
  • 2) all related source/sound files (.wav/.ck), as well as the final wave file
  • 3) 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
  • 4) submit all files to Canvas!
  • 5) email Ge and Orchi (ge@ccrma, orchi@ccrma) with the URL of your web page


Thanks and have fun!!!