Activity › Forums › Adobe After Effects › AE cs3 and leopard – what concrete problem?
-
AE cs3 and leopard – what concrete problem?
Posted by Arnljot Bringedal on October 31, 2007 at 3:10 amIm on leopard – and have not found any problems with AEcs3 yet….
Do anyone know what the problem is? Have they stated concrete problems?
What can i expect?
Brendan Coots replied 18 years, 10 months ago 10 Members · 14 Replies -
14 Replies
-
Brendan Coots
October 31, 2007 at 5:02 amAs I posted in the Leopard warning thread, AE CS3 (and other apps) seem to be working fine for me. When a software company says they can’t guarantee “full compatibility” it could mean anything. So far, I haven’t found any problems.
That said, Adobe really, really needs to get their act together when it comes to staying fully compatible with Macs. This BS of patches and updates 6 months after major OS releases makes me wonder if they even remotely take their Mac user base seriously.
-
Darby Edelen
October 31, 2007 at 7:08 amWhat’s frustrating for me, is that they seem to know what the issues are and yet refuse to tell anyone…
What’s the deal?! Knowledge is power!
Darby Edelen
DVD Menu Artist
Left Coast Digital
Aptos, CA -
Rick Sebeck
October 31, 2007 at 1:49 pmI heard that Apple didn’t release Leopard, even to deveopers, until right before the launch last friday. So if Adobe didn’t have a copy for the last 6 months, how do you expect them to write upgrades?
-
Steve Roberts
October 31, 2007 at 2:27 pmThat matches what I’ve read, even before Leopard. Apple doesn’t share its information with Adobe as it did in the past. They’re more “competitors” than “partners” nowadays, it seems.
-
Darby Edelen
October 31, 2007 at 3:48 pm[Rick Sebeck] “I heard that Apple didn’t release Leopard, even to deveopers, until right before the launch last friday. So if Adobe didn’t have a copy for the last 6 months, how do you expect them to write upgrades?”
Apple did not have a final release candidate until about 2 or 3 weeks before Leopard’s release. Which I don’t think is a great timetable, but that’s the fact of the matter. So NOBODY, including Apple, had the shipping version of Leopard until 2 or 3 weeks ago.
Prior to that, members of ADC (Apple Developer Connection) had access to the latest Leopard betas, which functioned primarily the same as the shipping version. A few more bells & whistles that were removed, and a few more bugs were squashed before launch, but not that much changes at the core of a product in the last stages of a development cycle.
Even my Wacom Tablet had a “works with 10.5 beta” driver available yesterday when I checked for it.
Me thinks maybe Adobe should visit https://developer.apple.com/ more often.
Darby Edelen
DVD Menu Artist
Left Coast Digital
Aptos, CA -
Matt Callac
October 31, 2007 at 4:29 pmIf I were adobe I’d be pissed at apple. They have a whole new OS upgrade once a year. That’s a ton of work for a software company to go through (for free mind you) just so a portion of it’s customers can run the New OS. I’ll be honest, as a consumer it frustrates me, b/c out of all the stuff that comes into play with thes new OS’s only 10% of the stuff is actual improvements as far as OS functionality/ ram allocation stuff is concerned. The rest is just new fancy bells and whistles. As cool as the dashboard and widgets seemed, I honeslty don’t use them all that much. Expose’ on the other hand. That was handy.
-mattyc -
Joseph W. bourke
October 31, 2007 at 5:33 pmHere’s Adobe’s official take on it (6 pages):
https://www.adobe.com/support/products/pdfs/leopardsupport.pdf
Joe Bourke
Art Director / WMUR-TV -
Darby Edelen
October 31, 2007 at 5:44 pm[Mattyc] “They have a whole new OS upgrade once a year.”
I wouldn’t say “whole new.” Apple has had a ‘major’ updated more regularly than Windows, but they make a point of trying to maintain backwards compatibility as much as possible. Proof in point, AE and every other application I own has been working fine for me on Leopard. The only thing I’ve had to do thus far is update a driver for my Wacom tablet…
My bigger complaint is with any company (and this definitely includes Apple as well as Adobe) that is aware of some very specific issue(s) but refuses to let people know what it is.
Darby Edelen
DVD Menu Artist
Left Coast Digital
Aptos, CA -
Adolfo Rozenfeld
November 1, 2007 at 5:59 am[beenyweenies] “That said, Adobe really, really needs to get their act together when it comes to staying fully compatible with Macs. This BS of patches and updates 6 months after major OS releases makes me wonder if they even remotely take their Mac user base seriously. “
[Darby Edelen] “Me thinks maybe Adobe should visit https://developer.apple.com/ more often.”
This is from an Apple knowledge base article posted this week:
“On computers running Mac OS X 10.5 Leopard, Master Templates (templates created in Motion) do not display in Final Cut Pro 6. If you open a Master Template in Final Cut Pro, it may appear in the Viewer and the Canvas as blank or black on a computer with Leopard.”
Would you say that Apple should visit their developer site more often, or take their Mac user base seriously?
-
Tim Wilson
November 1, 2007 at 12:06 pm[Adolfo Rozenfeld] “Would you say that Apple should visit their developer site more often, or take their Mac user base seriously?”
Exactly.
Don’t forget that Adobe’s are the only true suites out there. (FCS is less of a suite, and has a leg up re: getting early builds.) So they have more plates spinning than anyone. They also know that people absolutely depend on their Adobe dynamic apps to be absolutely rock solid, all day every day.
Last winter/spring, they had the biggest software upgrade in the history of software underway. There was no way they could — or should — change the timetable of that process so close to the end.
Last but not least, *application* developers often wait until they have the shrinkwrapped version of the software before final testing.
Mine is only one perspective, but it came from a long time (way too long, actually) in the belly of the development beast. I wrote about it here.
It’s different for driver developers, who only tap a small part of the OS. They can have stuff whipped right out. It’s different for companies with only one product, who can focus all their efforts on it. Much, much different for bigger teams with multiple products.
That said, my guess is that Adobe got an early look at a version of Leopard they trusted, which is why they were able to say so quickly that so many of the suite applications have zero issues.
So here’s the fun part: toward the back of that PDF, here’s what they have to say about CS3 and Leopard:
Does Adobe recommend running Production Premium or Master Collection before its updates are available?
A. Yes, we are comfortable recommending this. Our testing revealed a few issues in specific workflows when running the video professional applications on Mac OS X Leopard. Many video professionals would not encounter these issues on a day-to-day basis.
They also post the link to the knowledge base so you can check the issues out yourself.
Look, they’re conservative about saying it’s ready. They SHOULD be conservative about it.
But if Adobe is “comfortable” recommending that you go for it before the updates have been fully tested with the released version of Leopard, I recommend that you take their recommendation.
PS. All of this is speaking in my role as a user, NOT in my role as a Cow fella.
Reply to this Discussion! Login or Sign Up