Hey all, can anybody help me out with enumerating all of the possible ways that my plugin could be communicating to the host (Live 10) that a new parameter value is/needs set?
Something my editor is doing randomly (maybe 50% of the time) causes live to hit the
static void setParameterCB (VstEffectInterface* vstInterface, int32 index, float value) callback twice in immediate succession, first with the value I wanted to set, then with the value my parameter was at beforehand. So my parameter change is immediately clobbered with the old value. This only happens when the parameter change comes from Live (i.e. automation).
I’ve dropped breakpoints just about everywhere I can imagine (all over the VST_Wrapper, AudioProcessorValueTreeState, AudioProcessor::Parameter, you name it), and none of them get hit in this scenario where Live sends my plugin a parameter change and then immediately sends another one. I’m sure, however, that my editor is to blame, because I can never reproduce this when the editor is closed.
Unfortunately these calls from Live come on a thread that has no valuable stack trace, and I can’t find the instance where my editor/APVTS convinces Live to send the change again. Where can I possibly look here??