'Vertical' automation data not registering unless plugin GUI is open

[chagzuki]

This is a strange problem, and I'm specifically experiencing it with Phase Plant. I haven't yet tried replicating it with other plugins, so it's possible that it's a Phase Plant issue.
I'm getting the same behaviour in Mac OS Big Sur and Sonoma, with VST 2 Phase Plant 2.0 (a year old) and the new version. And with Waveform 11 and 12 in native and rosetta modes.

There's two ways of creating an abrupt/instant jump with automation: one can create two nodes of different values with no curvature and have them aligned in time (connected via a vertical line), or one can use a singe node and push the curve to an extreme such that it creates a 90 degree angle. I've found that with either of these methods, Phase Plant doesn't register the 'later' value unless the GUI is open. And even if one reduces the curvature a little, the moment that the curve goes vertical (or near vertical) the automation stops affecting the plugin. Unless the GUI is open, and then it works without problem. If one shifts nodes such that they're not fully aligned, i.e. if there's something of a ramp, the issue goes away. But often an abrupt change is required, and not a ramp.

I'll have to see if this is happening with plugins other than Phase Plant, and see if it happens with the AU and VST3 version.

Has anyone else noticed behaviour of this kind?

[Maarid]

it is quite possible that these are the difficulties of a particular plugin, I used automation to create glitches and the switching conditions were only on/off, which accordingly worked normally. But for example fabfilter pro q ignores any attempt at automation in any form, I just had to put up with it

[chagzuki]

it is quite possible that these are the difficulties of a particular plugin, I used automation to create glitches and the switching conditions were only on/off, which accordingly worked normally. But for example fabfilter pro q ignores any attempt at automation in any form, I just had to put up with it

The weird thing is that this particular edit used to play without issue, and I actually have an older MacBook which I thought was left in a safe configuration for older projects, but the same problem occurs there, and I can't think what system change might have introduced it.

[chagzuki]

I've just created a test edit with the same plugin, Phase Plant. The behaviour is recreated with a VST2 plugin, but doesn't occur with VST3.