OSC accelerometer values?

[Grin]

Hello,

I am slowly becoming familiar with OSC and using it with Resolume. I have been able to use TouchOSC and it's editor to create a simple layout for commands.

I am still yet to figure out how to map accelerometer values to proprieties in Resolume.

Say I want to put the opacity of my active clip on the x value of my mobiles accelerometer.

The input command would be /activeclip/video/opacity/values. I understand that the accelerometer message is from the phone as /accxyz. How do I script the input with data of the phone's accelerometer?

If someone would could give me and example that I could tinker with, that would be greatly appreciated.

Cheers!

[Sadler]

What you will want is some sort of bridge that translates /accxyz x y z to /activeclip/video/opacity/values x.

Perhaps PD or osculator or Midi Bridge. A Google search will tell you that this problem is not particular to Resolume.

[Oaktown]

Check out OSCemote for the iPhone, you can send OSC messages as follows:

Accelerometer
When you turn the accelerometer on or off, it sends an event with an int value 1 or 0 indicating on or off. When turned on, it sends a stream of 3-axis acceleration events with float values measured roughly in Gs (1.0 g = 9.81 meters per second per second = Earth's gravity).

/accelerometer {enabled}
/acceleration/xyz {x} {y} {z}
For example, turning it on, shaking the phone and then turning it off again sends:

/accelerometer 1
/acceleration/xyz 0.109012 -0.763081 -0.635901
/acceleration/xyz 0.199855 -0.763081 -0.763081
/acceleration/xyz 0.436047 -0.872093 -0.872093
/acceleration/xyz 0.181686 -0.890262 -0.363372
/acceleration/xyz -0.508721 -0.65407 0.490552
/acceleration/xyz -0.454215 -0.52689 1.01744
/acceleration/xyz -0.0363372 -0.327035 0.25436
/acceleration/xyz 0.890262 -0.327035 -2.16206
/acceleration/xyz 0.890262 -0.981105 -2.32558
/acceleration/xyz 0.0363372 -1.28997 -1.14462
/accelerometer 0

Then you would receive the data in Osculator and route one of the axis values (arg[0] for x, etc...) into an OSC string to control opacity in Resolume and send it to the Resolume port. I just tested it and it seems to work fine, but as you probably anticipate, the default value is 0 (in Gs) so it gravitates back to 0% opacity.