https://ccrma.stanford.edu/mediawiki/index.php?title=220b-winter-2014/hw1&feed=atom&action=history220b-winter-2014/hw1 - Revision history2024-03-28T20:32:06ZRevision history for this page on the wikiMediaWiki 1.24.1https://ccrma.stanford.edu/mediawiki/index.php?title=220b-winter-2014/hw1&diff=16284&oldid=prevGe: Created page with '= Homework #1: Timbre-scapes = <div style="text-align: left;">Image:Timber.jpg</div> Due date: 2014.1.23 11:59:59pm (or thereabout), Thursday. === Reading === * skim thr…'2014-01-14T18:03:19Z<p>Created page with '= Homework #1: Timbre-scapes = <div style="text-align: left;"><a href="/wiki/File:Timber.jpg" title="File:Timber.jpg">Image:Timber.jpg</a></div> Due date: 2014.1.23 11:59:59pm (or thereabout), Thursday. === Reading === * skim thr…'</p>
<p><b>New page</b></p><div>= Homework #1: Timbre-scapes =<br />
<br />
<br />
<div style="text-align: left;">[[Image:Timber.jpg]]</div><br />
<br />
<br />
Due date: 2014.1.23 11:59:59pm (or thereabout), Thursday.<br />
<br />
=== Reading ===<br />
* skim through articles on [http://en.wikipedia.org/wiki/Aleatoric_music chance music]<br />
<br />
<br />
=== Specification (part 1 of 2): Crafting Timbres with FM ===<br />
* check out the FM synthesis/drone examples, in particular<br />
** FM synthesis basics in ChucK<br />
*** [http://ccrma.stanford.edu/courses/220b/ck/fm-by-hand.ck fm-by-hand.ck] : fm synthesis, 1::samp at a time<br />
*** [http://ccrma.stanford.edu/courses/220b/ck/fm2-sync.ck fm2-sync.ck] : more commonly used FM synth basis, setting sync to 2<br />
*** [http://ccrma.stanford.edu/courses/220b/ck/fm2-step.ck fm2-step.ck] : yet another way to do FM synthesis in ChucK, via the Step UGen<br />
** time varying Drone example (from class)<br />
*** [http://ccrma.stanford.edu/courses/220b/ck/Drone-1.ck Drone-1.ck] : FM synthesis with SinOsc modulating a SqrOsc<br />
*** [http://ccrma.stanford.edu/courses/220b/ck/Drone-2.ck Drone-2.ck] : the above with an added, time-varying "demon bunny" filter<br />
*** [http://ccrma.stanford.edu/courses/220b/ck/Drone-3.ck Drone-3.ck] : layering three of the above, controlling each independently<br />
*** [http://ccrma.stanford.edu/courses/220b/ck/fm-mod.ck fm-mod.ck] : interpolating FM synthesis parameters<br />
* using FM synthesis in ChucK, create the following:<br />
** 3 different "static" timbres<br />
*** building blocks: oscillators, filters, etc.<br />
*** experiment with various parameters such as carrier frequency, modulator frequency, index of modulation, etc.<br />
** 3 time-varying timbres<br />
*** building blocks: oscillators, filters, time-based control code<br />
*** can be a "drone" (but doesn't have to be)<br />
*** the time-varying process(s) should be somehow coupled to one or more of the FM/filter parameters<br />
** next, take a timbre from above, and apply an ADSR envelope to "carve" out an attack, decay, sustain, and release<br />
*** test this by making some bleeps and bloops<br />
<br />
<br />
<div style="text-align: left;">[[Image:Lumberjack.jpg]]</div><br />
<br />
<br />
=== Specification (part 2 of 2): Musical Statement ===<br />
* explore and employ controlled randomness and chance, time-varying timbre and compose a musical statement<br />
** macro-level structure/form: as an exercise, the piece should contain at least 3 sections (think about the flow and relationship between sections)<br />
** think about how to leverage randomness to ''controllably'' generate passages...<br />
** potential parameters that can be influenced by chance and trajectories.<br />
*** pitch<br />
*** rhythm<br />
*** meter<br />
*** timbre / synthesis parameters (e.g., FM parameters)<br />
*** dynamics<br />
*** tempo<br />
*** texture<br />
*** many, many others<br />
** plan/score your composition somehow, pay attention to the above, and especially to the control of timbre<br />
** take advantage of the timbre, time-varying control, and "bleepin'"/note/pitched event capabilities you've developed in part 1<br />
** write ChucK programs to generate the different passages/sections/layers; for each, run/record the program multiple times, tweak parameters, and choose the best result for each part.<br />
** put them together in audacity/ardour, or a bigger ChucK program (final audio file - wav)<br />
<br />
<br />
=== Deliverables ===<br />
<br />
'''turn in all files by putting them in your Library/Web/220b/hw1/ directory, and then linking to them from your Library/Web/220b/index.html - email Ge and Romain with your hw1 URL'''<br />
<br />
* 1) your static timbres (part 1): 3 chuck files<br />
* 2) your time-varying timbres + bleeps/bloops (part 1): 3 chuck files + 1 bleepin' chuck file<br />
* 3) your musical statement (part 2): chuck files + final mix (.wav file)<br />
* 4) a short README text ('''readme.txt''') file that:<br />
** conveys your ideas/comments in constructing each program <br />
** contains instructions on running your programs<br />
** describes any difficulties you encountered in the process<br />
* 5) your index.html should link to these files (optionally, you can include your README directly in your index.html)</div>Ge