Skip to main content
FxFactory
Inspiring
December 8, 2025

Premiere Pro + AE Plugin SDK: Premiere doesn't support PF_WindowUnion->PF_ItemWindowInfo->port_rect

  • December 8, 2025
  • 3 replies
  • 150 views

Premiere Pro doesn't support the same layout for the PF_EventExtra structure when invoking plugins based on the AE SDK to handle events in teh Layer or Comp windows.

 

In After Effects, by virtue of uncommenting a macro in the SDK headers, plugins can access the context-specific PF_WindowUnion when processing events for the Layer and Comp windows. Crucially, this gives a plugin access to the PF_ItemWindowInfo->portRect member, the only sanctioned method to know the current viewport coordinates.

 

In Premiere Pro, if a plugin attempts to access that same structure, it is clearly filled with the wrong information, suggesting that the PF_USE_NEW_WINDOW_UNION is indeed After Effects-only.

 

Lacking this vital piece of information, plugins in Premiere Pro are forced to use a rather unorthodox approach. When handling a draw event, the PF_DrawEventInfo->update_rect member appears to containt coordinates for the viewport, which need to be cached and reused when processing mouse input. This is not ideal since it requires sharing state between drawing and event processing. It relies on the assumption that the update_rect is indeed always set to the entire viewport, something that isn't mentioned or guaranteed by the SDK. Lastly, it creates yet another situation where plugins have to be coded very different for two apps that presumptively share the same SDK.

 

Expected results:

Make Premiere Pro support the same PF_ItemWindowInfo structure. Get rid of that PF_USE_NEW_WINDOW_UNION macro that magically unlocks this SDK feature just in AE. Instead, document which version of your apps support it, specifically what version of Premiere Pro will begin supporting the same union to give plugins clean access to the current viewport.

 

 

3 replies

FxFactory
FxFactoryAuthor
Inspiring
December 8, 2025

...and while I thank you for taking a look at this so fast, I want to point out that all bugs filed today that relate to on-screen controls are linked to our most recent version, FxFactory 9. This is not a coincidence. This is the first version where we attempted to bring the same custom on-screen UI to Adobe apps as we currently provide in FxPlug and OpenFX (for Resolve).

FxFactory
FxFactoryAuthor
Inspiring
December 8, 2025

That is correct, this is a different issue (and more of a feature request than a bug report). But I wonder if you didn't mean to ask this question about a different bug also filed today:

https://community.adobe.com/t5/premiere-pro-bugs/premiere-pro-doesn-t-allow-dynamic-ui-changes-when-handling-parameter-value-changes-from-oscs/idi-p/15623930

 

Assuming you meant to comment on that issue... to the best of my knowledge Premiere is in fact generating PF_Cmd_USER_CHANGED_PARAM messages in response to a value change from on-screen event handling. The issue is just that if the plugin attempts to change UI while handing that command, such changes are just ignored by Premiere.

IanB_360
Community Manager
Community Manager
December 8, 2025

Hi @FxFactory 
This would be a separate issue from the one you logged back in  November. Is that correct? sdk-ae-fails-to-call-into-third-party-plugins-with-pf-cmd-user-changed-param-for-sliders
Ian