Robin Schmidt

the numStages will the selected automatically, according to your desired order (and whether it's a lowpass, or bandpass or whatever). oh, well you should use setPrototypeOrder

...maybe i should not publically inherit from BiquadCascade. most of its methods should not be used in an EngineersFilter object

...but as said...this should be only used for some preliminary experimentation. it will be very wasteful to use full-scale EngineersFilter objects for a task as benign as parameter smoothing (of...

ahhh...i see...you would not let the parameter-object itself be responsible for smoothing, but kind of attach a smoother object to it, whenever needed. you could keep a smoother-pool around in...

btw. i just discovered this nice pattern site a few days ago. it has a nice collection of design pattern descriptions

yes, sounds like a good design. moreover, we could dynamically attach different kinds of smoothers if they have a common baseclass (exponential, gaussian, linear, whatever)

class Smoother, subclasses: ExponentialSmoother, GaussianSmoother etc. the SmoothingManager would hold an array of pointers to the baseclass. ...or something

perhaps Smoothers should be applicable to any kind of value (not only Parameters). we could have a class: SmoothableValue and a Smoother would operate on an object of that class....

uuhh - random crashes? might this be a threading issue? i think, i will need to check this out in the proper context. changing the smoothing amount? is this the...

wtf is this? ``` smoother.setTargetValue(*this); //return smoother.getSample(); return smoother2.getSampleDirect1(*this); ``` you are passing a de-referenced this-pointer as function argument? into functions that take a double value as input?!