From CCRMA Wiki
Revision as of 14:00, 22 February 2016 by Ge (Talk | contribs) (Created page with "= Final Project: "Computer-Mediated, Audio-visual, Composition / Live Performance = <div style="text-align: left;">1000px</div> You are to craft, com...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Final Project: "Computer-Mediated, Audio-visual, Composition / Live Performance


You are to craft, compose, and present / perform a "Computer-mediated, Audio-visual Work." The deliverables for the final project include:

  • milestone presentations
  • webpage documenting your system/performance
  • the live performance

Due date

  • milestone 0 (in-class, Tuesday, 2/23/2016): initial sketch, detailing vision, sound, music, interaction, aesthetics, music technology involved
  • milestone 1 (in-class, Tuesday, 3/1/2016): initial working system, with sound, visual, and core performance
  • milestone 2 (in-class, Tuesday, 3/8/2016): fully working system + fully fleshed out performance, complete as possible
  • final performance rehearsal: Wednesday 3/16/2015, 5:00pm-10pm (sign up for a slot)
  • all material (final project website containing code, data files, README) due Wednesday 3/16/2015, 11:59:59pm
  • final presentations / performances : Thursday 3/17/2015, 12:15pm, CCRMA Stage

Aspect 1: "Computer-Mediated"

  • must take advantage of the computer in a compelling/non-trivial way
  • for example: algorithms! sound synthesis! interactive control! generative systems!

Aspect 2: "Audio-Visual"

  • audio: use/combine techniques we covered in class (synthesis, generative, interaction) or something else; use ChucK
  • visual: interpret this as you'd like;
    • option 1: use Processing for real-time graphics/animation, coupled to audio/ChucK via OSC
    • option 2: otherwise involve visuals in a core/non-peripheral way: e.g., design gestures/movement mapped to sound

Aspect 3: "Live Performance"

  • design not only the system (sound, music, interaction, code), but ***design the performance***, being extremely mindful to have and navigate one or more aesthetics
  • aim for 3-7 minute per piece (though your fully designed live performance can be longer or shorter)
  • keep in mind setup/transition time


turn in all files by putting them in your Library/Web/220b/project/ directory, and then linking to them from your Library/Web/220b/final.html - and submitting the link to Ge and Alex

  • 1) source code + sound files for your performance
  • 2) written documentation (and any program notes / bios)
  • 3) your final.html should link to these files
  • 4) the final live performance