Forum Replies Created
…and customizing the address names of Wekinator’s input OSC messages to match those of FaceOSC ( “/gesture/mouth/width”, etc.) still had no effect: no input. Tried downloading the FaceOSC-Wekinator source to see where these messages were set, but it seems the downloads of the source, despite being on the FaceOSC-Wekinator page (https://github.com/genekogan/ofxFaceTracker/releases), actually only give the source for the *regular* FaceOSC code, not the Wekinator version.
Ok… This is my very first day trying to use any of this stuff, and I’m done trying. Please help me out.
- This reply was modified 1 year, 6 months ago by drscotthawley. Reason: added note about downloading source
I wrote some Python code for a generic server to remap OSC messages: Incoming OSC messages that contain some filter string all get sent to Wekinator. This is perhaps lazy, but it’ll get the job done!
Code here: https://gist.github.com/drscotthawley/7c8337582f55191989d96db277be3c7d
I recommend running this first before starting up Wekinator, so you’ll know how many (Wekinator) inputs you have.
Glaferg, did you ever figure out how to do the remapping? I have a student who’s also interested in using Muse Monitor with Wekinator. My OSCulator skills are minimal, but perhaps you and he could work together to create an OSCulator file that others could easily import.
It seems like the TouchOSC example (http://www.wekinator.org/examples/#TouchOSC_for_mobile_devices_and_tablets_iOS_Android) yields an example many-to-one mapping wherein the slider values are made to piggyback on the accelerometer output (somehow…?) Perhaps that could serve as a template?
…Alternatively, maybe you could do the remapping “by hand” without OSCulator, e.g. via the Python input bundle.
- This reply was modified 6 months, 2 weeks ago by drscotthawley. Reason: added note about Python