Skip to main content
Inspiring
November 24, 2025

PF_OutFlag_NON_PARAM_VARY makes parameter animation not work with Adjustement Layer

  • November 24, 2025
  • 1 reply
  • 80 views

Hi !

 

I am developping an After Effects / Premiere pro plugin with the After Effects C++ SDK. My plugin effect evolves dynamically throughout the sequence duration. The entire point of this effect is to be able to animate the parameters.

 

My issue

 

On Premiere Pro, everything works well until the effect is applied to an Adjustement Layer and I try to animate the parameter. When I do so, the plugin will take the first value encountered at the first frame of the Adjustement Layer, and will use it for the entire sequence.

 

I investigated a bit and realised that the issue was coming from the PF_OutFlag_NON_PARAM_VARY flag. I used this flag initially to make my effect work with still images, as recommanded in the documentation. Without this flag, everything works well, but for still images, the plugin would use the first value encountered by the image sequence for the whole sequence.

 

To summarize :

- With the flag, my plugin works for still images, but I can't animate on Adjustement Layers.

- Without the flag, I can animate parameters on Adjustement Layers, but the plugin does not work on still images.

 

My question

Has someone already encountered this issue ? To my knowledge, the closest topic to my issue was this Adobe thread. But that was seven years ago, and again, the animation was working without the PF_OutFlag_NON_PARAM_VARY flag...

 

Is there a workaround for either of these :

- Make a dynamic effect work with still images without the PF_OutFlag_NON_PARAM_VARY flag ?

- Make the parameter animation work on an Adjustement Layer despite the PF_OutFlag_NON_PARAM_VARY flag ?

 

Thanks in advance for anyone that can help on this issue !

1 reply

FxFactory
Inspiring
November 24, 2025

If your plugin animates anything at all "on its own", meaning that the animation is not linked to a parameter that changes over time, that flag should be off. It is very rare (at least for me) to develop a plugin where that flag can ever be on.

 

I think it is important to understand that a parameter may still be driving your animation, e.g. "Do this for X seconds" where X is a slider, but AE may see that slider remain at a fixed value, e.g. 5 seconds, whereas your plugin is animating something within the scene faster or slower depending on that value. Compare this with a plugin that truly only animates everything in a direct link to a parameter, in which case the animation is tied to keyframes that are "visible" to AE and as such AE will correctly re-render each frame as opposed to pulling them from the cache, thinking the output is static. HTH!