Filtering Question

[Patrick Ruoff]

Hi Fortran58,
thank you for your positive feedback.

As to the filtering:
It's always a tradeoff between stability, accuracy and responsiveness.
The smoothing is just a simple average over the last n samples, so yes, I would turn this off by setting it to 1.
For the accela settings, you probably want more aggressive settings than standard FTNoIR in order to decrease lag and fully use the potential of point tracking ;-)

Some explanation of what accela does (mainly copied from my post at the freetrack forum):

"It looks at the difference between the new raw values from the tracker and the last filtered values and maps this difference via the customizable response function f by:

new_val = old_val + f(new_val - old_val) / reduction_factor

So if you set f(x) = reduction_factor * x, you will get no filtering at all.
If you set lower values for small x, then small deviations (usually noise) will get dampened. (a dynamic dead-zone around the current position so to say)

What is important is the last two points, because accela uses them to extrapolate for large deviations.
If you want to get a fast unfiltered response, be sure to set a slope >= reduction_factor here."

My current settings are:

[Accela]
Reduction=10

[Curves-Accela-Scaling-Rotation]
point-count=4
point-0-x=0.1
point-0-y=0
point-1-x=1.43
point-1-y=2.45
point-2-x=2.0
point-2-y=5.44
point-3-x=2.06
point-3-y=6

The curve is not too different from the standard one (except that I like a small dynamic dead zone for steady aiming, that's why the curve has a slope of 0 at the beginning)
However, the important thing is the reduction factor. A value of 10 means compared to the standard one of 100, that each value of the curve is effectively 10 times higher than in standard FTNoIR, which means higher responsiveness but can also lead to jitter/shaking.
Guess everyone has to find his personal sweet spot.