[filterdesign] bug ?
Hi,
The output of the object [cascade~] saturates when incrementing the order of a filter. Everything goes well if you decrement the order.
It seems to be a bug...
Thanks
i see no difference, peak is always the same.
of course if you send it "order 72" it might take a while until the filter is set up, and during that time the meter is over, because it hangs on the click.
yeah and it takes longer the higher the difference of the order value.
it basically clicks at every vector when a new filter is produced. so it depends on sampling rate and vectorsize, which is why i dont see and hear much before going up for at least 10 filters while you have to wait 0,7 seconds for only 4 more.
that this happens is somehow unavoidable. if they should have silenced it? no idea. the runtime has softstart for DSP now, but this external obviously not.