Jump to content

220b-winter-2015/final: Difference between revisions

From CCRMA Wiki
Ge (talk | contribs)
No edit summary
Ge (talk | contribs)
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Final Project: "Computer-Mediated, Audio-visual, Live Performance =
= Final Project: "Computer-Mediated, Audio-visual, Live Performance =
<div style="text-align: left;">[[Image:Greenwave.jpg|1000px]]</div>
You are to craft, compose, and perform a "Computer-mediated, Audio-visual, Live Performance."  The deliverables for the final project include:
* milestone presentations
* webpage documenting your system/performance
* the live performance


== Due date ==
== Due date ==
* milestone 0 (in-class, Tuesday, 2/24/2015): initial sketch, detailing vision, sound, music, interaction, aesthetics, music technology involved
* milestone 1 (in-class, Tuesday, 3/3/2015): initial working system, with sound, visual, and core performance
* milestone 2 (in-class, Tuesday, 3/10/2015): fully working system + fully fleshed out performance, complete as possible
* final performance rehearsal: Wednesday 3/18/2015, 6-10pm (sign up for a slot)
* final performance rehearsal: Wednesday 3/18/2015, 6-10pm (sign up for a slot)
* final presentations / performances : Thursday 3/19/2015, 3:30pm, CCRMA Stage
* all material (final project website containing code, data files, README) due Wednesday 3/18/2015, 11:59:59pm
* all material (final project website containing code, data files, README) due ***before*** performance starts!
* '''final presentations / performances : Thursday 3/19/2015, 3:30pm, CCRMA Stage'''


   
   
== Part 1: "Computer-Mediated" ==
=== Aspect 1: "Computer-Mediated" ===
* must take advantage of the computer in a compelling/non-trivial way
* must take advantage of the computer in a compelling/non-trivial way
* for example: algorithms!  sound synthesis!  interactive control!  generative systems!
* for example: algorithms!  sound synthesis!  interactive control!  generative systems!


== Part 2: "Audio-Visual" ==
=== Aspect 2: "Audio-Visual" ===
* audio: use ChucK
* audio: use/combine techniques we covered in class (synthesis, generative, interaction) or something else; use [http://chuck.stanford.edu ChucK]
* visual: interpret this as you'd like;
* visual: interpret this as you'd like;
** option 1: use Processing for real-time graphics/animation, coupled to audio/ChucK via OSC
** option 1: use [https://processing.org/ 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
** option 2: otherwise involve visuals in a core/non-peripheral way: e.g., design gestures/movement mapped to sound


== Part 3: "Live Performance" ==
=== 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
* 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)
* aim for 3-7 minute per piece (though your fully designed live performance can be longer or shorter)

Latest revision as of 00:58, 23 February 2015

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

You are to craft, compose, and perform a "Computer-mediated, Audio-visual, Live Performance." 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/24/2015): initial sketch, detailing vision, sound, music, interaction, aesthetics, music technology involved
  • milestone 1 (in-class, Tuesday, 3/3/2015): initial working system, with sound, visual, and core performance
  • milestone 2 (in-class, Tuesday, 3/10/2015): fully working system + fully fleshed out performance, complete as possible
  • final performance rehearsal: Wednesday 3/18/2015, 6-10pm (sign up for a slot)
  • all material (final project website containing code, data files, README) due Wednesday 3/18/2015, 11:59:59pm
  • final presentations / performances : Thursday 3/19/2015, 3:30pm, 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


Deliverables

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