Jakob / Cableguys wrote:We'd still have the problem of parameter values toggling back and forth. See my example in the very first post: the parameter might be moved by the user from 0.1 to 0.2 to 0.3, and will temporarily jump back to 0.2 when the host calls <setParameter> and echoes the parameter change, and then a little later again to 0.3.
When the GUI sets a parameter record a timestamp, current system time for example, and ignore any incoming changes for that parameter from the host unless they occur maybe 1 second after that. Essentially block host automation while the use has his hands on the control.
You could override SetParameter & SetParameterAutomated and have all the logic in there. You just need an extra array with the timestamp for each parameter.
In fact you probably dont need an array, just a single timestamp and parameter index, and just ignore the last changed parameter. The user cant move the mouse that quickly that you'd be likely to have more that one being wiggled in relevant amount of time.
Should work i think.