Robin Schmidt
Robin Schmidt
if we do oversampling, i'd probably rather just throw in a bessel filter
ok, we'll see. i'm offline now until sunday
not only do they have a different speed/rate but also are mouse movements potentially (and likely) non-equidistant which pretty much rules out any common filtering technique for upsampling the mouse...
well, if your use rosic::ExponentialSmoother for smoothing, this class actually encapsulates the sample-and-hold process and the 1st order lowpass into one convenient object. you could simply put another lowpass after...
smoother2 doesn't need a target value. it always gets an input that has the S/H already applied. think of it as a 3 step process: 1: sample-and-hold (i.e. update the...
hmm...maybe a general higher order Smoother class could be written that has a setOrder() function. no need to restrict yourself to powers of two, btw.
conceptually, it's just sample-and-hold and then apply any number of 1st order lowpasses one after another. of course, some optimizations are possible: if all lowpasses have the same settings, you...
...also, it's not necessary that all lowpasses have the same cutoff. it's not even necessarry to use a bunch of 1st order lowpasses - instead a single high-order lowpass could...
...but that might be too fancy. i guess, an auto-scaled series of equal lowpasses should be good enough and more straightforward and efficient
> Bah, just tried fourpolefilter what kind of four pole filter?