minning.de - Stefan Minning: CG Artist and Developer

  • Home
  • About
  • Portfolio
    • Videos
    • Demo Reel 2009
    • Galleries
    • A Night at the Cathedral
    • Archviz
    • Stuntman 2: Ignition
    • Paraworld
    • Frontlines: Fuel of War
    • Mark Antony
    • Now that takes the Biscuit
    • Sleeping Dragon
    • Bagel 2
    • Miscellaneous
  • Software
    • 2D Plug-ins
    • Atlas
    • Celulight
    • Edgar
    • Floodgate
    • Generator
    • Normality
    • Occlusionist
    • 3D Shaders
    • minShaders
    • Physical Shaders
    • Reptile Shaders
    • Toonkit Shaders
    • Tools
    • CPULight
  • Journal
    • Journal
    • Latest Entries
    • Categories
    • Artwork
    • Development
    • Downloads
    • Making of
    • Personal
    • Tutorials
    • Video
    • Website
    • Search
  • Contact
  •  
  • 日本語
November 2 2009

A plug-in developer's thoughts on After Effects CS5 being 64-bit only

64-bit, adobe, after effects

Just read a post by Michael Cole­man (prod­uct man­ager for Adobe After Effects) con­firm­ing that Adobe doesn’t intend to make it pos­si­ble to run 32-​​bit plug-​​ins in the upcom­ing AE CS5.
The new soft­ware will be 64-​​bit only and requires all third-​​party plug-​​ins to be upgraded by their respec­tive devel­op­ers to the new architecture.

Note: Michael Cole­man has taken the time to respond to my con­cerns in the com­ments.

That in my opin­ion is a mis­take if I’ve ever seen one.

Don’t get me wrong — I applaud the fact that After Effects is mov­ing to a 64-​​bit archi­tec­ture. It’s with­out doubt the way of the future and the com­peti­tors are already there and have been for a while. Per­son­ally, I’m ready… I’ve been run­ning 64-​​bit oper­at­ing sys­tems exclu­sively for years.
How­ever, Adobe needs to remem­ber what AE’s strengths are: In my opin­ion, and that of many other users, a great part of After Effect’s appeal lies in the vast amount of plug-​​ins on offer — free and com­mer­cial.
If that is changed over night, one of the main rea­sons to choose Adobe’s soft­ware over Nuke or Fusion dis­ap­pears over night as well.

A 64-​​bit com­pos­i­tor with­out the right tools to make use of it isn’t worth much, and let’s face it: Bare After Effects sans third-​​party plug-​​ins doesn’t cut it, 64-​​bit or not.

Now on the Mac side the users may be used to get­ting shafted by plat­form tran­si­tions every other year, but Win­dows users have come to love the lux­ury of being able to run obscure plug-​​ins more than 10 years old in some cases. I know many peo­ple that rely on them for their daily work.

It’s been shown in the past that third-​​party devel­op­ers take their time to upgrade plug-​​ins, if they do at all. The main rea­son being that devel­op­ing upgrades to new archi­tec­tures costs time and money. How­ever, they can’t charge their pay­ing cus­tomers for updates like these with­out gen­er­at­ing sig­nif­i­cant amounts of ill will. Def­i­nitely not a nice sit­u­a­tion to be put in as a devel­oper and one of the rea­sons I don’t sell my soft­ware to the gen­eral pub­lic.
In the case of for-​​hire/​freeware devel­op­ers like myself, there’s no incen­tive to spend the time devel­op­ing an update at all unless I also switch to the new plat­form, which under the described cir­cum­stances I don’t see myself doing.

I think this is some­thing Adobe def­i­nitely needs to reconsider.

There should be a tran­si­tion period where 32-​​bit plug-​​ins are sup­ported seam­lessly along-​​side the (hope­fully soon to be updated) 64-​​bit ver­sions.
It’s tech­ni­cally fea­si­ble: Just look at pro audio soft­ware (Sonar, Reaper, etc.). Those devel­op­ers clearly under­stand the value plug-​​ins have to their cus­tomers and have made the effort to ensure 32-​​bit plug-​​ins will work seam­lessly in their 64-​​bit environments.

If upgrad­ing to CS5 means los­ing (in)valuable plug-​​ins/​waiting ages for updates that may or may not arrive one day, many users are stripped of a sig­nif­i­cant invest­ment and might just go ahead and think “Oh well, might as well go with Nuke then if I’m forced to start from scratch any­way”…
I know I’ll be hard pressed not to take this per­fect oppor­tu­nity to ditch After Effects, and I guar­an­tee you I’ll take my home-​​grown plug-​​ins with me wher­ever I hap­pen to end up.

Adden­dum

Just to make it clear: I’m not com­plain­ing as a com­mer­cial plug-​​in devel­oper; I’m com­plain­ing as a user and cus­tomer of After Effects.

Frankly, I couldn’t care less about the extra work it would take to upgrade my own plug-​​ins to 64-​​bit — in fact, it’s prob­a­bly not a big deal in my case and port­ing to Nuke’s OpenFX for­mat would actu­ally be more work.
But I have no vested inter­est in AE devel­op­ment — I don’t make money doing it. I also have no ties to After Effects beyond the finan­cial invest­ment I have made in the soft­ware and third-​​party plug-​​ins. If Adobe’s deci­sion to cut sup­port for 32-​​bit plug-​​ins means I lose that invest­ment, you can be sure I’ll take a good look at the alternatives.

If I choose to switch plat­forms over this deci­sion then so be it. It just means that there will be no 64-​​bit updates to my plug-​​ins for AE… noth­ing is lost for me per­son­ally.
Whether this poses a prob­lem for any­one else out there I don’t know.

  • ‧
  • Permalink
after effects bagel 2 beta cel shading celulight cgtalk demo reel download normality npr NTTTB panda pendulum personal plug-in rant review shader short film site sleeping dragon studio lampion wordpress  
Recent posts
  1. 06/02 Quo vadis, Adobe?
  2. 05/02 Normality downloads are down
  3. 18/01 Normality will not run in After Effects CS5
  4. 07/12 Hey Australia...
  5. 15/11 Generator
  6. 05/11 A land Down Under


Copyright © 2004 – 2010 Stefan Minning & minning.de. All rights reserved.

Return to top

RSS Feeds