Difference between revisions of "PLOrk spring2010"

From CSWiki
Jump to: navigation, search
(Tentative precept schedule)
(Tentative precept schedule)
 
(18 intermediate revisions by 2 users not shown)
Line 122: Line 122:
 
*** Using the wekinator with feature extractors & synthesizers
 
*** Using the wekinator with feature extractors & synthesizers
 
** Using the [http://wekinator.cs.princeton.edu/ Wekinator] with HID devices and synthesis classes
 
** Using the [http://wekinator.cs.princeton.edu/ Wekinator] with HID devices and synthesis classes
 +
** Scribe notes from today
 +
*** [http://www.cs.princeton.edu/~fiebrink/314/2010/week5/scribe_hannah_1.pdf Part 1 by Hannah Barudin]
 +
*** [http://www.cs.princeton.edu/~fiebrink/314/2010/week5/scribe_clayton_2.pdf Part 2 by Clayton Raithel]
 
* 3/10 or possibly 3/8: Dan/Cameron/Dan teaching
 
* 3/10 or possibly 3/8: Dan/Cameron/Dan teaching
** Topic TBA: Probably focus on interaction and mapping
+
** Review of wekinator, interaction, and mapping
 
* 3/17: SPRING BREAK!
 
* 3/17: SPRING BREAK!
 
* 3/24: MIDTERM PERFORMANCES!
 
* 3/24: MIDTERM PERFORMANCES!
 
* 3/31: Frequency domain, plus lots of other useful things
 
* 3/31: Frequency domain, plus lots of other useful things
 +
** Makeup midterm performances
 
** Time/frequency representation of sound
 
** Time/frequency representation of sound
 
*** FFT and STFT
 
*** FFT and STFT
** Using audacity and sndpeek for spectral analysis
+
*** See FFT handout [http://www.cs.princeton.edu/~fiebrink/314/2010/week8/FFT_handout_2010.pdf here]
** Advanced coding practices
+
*** Using audacity and sndpeek for spectral analysis
 +
*** Analysis-resynthesis practice
 +
** Advanced coding practices / ChucK tips
 
*** blackhole object
 
*** blackhole object
 
*** scope, loops, and (no) garbage collection
 
*** scope, loops, and (no) garbage collection
** Analysis-resynthesis practice
+
** Chuck's unit analyzer infrastructure
** Implementing your own SynthClass for Wekinator (review & tips)
+
*** See [http://chuck.cs.princeton.edu/uana/ Chuck UAna reference]
** Intro to Open Sound Control
+
*** Perry's FFT/IFFT examples: [http://www.cs.princeton.edu/~prc/314/FFT/ http://www.cs.princeton.edu/~prc/314/FFT/] from 2009
 +
** [http://www.cs.princeton.edu/~fiebrink/314/2010/week8/ Code examples from class]
 +
** [http://www.cs.princeton.edu/~fiebrink/314/2010/week8/scribe_Mia.pdf Scribe notes by Mia]
 
* 4/7 Machine listening and audio analysis
 
* 4/7 Machine listening and audio analysis
 
** Audio analysis techniques
 
** Audio analysis techniques
 
*** FFT continued
 
*** FFT continued
 
*** Features, timbre, and perception
 
*** Features, timbre, and perception
*** UAnae and other audio feature extraction tools
+
*** UAnae and other audio feature extraction tools (see [http://chuck.cs.princeton.edu/doc/program/uana.html http://chuck.cs.princeton.edu/doc/program/uana.html])
 
** Supervised learning algorithms
 
** Supervised learning algorithms
 +
** [http://www.cs.princeton.edu/~fiebrink/314/2010/week9/ Code examples from today (cross-synthesis)]
 +
*** Also see Perry's FFT examples from 2009 at [http://www.cs.princeton.edu/~prc/314/FFT/ http://www.cs.princeton.edu/~prc/314/FFT/] (includes SinOsc pitch tracker)
 +
** Scribe notes:
 +
*** [http://www.cs.princeton.edu/~fiebrink/314/2010/week9/scribe_clayton.pdf Part 1 by Clayton]
 +
*** [http://www.cs.princeton.edu/~fiebrink/314/2010/week9/Scribe_Hayk.pdf Part 1/2 by Hayk]
 
* 4/14: More interactive coding techniques
 
* 4/14: More interactive coding techniques
 +
** MIDI, Events, LiSa introduction, coding strategies
 +
** [http://music.princeton.edu/~dan/plork/poly_midi.zip coding examples from class]
 +
** also, [http://wiki.cs.princeton.edu/index.php/LiSa_examples LiSa examples]
 +
** and [http://music.princeton.edu/~dan/LiSa/LiSa_tutorial.html LiSa tutorial]
 +
** and [http://chuck.cs.princeton.edu/doc/program/ugen_full.html#LiSa LiSa basic documentation]
 +
* 4/21
 +
** Intro to filters
 
** OSC
 
** OSC
** Writing your own events
+
*** See basic OSC examples: [http://chuck.cs.princeton.edu/doc/examples/osc/s.ck sender] and [http://chuck.cs.princeton.edu/doc/examples/osc/r.ck receiver]
** Writing your own classes
+
*** Rebecca's [http://www.cs.princeton.edu/~fiebrink/314/2009/osc_handout.pdf OSC handout]
** MIDI (if we haven't covered it already)
+
** Examples from class: [http://www.cs.princeton.edu/~fiebrink/314/2010/week11/ here]
* 4/21 and 4/28: What's left?
+
** Scribe notes from Emi & Tom:
** LiSa (introduce this earlier somewhere?)
+
* 4/28: What's left?
** Filters
+
** More on Filters
** Phase
 
** Aliasing
 
 
** Max/MSP and Processing
 
** Max/MSP and Processing
** Other wrap-up
 
  
 
=== Scribe notes ===
 
=== Scribe notes ===
Line 175: Line 192:
 
** [http://www.cs.princeton.edu/~fiebrink/314/2010/assignments/assignment4/assignment4.pdf download]
 
** [http://www.cs.princeton.edu/~fiebrink/314/2010/assignments/assignment4/assignment4.pdf download]
 
** See associated [http://www.cs.princeton.edu/~fiebrink/314/2010/assignments/assignment4/ stuff]
 
** See associated [http://www.cs.princeton.edu/~fiebrink/314/2010/assignments/assignment4/ stuff]
 +
* Assignment 5: due 4/13/10
 +
** [http://www.cs.princeton.edu/~fiebrink/314/2010/week8/314assignment5.pdf download]
 +
* Assignment 6: due 5/3/10
 +
** [http://www.cs.princeton.edu/~fiebrink/314/2010/assignments/assignment6/314assignment6.pdf download]
  
 
=== Code resources ===
 
=== Code resources ===
Line 186: Line 207:
 
*** Webcam code: [http://www.cs.princeton.edu/~fiebrink/314/2010/extractors/colortracker2.zip http://www.cs.princeton.edu/~fiebrink/314/2010/extractors/colortracker2.zip]
 
*** Webcam code: [http://www.cs.princeton.edu/~fiebrink/314/2010/extractors/colortracker2.zip http://www.cs.princeton.edu/~fiebrink/314/2010/extractors/colortracker2.zip]
 
**** This should show a webcam picture on your screen. Read the 314_ColorTrackFeatureExtractor.ck header for instructions on how to start tracking colors. If you get an error with this, you may have to set this app to run in 32-bit mode on OS X (right-click icon -> get info -> Open in 32-bit mode).
 
**** This should show a webcam picture on your screen. Read the 314_ColorTrackFeatureExtractor.ck header for instructions on how to start tracking colors. If you get an error with this, you may have to set this app to run in 32-bit mode on OS X (right-click icon -> get info -> Open in 32-bit mode).
*** Chuck code: [http://www.cs.princeton.edu/~fiebrink/314/2010/extractor/314_ColorTrackFeatureExtractor.ck http://www.cs.princeton.edu/~fiebrink/314/2010/extractors/314_ColorTrackFeatureExtractor.ck]
+
*** Chuck code: [http://www.cs.princeton.edu/~fiebrink/314/2010/extractors/314_ColorTrackFeatureExtractor.ck http://www.cs.princeton.edu/~fiebrink/314/2010/extractors/314_ColorTrackFeatureExtractor.ck]
 
**** More troubleshooting: You can only have 1 color tracker running at once. If you run into problems, make sure you're running the webcam app (and can see yourself in the webcam on the screen); if you still have problems, type "killall chuck" in Terminal and restart miniaudicle.
 
**** More troubleshooting: You can only have 1 color tracker running at once. If you run into problems, make sure you're running the webcam app (and can see yourself in the webcam on the screen); if you still have problems, type "killall chuck" in Terminal and restart miniaudicle.
 
** pitch detection (max/msp fiddle standalone application, sending to ChucK) [http://music.princeton.edu/~dan/plork/fiddleToChuck.zip here]
 
** pitch detection (max/msp fiddle standalone application, sending to ChucK) [http://music.princeton.edu/~dan/plork/fiddleToChuck.zip here]
Line 196: Line 217:
 
** Jeff's wekinated FM synth: [http://www.cs.princeton.edu/~fiebrink/314/wekinator/Jeff_FM_Synth_wekinated.ck http://www.cs.princeton.edu/~fiebrink/314/wekinator/Jeff_FM_Synth_wekinated.ck] (wekinator changes synth, key down triggers note on, key up triggers note off)
 
** Jeff's wekinated FM synth: [http://www.cs.princeton.edu/~fiebrink/314/wekinator/Jeff_FM_Synth_wekinated.ck http://www.cs.princeton.edu/~fiebrink/314/wekinator/Jeff_FM_Synth_wekinated.ck] (wekinator changes synth, key down triggers note on, key up triggers note off)
 
** Jeff's wekinated hammond synth: [http://www.cs.princeton.edu/~fiebrink/314/wekinator/Jeff_Hammond_wekinated.ck http://www.cs.princeton.edu/~fiebrink/314/wekinator/Jeff_Hammond_wekinated.ck] (SMELTified so that keyboard controls pitch)
 
** Jeff's wekinated hammond synth: [http://www.cs.princeton.edu/~fiebrink/314/wekinator/Jeff_Hammond_wekinated.ck http://www.cs.princeton.edu/~fiebrink/314/wekinator/Jeff_Hammond_wekinated.ck] (SMELTified so that keyboard controls pitch)
 +
*** This was updated on 3/29/10 to keep system from crashing with 0 valued params!
 
** Jeff's wekinated sampling synth
 
** Jeff's wekinated sampling synth
  

Latest revision as of 16:59, 17 May 2010

General Information

Welcome to COS/MUS 314/316 for Spring 2010. YOU are PLOrk, now don't hurt yourself!! Coming soon:

  • 314 syllabus
  • 316 syllabus

In addition to YOU, the following are involved in teaching these courses:

  • Dan Trueman, professor in Music
  • Rebecca Fiebrink, graduate student in Computer Science
  • Daniel Iglesia, visiting lecturer from Columbia University
  • Jeffrey Snyder, Technical Director, Princeton Computer Music Studios, and Associate Director of PLOrk
  • Cameron Britt, graduate student in Music

Laptop Configuration

All PLOrk members must configure their laptops (Macbooks) as described here

The current version of the PLOrk Repository, broken down into subfolders that can be downloaded individually, can be found here

Schedule

Classes

Precepts WILL be held the first week of class!!

  • 314: Precepts on Wednesdays from 7:30-9:20pm, Woolworth 102
  • 316: Precepts on Wednesdays from 7:30-9:20pm, Studio A/B
  • 314 and 316: Thursday rehearsal from 1:30-4:20pm, McAlpin and other rooms in Woolworth, when we break into smaller groups.

Important Dates

  • Classes begin: February 3 (both 314 and 316 will meet in 102 to start)
  • Spring break: Week of March 14
  • March 24: informal performances of midterm projects (314, maybe 316) at the Whitman Theater
  • April 2 & 3: Taplin dress rehearsal & performance
  • May 15: outdoor/indoor open house performances & projects

Resources

  • PLOrk Reader; lots and lots of reading relevant to PLOrk and this seminar in general. please add as you see fit, and ask us for the password for protected papers if you can't guess it.
  • Be sure you're on the PLOrk314-316 mailing list.
  • See the extensive list of resources at the Fall 2007 Wiki for starters.

COS/MUS 314 Info

Rebecca's office hours

Days & Times: Tuesday 1:30-2:30pm, Friday 1:30-2:30pm, also by appointment, beginning 2/9/10.

My office is room 416 in the Computer Science building, which is attached to the Friend center. The easiest way to find it is to take the CS building elevator to the 4th floor, turn right out of the elevator, and go to the third office on the right.

If my officemates are in my office and someone comes to meet with me for office hours, I'll often move to the CS tea room (which is basically a much bigger communal room with lots of tables and chairs, as well as some tea). In this case, I'll put a sign on my door for you to go to the tea room. To get there, go down the long hallway to your left once you come out of the elevator on the 2nd floor. The tea room is at the end of the hall.

You're always welcome to email me to set up a time to meet outside of office hours, but I don't recommend stopping by my office unannounced and expecting me to be there, since I do work from home a lot.

Tentative precept schedule

Scribe notes

For each Wednesday precept, we’ll ask for two volunteer scribes to take notes for an hour each, then email the notes to Rebecca in doc or txt format by the following Sunday. She’ll post them to the course Wiki, you will be the recipient of immortal gratitude from your classmates and countless others around the world, and you’ll receive extra credit (up to 1/2 of a homework assignment).

We'll post completed scribe notes up in the precept schedule, along with the corresponding precept topic outline.

Assignments

Please submit Assignments in Blackboard unless the instructions say otherwise. We'll often use Blackboard to give you feedback on your assignments, as well.

Code resources

MUS 316 Info

316 office hours (Dan I.)

I will be available before and after class and precept, and by appointment. If I am not around, technical issues (to PLOrk hardware and software, or studio hardware and software) can be addressed to Jeff.

Tentative precept schedule

Putting studio back into chuck info : newstuff

  • 2/3 studio hardware and software, routing, Pro Tools, recording
  • 2/10 sequencing, software modules, automation, editing
    • assig #1 discussion
    • Listening (field recording): various (probably pushed until next week)
  • 2/17 synthesis, psychoacoustics
    • Listening (synthesis and tuning): Riley, Young, Carlos, and others
  • 2/24 digital signal processing: time and amplitude
    • Listening(historical tape pieces): Schaeffer, Cage, Xenakis, Varese
  • 3/3 digital signal processing: filters/EQ, frequency domain, etc
    • Listening (mixed tape pieces): Stone, Broadcast
  • 3/10 production techniques, spatialization, specialized processing software (spear, soundhack, meapsoft)
  • 3/17 BREAK
  • 3/24 midterm presentations (with MUS314);
  • 3/31 generative processes
    • Listening: Lucier, Lewis
    • Take apart my “Ghost Jockey” and “DX-Heaven”
  • 4/7 instruments and live electronics
    • Listening: Hassell, de Leon
    • Take apart my “Transfaction”
  • 4/14 digital manipulation and digital failure
    • Listening: Cascone, Collins, Autechre, Anderson, etc
  • 4/21 incorporating multimedia interaction (video, sensors, etc)
    • Watching: Breer, Brakhage, Kraftwerk, Anderson, Repetto, etc.
    • Take apart my performance systems
  • 4/28 TBA, workshopping projects

Assignments

  • 1: listening and response; due 2/10 here
  • 2: field recording and editing; due 3/10 here
  • 3: studio composition (midterm); due 3/31
  • 4: performance instrument; due 4/28
  • 5: final project (either a fixed tape piece or a software system for performance or installation); proposal due 4/14; project due dean’s date

Rehearsal Groups and Schedules