Adobe CS5 Mercury Engine.

[John Jonathan]

http://blogs.adobe.com/genesisproject/2009/11/technology_sneek_peek_adobe_me.html

This is an off the shelf NVIDIA 4800 for MAC. Adobe and Autodesk are the first companies taking advantage of this card for MAC, Apple is busy making iPads and iPhones.

He imports RED 4k at about 10min into this video. 4k timeline and Keying in Realtime, in Native RED Format.

I don't understand my Apple is so mad at Adobe? Adobe is basically going to slaughter FCP with CS5.

 

[Uli Plank]

If they finally solve the TC issues with audio, maybe.

 

[Mel Matsuoka]

I don't understand my Apple is so m...thoughts-on-the-ipad/"][U]recently posted[/U] about the reasons for this continuing rivalry on his blog:

Another theme I’m seeing tonight is the lack of flash on the device. No surprise. If you really want to know why, think back a few years when Apple was trying to get back on its feet, and Adobe made a decision not to support its video products on the Mac, and instead tried to convince its mac customers to switch to PCs. Apple’s response then was ultimately to bring out its own video products — final cut — and ultimately ate the market out from Adobe. Later, when Apple was making the conversion to the intel platform, Adobe’s enthusiasm for bringing out Photoshop and its flagship products was most noticable — by how late they were and how uninterested Adobe seemed in actually trying to help Apple succeed. So now, when Apple has these really successful platforms and Adobes wants a piece of them, and yet Apple shows no real enthusiasm or hurry to cooperate? Well, folks, payback’s a bitch, and if you only see your partners for what they can do for you today, well, don’t whine when they choose to return the favor when the shoe is on the other foot. Burn your bridges with thought, folks, because you never know when you might want them back. And they’ll remember. Apple sure does. And wouldn’t it be great irony if Apple uses its platforms to turn Flash from a success to an also-ran by supporting HTML5 on platforms that are in enough demand that people who currently are building flash-based things end up recoding those things away from flash to support the platforms people are demanding? Just like — oh, say — Youtube just did? Hmm.

 

[Jim Hoffman]

Can't we all just get along...????...??? Ha.

That explains it in a nutshell.


This also looks very promising.

 

[Joe Carney]

I would be really impressed if they could do all this on a GT-285.

Whoops, saw the last part of the video, they do support the 285, just not as much layers.

 

[Tom Lowe]

When does CS5 hit the streets? Will it have Red support from day one?

 

[Michael Hastings]

You probably weren't around "back in the day", when Adobe was perceived by many in the Mac community to have abandoned Apple at a time when the Mac platform needed them the most.

Chuq Von Rospach, an Apple employee for 18 years, recently posted about the reasons for this continuing rivalry on his blog:

The rest of the article actually pretty much nails it in terms of explaining the ipad.

And for all those people that think Apple has been too busy on iPhones and iPads to get a new version of Final Cut out, I think you need to realize that Jobs, and Apple aren't stupid - they just aren't on the same timeline as a lot of us.

I actually think the success of iPhone, Ipod, and Apple bodes well for Final Cut in the long term. Apple has a ton of cash and a solid outlook which means they can invest heavily in Final Cut development. While some programmers may have been reoriented toward iPhone/iPad, I doubt if it is a large percentage of the Final Cut people and they can certainly afford to add software engineers even if it won't pay off for a while - something that wasn't necessarily true in the pre-iPOD days.

I also think Jobs realizes that even if Final Cut is no longer a large percentage of their revenue it is a 'sexy' product in terms of the attention the motion picture community gets. Having large amounts of cash means they don't need to rush out a new version just to get the upgrade revenue. Maybe they are taking their time to really get a new version right, kind of like RED with taking their time to get Epic right. (maybe this even means the complete rewrite that has been rumored, truly consolidating the different programs and converting to 64 bit.)

 

[ericyoung]

Well, you could argue that Apple were in the doldrums back then and weren't offering a compelling platform for Adobe to develop for. Apple stuck with PowerPC too long and strung it out with marketing hype. It's just POV whether you think Adobe were being deliberately anti-Apple, or simply acknowledging that PCs at the time had more horsepower for the buck and in absolute terms, and Apple typically playing it's cards close to it's chest gave no indication they were going to adopt Intel at all.

I know because I bet wrong with a overly expensive dual G4 which ended up being an even more expensive mistake very shortly afterwards. And I say that as a current fairly happy MacBook Pro user, but long time fairly happy PC user.

 

[Grant Goss]

I have the FX 4800 sitting here on my shelf, along with the REDrocket. Just in case. Bring on CS5....

 

[Chuck Z]

What does this mean for the RED Rocket card?

 

[David Rasberry]

Well, you could argue that Apple were in the doldrums back then and weren't offering a compelling platform for Adobe to develop for. Apple stuck with PowerPC too long and strung it out with marketing hype. It's just POV whether you think Adobe were being deliberately anti-Apple, or simply acknowledging that PCs at the time had more horsepower for the buck and in absolute terms, and Apple typically playing it's cards close to it's chest gave no indication they were going to adopt Intel at all.

I know because I bet wrong with a overly expensive dual G4 which ended up being an even more expensive mistake very shortly afterwards. And I say that as a current fairly happy MacBook Pro user, but long time fairly happy PC user.

I thought Adobe's decision to end PPC processor support was more of a practical economic one. Coding an app for two different processors with different instruction sets is much more expensive than translating between OS'es for the same instruction set.