Accelerometer to CC output (Missing Link)
Posted: 19 Dec 2011 08:07
Here's my first template, it's pretty simple. I wanted to be able to output CCs based upon the attitude of the device.
For Missing Link users, one important concept here is a technique for sending a message only when an axis changes by enough to warrant it, otherwise the MIDI stream gets flooded with redundant data.
Also, this shows how to use oscout to send OSC messages to the Missing Link.
The ring area changes size to indicate the accelerometer z value (which wreaks havoc on the display of the x/y values - they're actually really nice and smooth).
I'm not sure why you have to touch the ring area before it starts following the attractor.
To do:
* allow user to change x, y, and z target cc#s (dynamic osc addressing)
* change target midi channel
* adjust cc value output ranges
* toggle activity on/off for each axis
* adjust accelerometer sensitivity
* change ring area physics for different responses
* switch axis +/- directions
* save settings for all of above (possible?)
* smooth z-values
For Missing Link users, one important concept here is a technique for sending a message only when an axis changes by enough to warrant it, otherwise the MIDI stream gets flooded with redundant data.
Also, this shows how to use oscout to send OSC messages to the Missing Link.
The ring area changes size to indicate the accelerometer z value (which wreaks havoc on the display of the x/y values - they're actually really nice and smooth).
I'm not sure why you have to touch the ring area before it starts following the attractor.
To do:
* allow user to change x, y, and z target cc#s (dynamic osc addressing)
* change target midi channel
* adjust cc value output ranges
* toggle activity on/off for each axis
* adjust accelerometer sensitivity
* change ring area physics for different responses
* switch axis +/- directions
* save settings for all of above (possible?)
* smooth z-values