/t5/after-effects-discussions/new-signing-requirement-for-ae-and-pr-extensions-as-of-25-2-0/td-p/15300204May 01, 2025
May 01, 2025
Copy link to clipboard
Copied
It appears that a recent AE update changed requirements for plugins to be run while this is a marginal win for anti-piracy (it requires pirates to self sign their bundles, or write an installer to do so, but let's face it most pirates are not buying luxury computers), it would mostly seem to break older plugins which for various reasons have decided not to sign. Since most of the effected plugins are free (The best reason not to sign a bundle is because it costs $99 a year) there are probably a few useful and widely used plugins that have been bricked. Is there a place this change could be documented? is there a place the error codes in the plugin loading logs are documented?
I dropped Mac support due to this. Apple is becoming an increasingly closed off system and they've taken all the fun out of plug-in development by having to notarize, certify and what-not, as well as dish out an annual fee.
I'm sure there are other developers like me that will feel it's simply not worth their while to jump through hoops to create an app for Mac.
That's a total shame! I'm currently writing a very simple PKG installer with a simple post install script that will ad hoc sign the plugin for the users computer. If this interests you let me know. This is bad form, but I don't really care as long as more people have access to free, useful tools. The pain of the AE and PR development platforms has really made me consider writing my own video compositor.
2
Replies
AdChoices