converting absolute controllers to relative,

Thanks Roald Baudoux,

Couple of things:

1st: I resolved the issue by realizing that the faderfox has a feedback
system so I don't need to transform the abs to relative anymore! doh!
and: youpie!
:)

2nd: I have made a new feature for the LV2 called "auto track select on
fader touch" - many other LV2 owners may find this useful, you can find
the code at the bottom of this email.

For the book, let me at least clarify what the issue was:
Ok, I guess I was not very clear...

Here is an example:
When I turn the external abs controller to the right, it sends the
following data:
{123,124,125,126,127,127,127,127,127,...}

If I turn it fast to the right it could send something like this:
{100,104,108,112,120,127,127,127,127,127,...}

In both cases, the code works because it moves a relative signed 2 bit
controller in my software [Ableton live].

However, in "case one" I am turning slowly, in case two I am turning
fast. When i reach the end of the data range of the absolute controller
it sends out "127" no mater how fast i am turning the knob; so I need
some other mechanism to determine how fast I am turning otherwise I get
a non-linear/unpredictable output. Hence my idea to use a counter to
measure the rate at which the "127" data enters the system.

The output of the system is either 1 or 127. But the way relative 2 bit
works is that you can also have an output of 4 or 122. A "4" means move
up 4 steps and a "122" means move down 128-122=6 steps. this makes it
possible to "spin" these kinds of relative controllers quickly for rapid
changes - a form of smart acceleration.

What i was asking is if there was a smart / elegant way to measure a
rate of change, or if the only way to measure rate is to use a
time-control object; like metro?

--
LV2 feature addition: Auto select track on fader touch: Connect the out
port of your system back to the LV2 to have the LV2 auto-switch tracks
when moving a fader! Enjoy!
;)