one hour's feedback

[Michael Heuer]

Hello,

I was able to spend an hour or so with Wekinator last night, and while
I did get things up and running, I wasn't really able to make any
music with it yet. The setup/getting started doc might want to run
completely through a single example that works on all platforms (with
say mouse input), and give specifics about what motions to use when
training and what the result musically should be (e.g. vertical
movement of the mouse affected the pitch of the connected synth).

If I were using Wekinator for a performance, I would want it to be
running in the background on the command line from a saved
configuration, would that be possible?

Thank you,

michael

[Rebecca Fiebrink]

Hi Michael,

Thanks again for your feedback and for joining the wekinator list! Everyone else on here, please feel free to chime in.

> The setup/getting started doc might want to run
> completely through a single example that works on all platforms (with
> say mouse input), and give specifics about what motions to use when
> training and what the result musically should be (e.g. vertical
> movement of the mouse affected the pitch of the connected synth).

Agreed! I've posted a walkthrough that we used in PLOrk online here:
http://wiki.cs.princeton.edu/index.php/ChucK/Wekinator/Walkthrough

This doesn't exactly do what you asked -- in particular, it doesn't specify which input device/features someone should use. But it's almost there. You might find this helpful in getting Wekinator to make sound. And feel free to edit to make this better (this goes for anyone).

>
> If I were using Wekinator for a performance, I would want it to be
> running in the background on the command line from a saved
> configuration, would that be possible?

Basically, yes. If you run "java -jar Wekinator.jar --help", you can see the instructions for command line arguments for launching a saved configuration. The configuration files used here (for features, chuck settings, and learning system) can all be created and saved from within the app. There are also options to start running the Wekinator on launch, and to minimize the GUI.

Currently, there isn't a way for the Wekinator to run in GUI-less mode, or a way to save all these configuration files in one go from the GUI, though those would probably be nice.

Best,
Rebecca

[Daniel Trueman]

related, though not exactly the same: i've been interested in having a version of W that can import into MXJ in Max, so we can bypass OSC altogether and wrap it up nicely inside Max. there would be many advantages to this, including avoiding the OSC instabilities that crop up, and also for "publishing" instruments in ways that are easy for others to use (via exporting standalone applications in Max). as part of this, being able to suppress the GUI when using it as a fully trained instrument would make sense.

any max/mxj users out there?

dt

[Rebecca Fiebrink]

That sounds like a great idea! Many people have requested tighter integration into Max. I've never used MXJ though, so I'd love to hear from someone who's more familiar with it.

Rebecca

[Jeff Snyder]

Dan, that sounds like a great idea,
I haven't messed around much with mxj stuff in Max yet either, but
that possibility sounds very interesting to me...
-Jeff

[Cameron Britt]

It is a great idea. I think Konrad has done some stuff with MXJ... Is he on this list?