resolume : layer position range , why 8192 pixels ?

[homing]

Hi guys,



i'm doing a project in which the image in a layer need to move on the Y axis of the composition.

I'm receving some dmx data from a arduino sensor via Artnet. (the screen is physicaly moving, and we are overshooting with the projector, and need the layer position in resolume to follow the movement of the screen) Everything is working fine on that way.



Here is the problem :

Why is the value of anchor Y is so big (-8192 to + 8192 ) ? What does that value represent ? Can it be changed ? Because now the movement sensor is sending signal from 0 to 127 (in dmx signal) Of course it's not working at all to link the DMX value to the position of the layer. The value is way too big



Could the be a way to link a mathematical expression like : DMX value / whatevervalue = layer anchor Y



thanks

[sleepytom]

8192 is the maximum viewport for resolume 4.

You could use processing or something to do a simple value scale from your dmx to OSC into resolume. This will give you precise control.

[vjair]

using DMX in its full range of 256 instead of 128 will also make your control more precise.

[homing]

thanks guys, for the info i also asked the guys at resolume via email . here here the reply :


Thanks for your question.


Why is the value of anchor Y is so big (-8192 to + 8192 ) ? What does that value represent ?


This value represents the minimum and maximum texture limits of your graphic card. On some computers it is even -16384 to 16384!

Can it be changed ?


No, unfortunately not.

Because now the movement sensor is sending signal from 0 to 127 (in dmx signal) Of course it's not working at all to link the DMX value to the position of the layer. The value is way too big

Could the be a way to link a mathematical expression like : DMX value / X = layer anchor Y


The thing is that even with the added math, 127 steps is usually not enough precision to handle pixel positioning. If you are sending out from an Arduino anyway, I'd suggest sending OSC values instead of DMX. This way you have floating precisions, and you can also handle the math more precisely.

I hope that answers your questions. Feel free to write if you have any more!

[homing]

workaround Follow up :

Here's what i've finnaly done : I've applied the Shift RGB effect, linked every channel (RGB) to a common dashboard knob , and controlled that knob to do th sliding.

[LR12]

instead of Shift RGB, you could also use the FrParameters FFGL plugin. Position X/Y are based on the composition size. Anchor unfortunately have a different scale (2* comp size?)

http://www.1210visuals.net/index.php...d=48&Itemid=58