After Effects plugins removed in 5.1

[Jeremy Garchow]

Also, concerning the M100 AE plug in, I’m not sure that Adobe made that as it came with the M100 install disks. I bet that was M100 coding, not Adobe coding.

Automatic duck is completely worth every penny. It pays for itself in the time it saves in doing stuff the hard way.

Jeremy

[Walter Biscardi]

[JeremyG] “Also, concerning the M100 AE plug in, I’m not sure that Adobe made that as it came with the M100 install disks. I bet that was M100 coding, not Adobe coding.”

I believe you’re right because I remember M100 made a big deal about that when it came out. I also remember lamenting about the loss of that feature when I made the jump to FCP, and then Wes came along with his tool. It has saved me countless hours in After Effects.

Walter Biscardi, Jr.
https://www.biscardicreative.com

Director, “The Rough Cut”
https://www.theroughcutmovie.com

Now Posting “Good Eats” in HD for the Food Network

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters

[Walter Biscardi]

[Dave LaRonde] “AE is on a LOT more platforms than FCP, and if Apple is not going to play nice with Adobe, perhaps Adobe ought to take matters into is own hands. I’ll ask what people think about that on the AE forum; I can see it’s a fruitless discussion here.”

Hey, making it completely free to move FCP projects to AE would be great.

But just think about what you’re asking. You’re asking Adobe to make it easier for After Effects to work with a competing NLE. If you look at the Adobe Suite, I’m pretty sure Premiere works seamlessly with AE. If I were Adobe, I would keep it that way.

Walter Biscardi, Jr.
https://www.biscardicreative.com

Director, “The Rough Cut”
https://www.theroughcutmovie.com

Now Posting “Good Eats” in HD for the Food Network

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters

[Pierre Jasmin]

”
Probably because AE is not a universal app. Adobe has stated it will not support a Universal app until the next rev of the app which will most likely be 2007.”

FALSE

You can do Universal Plug-ins without Adobe doing anything right now. An host does not need to know what Adobe will do, this only applied to the X-Code support (the Apple compiler) and how-to is publically available since After Effects 7 release on january 17 (so an host can turn off the CPM wrappers). So it’s ridiculous Apple crap! It’s half a day of work to support AE plugins in a macIntel compile.

Pierre
RE:Vision Effects

[Bj Ahlen]

Relief!

Thanks for the update.

[Pierre Jasmin]

Relief in what sense? It’s not working in FCP for what appears to be marketing reasons (my opinion).
I am saying it’s easy for an host to support, not that FCP has plug the necessary hook so it can work.

Pierre

[Bj Ahlen]

Ouch, I misunderstood what you wrote.

Apple can certainly be sneaky, and this could be part of a tit-for-tat with Adobe because they put such an extremely low priority on the Macintel port.

It would seem hard to believe that Apple would have been able to put together an AE killer in time for NAB though, and I would have to think that Adobe will change their minds and accelerate the AE port.

Sigh.

[Tom Wolsky]

Peter,

Have you been able to test an old project that may have AE plugins in the project. What happens when you open it with the UB version of FCP?

Thanks very much.

All the best,

Tom

All the best,

Tom

Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 2 Editing Workshop” Class on Demand “Complete Training for FCP5” DVD

[Peter Wiggins]

Tom,

All I have tested so far is if try to open a FCP PPC project in FCP (intel) that has AE plugins in it, it will open but will say it can’t find the plugs & do you want to find them in another directory. You also get that red screen.

So if you do have an old sequence you can open the thing up & remove the filters & work on it fine.

I will get round to trying to install Sapphire on my MBP later.

Hope that helps!

Peter

Free Motion Templates

https://www.peterwiggins.com

[Pierre Jasmin]

Let’s hope there will be a 5.1.1 patch to download soon which addresses that and it’s just a side effect of Steve Jobs wanting a Universal Binary shipment by end of march as he publically announced that.

Although I say that MacIntel port is easy for an host like FPC, this assumes the host already supports Mach-O AE plugins, and that part might be a bit more work as users expect on PPC that their old plugins would still work, and that usually cascades into testing… and this information was only made available by Adobe 2.5 month ago, probably not fast enough for Apple to handle.

So the hope is a quick downloadable 5.1.1 patch:

1) That supports PPC side Mach-O versions of AE compatible plugins which would make the Mach-o recompiled plugins run about 30% faster.(https://www.revisionfx.com/pressreleasesfolder/pressrelease62.htm )
2) That supports MacIntel recompiled AE plugins, for which there is no dependance on knowing what Adobe will do since the plugins that ship with AE itself don’t work in other applications then AE and Premiere anyway.

In retrospect and now in theory Apple could have supported Mach-O PPC AE plugins a year ago (the PPC part of a Universal binary), the only issue would have been that third parties would have needed to rebuild the plugin package which they have to do anyway, and which would have been a better outcome then no support at all. To be clear the AE plugin format is just a set of definitions, it’s not like Quicktime and things like that as there is for Apple no reliance on a compiled component provided by Adobe etc.

Pierre