220b-winter-2009/hw3

From CCRMA Wiki

Revision as of 21:51, 26 February 2009 by Jakesb (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Final Project: Computer-Mediated Live Performance

Image:beam-us-up.jpg

...

Due date

  • part 1: (instrument + files + documentation) : Saturday 3/14, 11:59:59pm
  • part 2: (live performance) : Tuesday 3/17, 7pm, CCRMA Stage (with rehearsal on Sunday 3/15, starting at noon)

Collaboration

  • you have the option of officially working in a duo
  • you can still go "maverick" (i.e., solo)
  • try to pair up with someone with whom you haven't played together (a lot) before


Part 1: Create a Live Performance

  • theme: "Computational Music Universe"
  • create a computer-mediated live performance, using any combination of the tools we've covered in 220a/b:
    • ChucK
    • pd
    • even TAPESTREA, calories, and/or Audacity (may need to think harder about how to use these in a meaningful way for live performance)
  • in your design of the piece, pay attention to the following questions:
    • what is the difference between a live computer music performance vs. non-live media? (what does it mean to perform live with a computer?)
    • what is to be the musical instrument here?
    • how to musically engage the performer(s)?
    • how to expressively engage the audience?
    • at what levels (of expression, abstraction, representation) does the performance interact with the computer?
    • what is the computer:human involvement ratio?
    • sonic/visual/performative aesthetic?
    • how much, if any, improvisation? score?
  • deliverables:
    • all code, sound files, instructions
    • create documentation for your performance: program notes (if any)
    • README


Part 2: Perform It

  • 220b Winter 2009 performance: Tuesday, March 17th at 7pm on CCRMA Stage
  • dress rehearsals: Sunday, March 15 from noon-??? and Monday, March 16 from noon-??? on CCRMA Stage
  • aim for 3-7 minute per piece (though your fully designed live performance can be longer)
  • keep in mind setup/transition time

A Few Examples as Starting Points

(experiment! definitely not limited to these)

  • live coding
  • laptop as physical instrument (see http://smelt.cs.princeton.edu/)
  • commodity and/or custom computer music controllers
  • live processing/sampling (computer + other instrument, e.g., voice, flute, saxophone, bass guitar, tuba, paper, etc.)
  • sound + image/graphics/video (what is the interaction thereof?)


Deliverables

turn in all files by putting them in your Library/Web/220b/hw3/ directory, and then linking to them from your Library/Web/220b/hw3.html

  • 1) all source code + sound files for your performance
  • 2) written documentation + program notes / bios
  • 3) your hw3.html should link to these files
  • 4) a live performance of the piece
Personal tools