New Final Cut Pro Announcement at SuperMeet?

[yoclay]

But they said right at the beginning that they colorsync the footage on import, didn´t they.

Doesn't matter, it's when you go to output that the gamma shift often shows up. In my opinion the gamma shift is actually coming from Colorsync process itself! Also, how are they going to Colorsync between a YUV video monitor/final product and an RGB (computer) workflow..? All these people correcting in FCPX on their home computer like an iMac are not going to be anywhere near a video output. How will colorsync deal with that? People still don't get that using a Spyder for your computer monitor and Photoshop is not the same thing at all as video monitoring, especially if you want to be broadcast safe.

 

[DimitriL]

Yeah and it´s funny they basically copied a very old software on many features and even the colorscheme here: FAST/Pinnacle/AVID-Liquid Edition. It had the same grey,blue and in the same tone. It also had background rendering and quick-fades etc. It is funny that AVID had this software in its hands and now Apple runs with its ideas......

I don't know about the features, but I just looked at the colorscheme and...eh? It doesn't look a thing like FCPx's colorscheme (or for that matter, the current version of Adobe Premiere, which is what I thought FCP much more closely resembled). Every shot I found of the software you described looks exactly like...*current* FCP.

 

[DimitriL]

Doesn't matter, it's when you go to output that the gamma shift often shows up. In my opinion the gamma shift is actually coming from Colorsync process itself!

I thought it was well established that this was purely a QuickTime bug. There were a lot of reports of people being able to replicate the gamma shift problem in h.264 exports from Premiere as far back as CS3, at least that I can find. That would seem to eliminate ColorSync as the culprit and leave the entire QuickTime rendering engine as the problem.

I listened to a lot of high-level editorial discussions before the SuperMeet sneak, and the consensus was that the only way to do a lot of the stuff that was, in fact, unveiled would be to completely eliminate QuickTime as the rendering engine in FCP. The only way to do that would have been to rewrite FCP from scratch, which we now know they did. if Core Animation and Open CL is driving this, the gamma bug should be dead - unless, of course, they find a way to "update" that as well.

 

[cheezweezl]

Yes, but you definitely need to have decent hardware behind it, the tracking is great for the Resolve, but super intensive for instance. iMacs and Macbooks are not going to deal well with it. This means having the right video cards, serious cal-digit style backup array systems and probably a tower. For personal stuff many folks just don't have the resources to make that kind of addtional investment merely for their grading application.

true. as of now, there's no way to run it on an imac. and there's only one 17"mbp that will run it. it's really a mac pro (or hackintosh) thing. but once you're there, you can be fixed for hardware for as little as $550. GPU, and output card are all you need. big expensive raids, sans, and elaborate backup systems aren't any more necessary on davinci than any other system that needs speed and involves critical client data, including color. i have a raid but i can stream prores hq realtime from a single fw800 drive if necessary.