Project
Accelerometer to CC output (Missing Link)
Started by armatronix on .
Sign in or create an account to join the conversation.
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.
ML Accelerometer Lemur.zip
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.
ML Accelerometer Lemur.zip
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
Here's a new version, I used an extra ring area to smooth z.
Can anyone help me figure out how to make ring areas move when the interface loads, without requiring initial touches?
To do:
* allow user to change x, y, and z target cc#s (dynamic osc addressing)
* change target midi channel (dynamic osc addressing)
* adjust cc value output ranges
* adjust accelerometer sensitivity
* save settings (possible?)
Done:
* smooth z-values
* toggle output on/off for each axis
* switch axis +/- directions
* change ring area physics for different responses
ML Accelerometer Lemur 03.zip
Can anyone help me figure out how to make ring areas move when the interface loads, without requiring initial touches?
To do:
* allow user to change x, y, and z target cc#s (dynamic osc addressing)
* change target midi channel (dynamic osc addressing)
* adjust cc value output ranges
* adjust accelerometer sensitivity
* save settings (possible?)
Done:
* smooth z-values
* toggle output on/off for each axis
* switch axis +/- directions
* change ring area physics for different responses
ML Accelerometer Lemur 03.zip
This is SOOO cool. Makes my attempt look pretty lame, even with help from high mountain and lucasparis http://liine.net/forum/viewtopic.php?f=25&t=836&p=2730#p2730
Its just a module to output accel values when the pad is pressed
Things I don't know how to do
. smooth the output so its not sending mass data and scale to 127
. make it the ball move slowly back to the accel point when engaged rather than jumping
acceltester.jzlib.zip
Its just a module to output accel values when the pad is pressed
Things I don't know how to do
. smooth the output so its not sending mass data and scale to 127
. make it the ball move slowly back to the accel point when engaged rather than jumping
acceltester.jzlib.zip