Rebecca

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 25 total)
  • Author
    Posts
  • in reply to: Complex Gestures with Wekinator and Kinect #533

    Rebecca
    Keymaster

    Yes, this is certainly possible. I recommend especially paying attention to the Kadenze lectures on features and capturing change over time.

  • in reply to: Recieve OSC input over IP #531

    Rebecca
    Keymaster

    Wekinator will be perfectly happy to receive OSC from outside networks (it can’t even tell where a message is coming from). You will need to ensure that Muse Monitor is sending to the right IP address, that your network isn’t blocking OSC messages, that Muse Monitor is sending to the right port (6448 by default), that Muse Monitor is sending the right message name (if not /wek/inputs, Wekinator’s default, then you’ll need to change the OSC message name in Wekinator), and that Muse Monitor is sending a single OSC message with all its features sent in the same message (the same number of features every time) as floats. (See http://www.wekinator.org/detailed-instructions/#1_Setting_up_communication_between_inputs_outputs_and_Wekinator for more info.) If Muse Monitor isn’t capable of doing this, you’ll need to use a separate program like OSCulator or something you’ve written yourself to translate Muse Monitor messages into these types of messages.

  • in reply to: FaceOSC & Wekinator on Mac #519

    Rebecca
    Keymaster

    Hi Pratyush,

    Thanks for posting. There is an issue with openFrameworks-generated apps on some versions of OS X, specifically having to do with OS X Gatekeeper. This may be causing the problem you’re seeing.

    One easy fix is to move the app to another directory (e.g., to the desktop) and then back. Then try double-clicking on it again. If it’s the Gatekeeper issue causing your problem, this should fix it.

  • in reply to: faceOSC ——->> wekinator #514

    Rebecca
    Keymaster

    Hi there,

    Regarding the problem with the pre-compiled executable, I suspect you are experiencing the same problem as here: http://www.wekinator.org/forums/topic/mac-binaries-failing-for-webcam-inputs/

    There is an issue with openFrameworks-generated apps on High Sierra, specifically having to do with OS X Gatekeeper.

    One easy fix is to move the app to another directory (e.g., to the desktop) and then back. Then try double-clicking on it again. If it’s the Gatekeeper issue causing your problem, this should fix it.

    Rebecca

    • This reply was modified 11 months, 3 weeks ago by  Rebecca.
  • in reply to: faceOSC ——->> wekinator #512

    Rebecca
    Keymaster

    Hi there,

    I’m also on Sierra and FaceOSC works OK for me, so it’s hard to say what is going wrong. I recommend the following:
    1. Make sure you’re running the executable (http://www.doc.gold.ac.uk/~mas01rf/WekinatorDownloads/wekinator_examples/executables/mac/inputs/VideoInput_FacialExpression_oF_14Inputs.zip) rather than from source, in case something has changed in the source on Gene’s github to make it incompatible
    2. Make sure FaceOSC executable draws funny white lines on your face. If it doesn’t, that means it isn’t finding your face. Ensure the data/ directory (which was in the same zip as the executable) remains in the same directory as the executable. (I.e., unzip the file from step 1 and don’t move the executable without the data directory). If you still don’t see white lines, try adjusting your lighting or removing your glasses.
    3. Restart your computer and launch only the FaceOSC executable and Wekinator, and ensure Wekinator is set up to receive 14 inputs. Restarting ensures that there isn’t some other program also receiving OSC.

    Hope this helps.

  • in reply to: export model as C++ file #511

    Rebecca
    Keymaster

    Hi there, this option isn’t yet in the official “release” builds of Wekinator, but you can get it by either (1) building Wekinator from the current source (https://github.com/fiebrink1/wekinator), or (2) using Michael Zbyszyński’s fork at https://github.com/mzed/wekimini (which has release versions you can download if you don’t want to build from source). Using either of these versions, every time you save a project, Wekinator will automatically save the C++ versions of the trained models within the project directory.

  • in reply to: Not receiving class probabilities from classifier #502

    Rebecca
    Keymaster

    Hi Sergio,

    I’m afraid I’m not able to duplicate this problem. Have you tried receiving these messages using this Processing sketch? http://www.doc.gold.ac.uk/~mas01rf/WekinatorDownloads/wekinator_examples/all_source_zips/Processing_SimpleDistribution_1Classifier.zip

    Rebecca

  • in reply to: OSC functionality #494

    Rebecca
    Keymaster

    Hi Jelle,

    That’s a great idea! Thanks for the suggestion. I will add this to the list of features to add to the next version (hopefully this summer).

    Best
    Rebecca

  • in reply to: OSC output and input setup #492

    Rebecca
    Keymaster

    Hi Kieran,

    For color tracking, I recommend trying out the colour tracker my student Sam made:
    https://github.com/fiebrink1/MaxColourTrackerForWekinator (in Max)
    or
    https://github.com/fiebrink1/MaxColourTrackerForWekinator/releases/tag/v1.0 (executable for Mac, which you can run outside of Max)

    If what you want to do is turn an 8×8 pixel grid into a step sequencer, you might not need machine learning for that (it may be easier just to write the code to determine what colour is present in each grid square, for instance).

    For sending data from Wekinator to Max 7, I recommend looking at the Max examples for receiving wekinator information here: http://www.wekinator.org/examples/#MaxMSP_audio-2

    It’s simpler to get started in Max than in Ableton, so I recommend making sure you understand how this all works with Max first.

    Best
    Rebecca

  • in reply to: Mac binaries failing for Webcam Inputs #491

    Rebecca
    Keymaster

    Scott, did this fix your problem?

    Jegama, can you describe what you are experiencing?

  • in reply to: Change output class with OSC (Classifier) #484

    Rebecca
    Keymaster

    Hi M,

    I’m assuming that you mean sending an OSC message to Wekinator to change the current output values (i.e., change the value of a dropdown box for a classifier, or the value of the slider/number box for a regression model), so that when you record new examples they are recorded with the correct output/label values.

    You can do this with the OSC message “/wekinator/control/outputs” . You’ll want to send 1 float per output in the current project.

    If this doesn’t answer your question, please let me know.

    Rebecca

  • in reply to: Graphic Tablet's Stylus -> OSD (Linux, Qt 5.7) #471

    Rebecca
    Keymaster

    Thanks Marc! I’ve added this (belatedly) to the wekinator examples page.

  • in reply to: Myo input utility and example #469

    Rebecca
    Keymaster

    Thanks both! I’ve linked to both your projects on the Wekinator examples page.

  • in reply to: HMM #467

    Rebecca
    Keymaster

    Nope, sorry! In my experience, HMMs usually need more training examples to work reasonably well. Gesture Follower (http://imtr.ircam.fr/imtr/Gesture_Follower) is a good alternative, since it’s designed to work with just one example per gesture class.

  • in reply to: Kinect V2 Visual Studio Skelton C++ Windows #465

    Rebecca
    Keymaster

    Thanks for sharing this, David! I’ve belatedly added this to the Wekinator examples site, with credit to you.

Viewing 15 posts - 1 through 15 (of 25 total)