-
Plugin confusion PPRO/Aftereffects V1.5, 6,5, V2, etc..
Could someone clarify the state of plugins for PPRO and Aftereffects for me? Specifically:
* Are PPRO $ Aftereffects plugins exchangable, ie can be used by both programs on the same system? The ones I am interested in are Boris Red, Trapcode, Synthetic Aperture Color Finesse v 1.5.3, MagicBullet Suite v2.0, etc.
* Are 3rd party plugins Version dependant, ie works in PPRO 1.5 but not 2? I have already found two cases: Canopus ProCoder2 does not work in V2, and my capture card plugins (Snazzi) don’t either, not that they ever really worked).
* If the answer is yes to some and no to others, what is everyone doing? Running two systems, ie one system with let’s say AfterEffects 6.5 and PPRO 1.5, and another with the newer Production Suite softwares (V2&7) and the corresponding plugins that work? Seems nuts.I thought years ago that adobe made an API for plugins so these problems would not exist? What happenned?
Well, thanks for your thoughts and suggestions!
jigs in nepal -
3 Replies
-
The answer to all of your questions is that if the plug-in in question is dependent on a feature that is specific to one application or the other, or one version or the other, it may not function correctly in an app or version it wasn’t written for.
To break it down a little more, remember that while AE and Premiere have similar capabilities, they have different feature sets the plug-in writers may choose to take advantage of. Also, between versions, small changes may be made in the API that can break a plug-in. I know for a fact that happened on the Mac for Photoshop and AE because Mac has forcing all app developers to roll over to Mach-O.
I don’t know which of those specific plug-ins will work cross-app or cross-version. I think Trapcode may work, I’m almost positive Color Finesse won’t, and no idea on the others.
Adobe’s API does try to be pretty universal between the apps, but there’s enough specific differences between them that it won’t work in every case.
In regards to version-to-version problems, most plug-in writers will update their software for a new release from Adobe, so you can always get a patch or upgrade (though sometimes you have to wait a few months; most AE plug-ins are compatible with 7.0 now but there are a few stragglers).
-
great answer! thanks for that. do u know the dif betwwen prm and aex plugin extension? is one for premiere and the other a shared type between after effects and ppro?
also, it seems older plugins don’t know where to install properly in premiere 1.5.1. so i select the dir /plug-ins/us-en and sometimes they work and some don’t. is it a dir problem or just an incompatibility when they don’t show up in the effects folder?
well, i am sure this thread will help others!
jigs -
AEX is an After Effects plug-in. A plug-in with that extension was designed to work in AE, not Premiere. But because Premiere has a limited implementation of the AE API (or at least the parts that Premiere can do), some AEX files will work in Premiere.
PRM is a Premiere plug-in. I don’t think anything but Premeire can read them.
If your plug-ins are older than Premiere Pro 1.0, it’s very probable they won’t work. So much was changed with Premiere Pro from previous versions, the only plug-ins that are older and may still work would be AEX files.
Reply to this Discussion! Login or Sign Up