Updated Monday, Feb. 24, 2020: The next release of Premiere Pro and Adobe Media Encoder will default to “New World” ExtendScript environments with “Old World” behavior remaining accessible as-needed. Find additional details here.
Upcoming changes will affect all ExtendScript integration and CEP panels within Adobe Premiere Pro, After Effects, Audition, Media Encoder and Prelude.
We’re sharing this information as early as we can, to provide maximum response time for our partners. Here’s what we’re doing, and how partners can respond.
Sounds nice, eh? Here’s how we get there.
Two modernization efforts underway within Adobe impact all ExtendScript and CEP integrations.
The new engine is off by default; unless you specifically request it, your integration’s behavior is unchanged.
The new engine does an uncanny impersonation of the old ExtendScript interpreter; we call this “New World scripting”.
Due Date: As of our MAX 2019 releases, use of the New World scripting engine will become “opt-out”: The new engine will be used by default, with the old one available via configuration, for emergency use only.
What you can do, today:
Test your current, shipping integration in New World scripting, as soon as possible.
Also, please join our Integration Engineering pre-release program, where we’ll be discussing such issues and posting any builds containing fixes for New World issues. You can also report issues to me directly.
Effort 2: Replace CEP extensions with UXP plugins
All Adobe applications are replacing CEP extension support with UXP plugin support; schedules vary by application. No CEP removal is currently scheduled.
The video applications are already integrating UXP, and plan to deliver initial UXP plugin hosting in the first half of 2020. This initial support will likely not include a full 1:1 replacement for ExtendScript API calls, but will allow you to get started with the UXP version of your integration.
What you can do today:
We know these Adobe-imposed architectural changes require time and resources from our partners. We’re grateful for your efforts!
For more stories like this, subscribe to our Creative Cloud Developer Newsletter.