Also keep in mind that when Pro Tools loads your plug-in, it will send to it BOTH the values of automated parameters and the “blob” of StateInformation data.
I don’t remember in which order, but if the two don’t represent the same plug-in state, it’s possible that the one that comes last determines the state of the plug-in and that’s different from the state you would expect.
If you add DBG statements to have debug printouts in your code, IIRC you can see their output even using the non-developer version of Pro Tools if you start Pro Tools from the Terminal and watch the same Terminal window for their output.
So after loading the preset, the audio doesn’t seem to be affected by the parameters? I guess that would be in processBlock, but you’d have to get debugging to figure it out. As @yfede said, you can still use DBG statements without the developer version of Pro Tools, you could also probably reproduce with a VST version in a more debugger-friendly DAW/Plugin Host.
@railjonrogut I tend to agree but testing all other formats VST, AU on both the platforms PC and Mac, it was only observed in AAX plugins on both PC and Mac.