> whilst practically speaking often true, this is actually not the case. w.r.t. AAX: during parameter automation events that involve a continuous change (e.g.,

> whilst practically speaking often true, this is actually not the case. w.r.t. AAX: during parameter automation events that involve a continuous change (e.g., a linear increase in gain), the process block size is reduced to 64 samples (if i recall correctly), and parameters are interpolated by the host and fed into the processor as fixed values for that time period. it means that it's not possible to answer the question: "at sample n, what is the value of this parameter?" This is correct if you implement parameter events naively (i.e. following the documentation!), but there's a way around it to get per-sample events. The unfortunate thing here is that it's not possible to talk about the protocol openly, AND a lot of devs use JUCE (or whatever wrapper) which doesn't support AAX's capabilities in this area. The bigger issue here is that VST3 doesn't pass MIDI events (CC/RPN/NRPN) directly to/through the plugin, which is a major hassle if you're doing anything that heavily relies on those facilities like scripters for orchestral plugins.