Inspiring

Answered

Premiere Pro 15.4 breaking plugins

Forum|Forum|4 years ago
July 20, 2021
7 replies
10930 views

Just updated to 15.4 on several systems, and it looks like it is causing problems with various plugins. Already heard some people talking about issues with Red Giant, but I'm having issues with my own plugin as well.

On launch, the plugin looks like it starts to load, but nothing shows up in the panel itself. And if I close the panel and re-launch it, I don't even get the plugin panel to come up until I close and restart Premiere Pro.

Tried taking out pretty much everything in my index.html file except a single text field, but still nothing. So I think it has something to do with a change to what is needed in the manifest file perhaps? What is odd is that it seems to load just fine on my M1 Macbook, but not on my desktop PC.

Anyone else seeing similar issues?

SDK

This topic has been closed for replies.

Correct answer PugetSystems_Matt

Update on this: turns out it was because Premiere Pro (and After Effects) moved to CEP 11. Shoudln't affect packaged plugins, but since I am doing development, I had to get into the registry and add a "PlayerDebugMode" key under CSXS.11 .

So, no issue with Premiere Pro, I just wasn't aware that Ae and Pr moved to CEP11 with this latest release.

D

defaultmjbfgzt6py7l

Participant

Can anyone help me ... my red giant plug ins show in AE but not PR I tried everything even called geek squad then called adobe and they said to just go back to the 15.4 version but I think it's something else I can do so I can be on the latest software

R Neil Haugen

Legend

Odd that they show in Ae but not PrPro.

Current PrPro is 15.4.0.

Current Ae is 18.4.0.41

Neil

Everyone's mileage always varies ...

Bruce Bullis

Community Manager

Is your installation of PPro, ARM-native?

nicos42976418

Participant

Same issue here, just updated on a M1 Macbook and have lost access to my plugins (Film Impact). I've tried a roll back to 15.2 and it sees them again, annoying though as i need the 15.4 compatability.

Anyone got a solution?

Cheers,
Nico

Bruce Bullis

Community Manager

You're hitting a different issue; the initial report (in this thread) was about extensions, not plug-ins.

If you're running natively on ARM, you will need updated ARM-native Film Impact plug-ins; happily, Film Impact were among the first to port their plug-ins to ARM>

nicos42976418

Participant

Thanks for the response Bruce, turns out my legacy Film Impact plug-ins are no longer supported (by FI for ARM processor).

Looks like I have to switch to their subscription model to maintain compatability.

P

PugetSystems_MattAuthorCorrect answer

Inspiring

Update on this: turns out it was because Premiere Pro (and After Effects) moved to CEP 11. Shoudln't affect packaged plugins, but since I am doing development, I had to get into the registry and add a "PlayerDebugMode" key under CSXS.11 .

So, no issue with Premiere Pro, I just wasn't aware that Ae and Pr moved to CEP11 with this latest release.

jondrometa

Inspiring

Thank you for this solution! I was experiencing the same thing for our internal extension (in development mode) and this resolved the issue for us as well.

Also: Make sure your extension is running NodeJS version 15.9.0 or higher, as mentioned here on Adobe's CEP Resources page.

1. Update the Node Modules: CEP 11 works with NodeJS 15.9.0 and Node-WebKit 0.50.1 versions.

If extensions were build on older version of NodeJS there can be cases where these extensions may not load in CEP 11 due to incompatible node modules.

In such cases, the node modules need to be updated using NodeJS version 15.9.0 or higher.

R Neil Haugen

Legend

Anyone with plugins should ALWAYS check with the plugin maker for updates when they update PrPro. Period.

For those with RedGiant/Maxxon plugins, you need to update via your RedGiant/Maxxon Application manager, and then all is well.

Neil

Everyone's mileage always varies ...

davef43726944

Inspiring

No, you don't ALWAYS need to. It's pretty easy to update PP, check if things work and then roll back to an earlier version if they don't.

R Neil Haugen

Legend

Well ... if you don't mind finding out when it doesn't work, hey, that's fine.

I like to just have things work when I get started ... so if I do update PrPro/Ae/Resolve, I do always check for updates for plugins before starting the app. So like, this morning, my RedGiant stuff was all available immediately as I sat down to work.

So ... no, you don't have to ... but it might be a wise thing to check ... 😉

Everyone's mileage always varies ...

Kevin-Monahan

Community Manager

Hey Matt,

Thanks for the message.

Edit: appears the application manager needs to be updated. See Neil's response.

Regards,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

bbb_999

Adobe Employee

Existing extensions should continue to load.

bbb_999

Adobe Employee

Hi Matt,

I think you mean (JavaScript-based) extensions, not (C++-based) plug-ins...correct?

We've tested numerous internal and 3rd party extensions in 15.4, without issue, but if you could send me your extension directly, we'd be happy to investigate further.