Difference between revisions of "220b-winter-2008/hw3"
From CCRMA Wiki
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | = Homework #3: Computer-Mediated Live Performance = | + | = Homework #3 -> Final Project: Computer-Mediated Live Performance = |
<div style="text-align: left;">[[Image:beam-us-up.jpg]]</div> | <div style="text-align: left;">[[Image:beam-us-up.jpg]]</div> | ||
| Line 5: | Line 5: | ||
== Due date == | == Due date == | ||
| − | * (files + documentation) | + | * (files + documentation) Extended! (TBA) |
| − | * (live performance) | + | * (live performance) Extended! (TBA) |
| Line 16: | Line 16: | ||
== Part 1: Create a Live Performance == | == 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: | * create a computer-mediated live performance, using any combination of the tools we've covered in 220a/b: | ||
** ChucK | ** ChucK | ||
| Line 35: | Line 36: | ||
== Part 2: Perform It == | == Part 2: Perform It == | ||
| − | * 220b recital: | + | * 220b recital: Wednesday, March 19th at 8pm on CCRMA Stage |
| − | * dress | + | * dress rehearsals: Saturday, March 15 from 11am-? and Tuesday, March 18 from 5pm-? on CCRMA Stage |
* aim for 3-7 minute per piece (though your fully designed live performance can be longer) | * aim for 3-7 minute per piece (though your fully designed live performance can be longer) | ||
* keep in mind setup/transition time | * keep in mind setup/transition time | ||
| − | |||
== A Few Examples as Starting Points == | == A Few Examples as Starting Points == | ||
| Line 51: | Line 51: | ||
== Deliverables == | == Deliverables == | ||
| − | + | '''turn in all files by putting them in your Library/Web/220b/hw3/ directory, and then linking to them from | |
| − | '''turn in all files by putting them in your Library/Web/220b/ | + | your Library/Web/220b/hw3.html''' |
| − | your Library/Web/220b/ | + | |
* 1) all source code + sound files for your performance | * 1) all source code + sound files for your performance | ||
* 2) written documentation + program notes / bios | * 2) written documentation + program notes / bios | ||
* 3) your hw3.html should link to these files | * 3) your hw3.html should link to these files | ||
| − | * 4) a live performance of the piece | + | * 4) a live performance of the piece |
Latest revision as of 21:00, 11 March 2008
Contents
Homework #3 -> Final Project: Computer-Mediated Live Performance
...
Due date
- (files + documentation) Extended! (TBA)
- (live performance) Extended! (TBA)
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?
- create documentation for your performance
- program notes (if any)
- README
Part 2: Perform It
- 220b recital: Wednesday, March 19th at 8pm on CCRMA Stage
- dress rehearsals: Saturday, March 15 from 11am-? and Tuesday, March 18 from 5pm-? 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
