Latest revision as of 23:07, 5 April 2012

Assignment #1: Single Hemi Instrument + Sound Sketch

This assignment asks you to work with the quintessential laptop orchestra building block: laptop + a single hemispherical speaker array, and create a short sound sketch for it!

Due dates:

milestone 2012.4.11, Wednesday (show us progress on your instrument!)
due 2012.4.18, Wednesday (demo the instrument + a short sound sketch/musical statement with it)

Specification

create an instrument for a single hemi using ChucK
should take advantage of the multi-channel aspect
consider issues of playability, expressiveness, sound, and also use in an ensemble setting
craft a very short piece for your instrument, describe/score it, be prepared to demo it
each person should turn in their own instrument - however, working together is highly encouraged!

Deliverables for Milestone

1) at least a bit of progress on both parts (some combination of ideas, source code, any scores, audio files, etc.)
2) be prepared to talk about
- your progress so far
- any difficulties you are encountering in the process
- plans for next week
- any outstanding code/design/sound issues?

Overall Deliverables

turn in all files by demo'ing

1) show us how your instrument sounds, works, etc.
2) perform/demo your sound sketch/short musical statement (~1-2 minutes in length)

Have fun with it!!!

@@ Line 1: / Line 1: @@
-= Assignment #1: Single Hemi Fun + Small SLOrk Sound Sketches  =
+= Assignment #1: Single Hemi Instrument + Sound Sketch  =
 [[Image:SLOrk-lr-01m.jpg]]
-This assignment asks you to work with the quintessential laptop orchestra building block: laptop + a single hemispherical speaker array
+This assignment asks you to work with the quintessential laptop orchestra building block: laptop + a single hemispherical speaker array, and create a short sound sketch for it!
 Due dates:
-* '''milestone A''' 2012.4.11, Wednesday.
+* '''milestone''' 2012.4.11, Wednesday (show us progress on your instrument!)
-* '''milestone B''' 2012.4.18, Wednesday.
+* '''due''' 2012.4.18, Wednesday (demo the instrument + a short sound sketch/musical statement with it)
-== Specification (part 1 of 2): Single Hemi Fun ==
+== Specification ==
 * create an instrument for a single hemi using ChucK
-* should take advantage of the multi-channel aspect (or have a good reason to not do that)
+* should take advantage of the multi-channel aspect
 * consider issues of playability, expressiveness, sound, and also use in an ensemble setting
-* craft a very short piece for your instrument, describe/score it, turn in with assignment
+* craft a very short piece for your instrument, describe/score it, be prepared to demo it
 * each person should turn in their own instrument - however, working together is highly encouraged!
+== Deliverables for Milestone ==
+* 1) at least a bit of progress on both parts (some combination of ideas, source code, any scores, audio files, etc.)
+* 2) be prepared to talk about
+** your progress so far
+** any difficulties you are encountering in the process
+** plans for next week
+** any outstanding code/design/sound issues?
-== Notes ==
-* Have fun with it!!!
-== Deliverables (milestone A) ==
-'''turn in all files by demo'ing '''
-* 1) at least a bit of progress on both parts (some combination of ideas, source code, any scores, audio files, etc.)
+== Overall Deliverables ==
-* 2) a short README text ('''readme.txt''') file that:
+'''turn in all files by demo'ing'''
-** describes your progress so far
-** describes any difficulties you are encountering in the process
-** plans for next week
-** any outstanding code issues that we reviewers will encounter during our review
+* 1) show us how your instrument sounds, works, etc.
+* 2) perform/demo your sound sketch/short musical statement (~1-2 minutes in length)
-== Deliverables (milestone B) ==
-'''turn in all files by demo'ing and checking in the files with instructors on the Tuesday that it's due, at CCRMA'''
-* 1) files for both parts of the assignment (source code, any scores, audio files, etc.)
+* Have fun with it!!!
-* 2) a short README text ('''readme.txt''') file that:
-** contains instructions on running your programs
-** describes any difficulties you encountered in the process