Revision as of 16:59, 19 November 2009

Current revision

Line 25:

=== Code ===

* File IO based communication (as alternative to OSC for large feature vectors)

-

* Allow synthesis module to communicate current parameters to GUI (just once, not in play-along mode), to allow parameter text boxes to be auto-filled (Konrad's idea)

+

* Allow synthesis module to communicate current parameters to GUI (just once, not in play-along mode), to allow parameter text boxes to be auto-filled (Konrad's idea) (done)

-

* Ability to designate N-M mappings (not All-All), e.g. ability to train one classifier on vocal features and one on gesture features (Anne's request)

+

* Ability to designate N-M mappings (not All-All), e.g. ability to train one classifier on vocal features and one on gesture features (Anne's request) (done)

* Integrate MFCC feature extractor, possibly ramp time feature extractor (Cameron's request, ref. Adam Tindale's paper)

* Debug mode flag so that users don't get scared when they see code messages being printed out

Line 42:

* More thought on time-dependent features / modeling

* Fix so that user gets indicator that training has finished after a long training round, not just 1st time

-

* Better control of ChucK (get rid of machine add files)

+

* Better control of ChucK (get rid of machine add files) (done, but currently buggy)

+

** Incorporate console to view chuck's error messages

+

** Add --blocking, perhaps as an option to chuck

+

* Ability to capture palette of sound you like during a 1st rough training, then re-play these during playalong mode.

+

* Ability to quickly change mappings mid-performance

+

** And ability to specify this via an OSC command

+

* Fix OSC feature receiver so that ints are accepted as well as floats

+

=== Documentation ===

Line 55:

Line 62:

* Tip: Drag from Finder to Terminal to get path

* Explicit info on message used to send params to Wekinator from OSC synth (/realValue f+)

-

+

* Better documentation on how to edit SynthClass for incorporating your own synthesizer from previous code: specifically, telling user to make all methods & variables class methods & variables & to spork everything in setup().

+

* Updated build instructions: ant w/ svn

=== Examples ===

Line 95:

Line 103:

*** Create traditional dataset & use CV accuracy to select features & classifier?

*** Integrate with methods like onset detection for selective application of Wekinator output?

+

* November 9

+

** New version includes check boxes for parameters, so you can decline to train certain parameters on the input you're currently providing

+

** Konrad & Dan brought in their work to hack on

+

** Briefly discussed upcoming Chuck-within-GUI support

+

* November 16

+

** Chuck within GUI is working (but buggy): We definitely need better debugging support for running in this mode, so that users have feedback on what Chuck is doing!

+

** Dan, Cameron, and Konrad all brought their stuff to work on

+

*** Cameron has an Arduino controller speaking to ChucK using Chuck file I/O!

+

*** Dan using tether blotar with the help of several people; also wekinating sillicarbon code

+

** Anne and others discussed still needing ability to specify which features control which parameters (this is coming for next week!)

+

** Dan and I talked about allowing the user to create a play-along score from within the GUI, for example using parameter snapshots from a previous training round

+

== Bibliography ==

Line 130:

Line 150:

This will grab you a copy of all the code.

-

Step 1: Do this every time you update:

+

Step 1: Do this every time you update.

-

Download dist.zip from http://www.cs.princeton.edu/~fiebrink/drop/wekinator/dist.zip

+

-

Unzip this file, which will create a directory called "dist." Find the wekinator-read-only directory that SVN created in step 0. Put the new dist directory in

+

-

wekinator-read-only/project/java/Wekinator/

+

Open terminal. Go to the wekinator-read-only directory. Type:

-

so that you now have a directory wekinator-read-only/project/java/Wekinator/dist

+

<pre>svn update</pre>

-

(This updates the java executable file, which we don't put in SVN.)

+

This will check out all the other changes into your directory. If you've made modifications to the code, it'll try to merge my changes with yours. Likewise, if you've created your own files, SVN will not move / delete / overwrite / change them.

-

Step 2: Do this every time you update.

+

Step 2: After step 1, every time you update: <b>NEW instructions as of 11/19/09</b>

+

In terminal, go to directory java/Wekinator/. At the prompt, type:

-

Open terminal. Go to the wekinator-read-only directory. Type:

+

-

<pre>svn update</pre>

+

You should see "Build successful" after this finishes running. If you don't see that, make sure you've done Step 1, otherwise email Rebecca because it's probably her fault!

-

This will check out all the other changes into your directory. If you've made modifications to the code, it'll try to merge my changes with yours. Likewise, if you've created your own files, SVN will not move / delete / overwrite / change them.

+

(This updates the java executable file, which we don't put in SVN.)

-

+

-

=== Option 2 for developers ===

+

-

Just use SVN, build .jar yourself using NetBeans or IDE of choice. Netbeans make files etc. should all be in SVN.

+

 | style="background:#DDDDDD"| ||  ||
 |-
-| style="background:#DDDDDD"| sputter || Jascha Narveson (mostly stored in Studio D) ||
+| style="background:#DDDDDD"| sputter || given back to Dan after the Oct. 9 NYC show.
 |-
 | style="background:#DDDDDD"| ||  ||

CSWiki - Recent changes [en]

PLOrk laptops

MML fall2009

 === Code ===
 * File IO based communication (as alternative to OSC for large feature vectors)
-* Allow synthesis module to communicate current parameters to GUI (just once, not in play-along mode), to allow parameter text boxes to be auto-filled (Konrad's idea)
+* Allow synthesis module to communicate current parameters to GUI (just once, not in play-along mode), to allow parameter text boxes to be auto-filled (Konrad's idea) (done)
-* Ability to designate N-M mappings (not All-All), e.g. ability to train one classifier on vocal features and one on gesture features (Anne's request)
+* Ability to designate N-M mappings (not All-All), e.g. ability to train one classifier on vocal features and one on gesture features (Anne's request) (done)
 * Integrate MFCC feature extractor, possibly ramp time feature extractor (Cameron's request, ref. Adam Tindale's paper)
 * Debug mode flag so that users don't get scared when they see code messages being printed out
 * More thought on time-dependent features / modeling
 * Fix so that user gets indicator that training has finished after a long training round, not just 1st time
-* Better control of ChucK (get rid of machine add files)
+* Better control of ChucK (get rid of machine add files) (done, but currently buggy)
+** Incorporate console to view chuck's error messages
+** Add --blocking, perhaps as an option to chuck
+* Ability to capture palette of sound you like during a 1st rough training, then re-play these during playalong mode.
+* Ability to quickly change mappings mid-performance
+** And ability to specify this via an OSC command
+* Fix OSC feature receiver so that ints are accepted as well as floats
 === Documentation ===
 * Tip: Drag from Finder to Terminal to get path
 * Explicit info on message used to send params to Wekinator from OSC synth (/realValue f+)
+* Better documentation on how to edit SynthClass for incorporating your own synthesizer from previous code: specifically, telling user to make all methods & variables class methods & variables & to spork everything in setup().
+* Updated build instructions: ant w/ svn
 === Examples ===
 *** Create traditional dataset & use CV accuracy to select features & classifier?
 *** Integrate with methods like onset detection for selective application of Wekinator output?
+* November 9
+** New version includes check boxes for parameters, so you can decline to train certain parameters on the input you're currently providing
+** Konrad & Dan brought in their work to hack on
+** Briefly discussed upcoming Chuck-within-GUI support
+* November 16
+** Chuck within GUI is working (but buggy): We definitely need better debugging support for running in this mode, so that users have feedback on what Chuck is doing!
+** Dan, Cameron, and Konrad all brought their stuff to work on
+*** Cameron has an Arduino controller speaking to ChucK using Chuck file I/O!
+*** Dan using tether blotar with the help of several people; also wekinating sillicarbon code
+** Anne and others discussed still needing ability to specify which features control which parameters (this is coming for next week!)
+** Dan and I talked about allowing the user to create a play-along score from within the GUI, for example using parameter snapshots from a previous training round
 == Bibliography ==
 This will grab you a copy of all the code.
-Step 1: Do this every time you update:
+Step 1: Do this every time you update.
-Download dist.zip from http://www.cs.princeton.edu/~fiebrink/drop/wekinator/dist.zip
-Unzip this file, which will create a directory called "dist." Find the wekinator-read-only directory that SVN created in step 0. Put the new dist directory in
-wekinator-read-only/project/java/Wekinator/
+Open terminal. Go to the wekinator-read-only directory. Type:
-so that you now have a directory wekinator-read-only/project/java/Wekinator/dist
+<pre>svn update</pre>
-(This updates the java executable file, which we don't put in SVN.)
+This will check out all the other changes into your directory. If you've made modifications to the code, it'll try to merge my changes with yours. Likewise, if you've created your own files, SVN will not move / delete / overwrite / change them.
-Step 2: Do this every time you update.
+Step 2: After step 1, every time you update: <b>NEW instructions as of 11/19/09</b>
+In terminal, go to directory java/Wekinator/. At the prompt, type:
-Open terminal. Go to the wekinator-read-only directory. Type:
+<pre>ant</pre>
-<pre>svn update</pre>
+You should see "Build successful" after this finishes running. If you don't see that, make sure you've done Step 1, otherwise email Rebecca because it's probably her fault!
-This will check out all the other changes into your directory. If you've made modifications to the code, it'll try to merge my changes with yours. Likewise, if you've created your own files, SVN will not move / delete / overwrite / change them.
+(This updates the java executable file, which we don't put in SVN.)
-=== Option 2 for developers ===
-Just use SVN, build .jar yourself using NetBeans or IDE of choice. Netbeans make files etc. should all be in SVN.