Activity › Forums › Adobe After Effects › Upcoming CS5 will be 64 bit, no port to 32 bit Plugins (Customer Service Comments)
-
Upcoming CS5 will be 64 bit, no port to 32 bit Plugins (Customer Service Comments)
Ed Bangle replied 16 years, 4 months ago 14 Members · 17 Replies
-
Michael Coleman
January 4, 2010 at 8:33 pmMartin,
Do you know of any specific developers that are not planning on creating a 64-bit compatible version of their plug-ins? The developer’s blog that you refer to (https://www.minning.de) indicates that it would be ‘no big deal’ to convert, should he choose to do so.
If you do know of any, I’d appreciate it if you could send them my way and we can do what we can to encourage them to move forward. I haven’t talked to any, but if you have specific info, please let me know.
The AE team knows you can’t live without all the great plug-ins to After Effects, which is why we have taken additional steps to make this as easy as possible for our 3rd party developers. This includes early availability of our 64-bit SDK and access to members of the After Effects technical staff for guidance if necessary. This means that developers can start the conversion now. The ones I’ve talked to are either going to be ready at the time the next After Effects ships or shortly thereafter.
Also, Adobe is typically very tight-lipped about what’s coming down the road. We’ve chosen to make this 64-bit information public and open in order to accelerate the transition. Of course, the down side is that it tends to cause a bit of concern, as has been expressed in this thread. In this short post, it’s impossible for me to communicate the extents of what goes into a decision like this. In the end, we felt that moving forward with most advanced After Effects possible is better than the alternative. For example, I’m sure that if we had to delay 64-bit on the mac another year or two, this would be much more painful for our customers. I talk to a lot of customers and almost universally, people want us to push the product forward faster.
In any case, consider this like ripping off a bandaid. It’s better to do it quickly.
—
Michael Coleman
Product Manager, Adobe After Effects
https://blogs.adobe.com/keyframes/ -
John Sullivan
January 5, 2010 at 7:35 amI for one know I won’t be taking the plunge to get CS5. It should be obvious to dedicated users as to why. Much of it has already been said at this point so I won’t bother going into that.
If you look at the transition we have seen in the video world, going from SD to HD, you could see it coming and you knew without a doubt how hard it would hit before it actually did. There was fair warning to start working towards HD at some kind of pace. Many are still working in SD with the intention to migrate to HD. They are the procrastinators and the lovers of the status quo. But its not too late for anyone.
Then look over at Adobe and their “grande” ideas. Turning their backs on technology that is still front and center of the consumer world is equal to turning their backs on consumers. They candy coat their new ideas. Imagine a new President of the United States trying to change the liberties of America and finding some clever scheme to trick citizens into “wanting” the change. We saw this with the last “prez”. But I would like to think that consumers aren’t so dumb. Fairly intellectual people edit video. Thinkers. The kinds of people that would look at Adobe and say, “How dumb do you think I am?”.
To tell me that all my 32-bit plugins will not work is like coming into my house and stealing my software, and then trying to sell me something.
NADA.
WON”T HAPPEN.
I will be a CS4 user for some time. And it might just take some clever hackers to fix the bugs, since Adobe clearly will not. You couldnt ask for a better product without going with a different company. That’s why I love Fusion.
-
Joe Moya
January 5, 2010 at 2:19 pmNothing personal… but, I think the phrase is this…”don’t pee on me and tell me it’s raining”….
…the problem isn’t that everyone knows about Adobe’s decision to no longer support 32 bit… the problem eventually comes down to simple economics. From Adobe’s standpoint the cost of conversion is being placed squarely on the backs of the customer and the third party plug-in developers.
It is not a question of whether or not the third party plug-in developers know about the is 64bit conversion ONLY road Adobe has choosen to go down… but, rather the question should be asked, “Do you know of any specific developers that are planning on creating a 64-bit compatible version of their plug-ins for free?” I doubt it (nor do I expect it)… and, so the fundamental issue is still the same. The cost of this lack of 32 bit compatability is being transferred from Adobe to it’s customers and developers… end of story… no need to sugar coat this fact. I don’t see how it is difficult to communicate this simple fact (even in a short post on a AE forum).
All this being said, I am happy to see Adobe communicate this key fact beforehand. It gives me and it’s customer’s the opportunity to evaluate my next upgrade in system applications. Which in code means this… since I am going to fork over a significant additional cost per station (because of lack of 32 bit compatibility). Then, the question becomes, “Why not just scrap Adobe applications all together and go with another compositing software?”
In the end, this decision will come when we look at stability of the applications and it’s relative costs. In that respect, 64bit only application may save Adobe important development costs but may at the same time reduce revenue.
When I see these sort of decisions come into play… I can almost always find the accountants (or, the accountant mindset) running the business instead of the sales and marketing departments. Such decisions tend to be simple and shortsighted. It is always easier to cut costs than to sale more. It also tends to have negative implications to it’s image and ability to market the products that keep the revenue side with a positive growth rate. At that point, enter the spin-doctors of marketing…. and, the resulting “kick me” sign pinned on the back of the Adobe customer.
As for the band-aid… exactly who’s skin is being ripped off? Adobe customers already know who is doing the ripping and who will be doing the screaming. I really wish Adobe would at least kiss the boo boo with a significant cost reduction compensation or rebate system for upgrading plug-ins to a 64bit application.
So,… Adobe… why not implement a “proof of purchase” rebate system for those who have to upgrade to 64bit plug-ins and prove you do have the customer’s thoughts in mind (…but, shhh… just don’t let the accountants find out)?
-
Walter Soyka
January 5, 2010 at 3:43 pmI am really happy that Adobe is making After Effects 64-bit. It will make a huge difference in my studio’s workflow and productivity on HD and higher-res projects.
I’m also glad that Adobe is making CS5 64-bit-only, because it will force developers to update their plugins to stay current. If there were a 32-bit mode, I think you’d see fewer plugins go 64-bit, and the entire transition would be much longer and much more painful.
I really can’t understand all the griping on this thread — if you don’t think the new features are valuable for your work, then don’t upgrade! My studio is still on CS3, and we are still producing great work and keeping our clients happy. I’d rather see Adobe pushing AE and its entire ecosystem forward so I can work better; I’d hate to see them hold back development for any reason. I didn’t see enough value in CS4 to justify the upgrade costs, but upgrading to CS5 is a no-brainer for me, for 64-bit AE alone.
My thanks to the Adobe reps for their thoughtful responses in this thread, as well as to the other posters who are keeping the discussion civil.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
Paul Uusitalo
January 5, 2010 at 7:22 pmWhat specific problems are you having with CS4?
You’ve updated to 9.0.2, correct?
Paul
-
John Davidson
February 26, 2010 at 10:31 pmMichael,
Sorry to weight in on a older post, but has your team considered completely revitalizing the plug-in process? The major caveat to any new installation of an adobe product lineup for me is the excessive amount of time, effort, and homework involved in installing not just the programs, but the plugins. Invariably I end up losing plugins that sometimes cost as much as the program itself! Wouldn’t it be fantastic to have a plugin manager similar to the app store? Developers would complain forever, but this is a concept that works. Suddenly, I’d know when Zaxwerks is updated, I’d be able to redownload all my plugins automatically on a fresh install, and gosh, I’d be able to write a review if a plugin sucked. There have been many times that I knew my main system needed a clean install, but Adobe products specifically limit my ability to do this – and crush my desire to even try.It doesn’t even have to be an exclusive installation process, the old installation format could still work, but the ‘new’ process would be so much sexier for plug-in developers. Honestly, finding plugins for AE right now is bizarre when you think about it. Finding and researching plugins for After Effects should be feasible from within the application itself.
Has there been any talk of something like this?
-
Ed Bangle
March 16, 2010 at 2:34 amI have a New Dell Precision Workstation running true 64 bit Windows 7. Got CS5?
Please let me know how to accomplish testing the software.
I have been waiting since I bought a 64 bit digital computer in 1997. Man, what a waste. It has taken more than 10 years but I guess it is worth it. The digital machine was emulating adobe software and running on a P3 500 mhz processor. Yuck!.
I appreciate your input on an ETA.
ed
Reply to this Discussion! Login or Sign Up