Yep, VSTGUI 3.x Sorry for not being more clear.mystran wrote:Oh ok. Sure. I don't even have such a method anywhere, so I guess this must be something specific to VSTGUI?AdmiralQuality wrote:Note that that's editor::setParameter I'm talking about, not effect::setParameter.mystran wrote:Well, doing that will fix any race conditions. You can still get potential priority inversions, though Windows not being RTOS those will get resolved eventually anyway (though sometimes after some audio drop-outs).The only concession I make to multithreading in VST plug-ins is to put a critical section around editor::setParameter() and editor::close().
I'm going to make a test plug-in to see if I can get effect::setParameter called during effect::process. If I'm wrong about this I don't want to be spreading disinformation. (Of course, an editor is free to call effect::setParameter, though it should usually be calling effect::setParameterAutomated Not sure offhand if that doesn't just immediately fire setParameter as well, probably does.