schlam

Hello, I have a patch that store with pattrstorage about 1000 parameters from a live.Set

When I interpolate all the values, there is no real problem.

Between the slider controlling the interpolation value and [pattrstorage] I have a speedlim 60.

If I move the slider quickly from 0 to 1. : no problem

If I perform a "stress test", moving the slider up and down very quickly a lot of time, the values continue to move up and down during few times as the value were "queue"..

Hello, I have a patch that store with pattrstorage about 1000 parameters from a live.Set
Everything works quite well.
When I interpolate all the values, there is no real problem.
Between the slider controlling the interpolation value and [pattrstorage] I have a speedlim 60. 

My question :
If I move the slider quickly from 0 to 1. : no problem
the speedlim do the job : no lag.
If I perform a "stress test", moving the slider up and down very quickly a lot of time, the values continue to move up and down during few times as the value were "queue"..
is there a way to avoid that ?

Hello, I have a patch that store with pattrstorage about 1000 parameters from a live.Set
Everything works quite well.
When I interpolate all

interpolation-question-with-lots-of-parameters

You could test [qlim] instead. speedlim creates high priority output.

(aargh.. "qlim" object is not in the list of related objects when you open the speedlim help...)

(aargh.. "qlim" object is not in the list of related objects when you open the speedlim help...)
Now I know.


interpolation question with lots of parameters