|
Communication
The gesture training and recognition system can be fully operated by sending OSC messages. The following list of messages detail the currently supported functionality. Message use '/gestr/action' as their OSC address pattern 1. The first string argument is the action. The responses for each message is also detailed here, with their arguments. save The save message uses the second argument to serialize the active gesture set. Saved binary files have a .gestr extension. load The second argument is used the load a gesture set from a .gestr file. For save and load, the second argument, the file path, can be either relative to the executable, or absolute. clear Clears any active gesture set. No gestures will be classified after a clear message. parameterize The parameterize message (see Parameterize) allows addition of parameters to any previously trained gesture. The arguments for this message are (in order) i) the name of the gesture to parameterize ii) the name of the new parameter and iii) the parameter specification string. train The train message will train a new gesture with the collected gesture samples. classify The classify message uses the active gesture set to classify the last sample collected. In addition to the '/gestr/action' messages, MGestr also uses the '/gestr/sample' address pattern to mark the start and end of a gesture sample. The first argument for this message is one of the two strings: 'start' and 'end'. This control flow is used by the graphical user interface to pass saved gesture samples to MGestr. Parameter updates are sent via a /gestr/action message with first arguement as parameter_update followed by the list of arguements associated with the parameter: |