Jobs Reportedly Says Final Cut Update 'Coming Early Next Year'

[Cüneyt Kaya]

The discussion is about FCP not about the mac.

no, it was you regretting buying a mac.
you switched from fcp to talking about regretting to have bought apple hardware.

 

[Hrvoje Simic]

no, it was you regretting buying a mac.
you switched from fcp to talking about regretting to have bought apple hardware.

He could have fooled me...

I have almost regretted investing in an apple computer 2 years ago under the impression that FCP would lead the way.

 

[Michael Hastings]

I have almost regretted investing in an apple computer 2 years ago under the impression that FCP would lead the way. It turned out the opposite has happened. :-(

I can understand this part a little bit, especially if you weren't a Mac person to begin with, because I had the same impression. But I'm not sure if it was Apple or RED that gave me that impression, and I don't have any idea how those internal relationships work, so can't really "blame" anyone.

For me it just means I upgraded to a Macpro earlier than I would have otherwise so was a generation early and now a generation behind since I would have normally waited to buy this years version, so will probably wait until next year to buy new. Basically about a $1000 waste spread out over a year or so - not the end of the world.

 

[Sanjin Jukic]

What would a 2011 Final Cut Studio look like?

What would a 2011 Final Cut Studio look like?

What would a 2011 Final Cut Studio look like?

"One thing for certain would be more rewritten code in Final Cut Pro. In Final Cut Pro 7
we got a completely rewritten Speed Control: evidence is the different look and feel,
additional features and that if you feed it XML you get a slightly different result in
Final Cut Pro 6 than in 7. Similarly my programming partner tells me that the XML writer/parser was very,
very likely rewritten for Final Cut Pro 7. While the rewritten Final Cut Pro 7 XML import/export
(and the features in that version) are great for developers like ourselves,
they don’t generate a whole lot of customer excitement.

So, rewriting to Cocoa from Carbon has probably been progressing between releases.
There’s nothing to prevent rewriting the Transition Editor or dozens of other parts of
the application that aren’t media or media metadata related. I was thinking that the
rudimentary image recognition features of iMovie ‘11 – how many people are in a shot,
is it W, M or CU? – would be a great addition to Final Cut Pro 7, but that could require work
on the Bin/Browser interface, and I think Bin/Browser will require some tools for reading
QuickTime Metadata that are Cocoa based rather than old Carbon code, but perhaps not.

Editing features, or perhaps even templates, could come over from iMovie ‘11 without taking
out any professional level features. This would be much like Aperture 3, which included iPhoto
features without losing or dropping “professional features”."

What would a 2011 Final Cut Studio look like? >>>Read more>>>