Final Cut Pro can manipulate 4k files!!!

[Anders Holck]

David.
How I understand it:

In the end the the Red camera will record in 4k and 2k Redcode RAW, 1080p and 720p Redcode RGB. Only in camera Redcode RAW will be enabled in the first cameras.

In the end Mac support will come in three steps:
1. Redcine
2. Normal Quicktime codec, for RAW and RGB support in all QT applications.
3. Enhanced FCP support.

Redcine and hopefully the normal quicktime codec will ship with the first cameras.

Later a FCP update will enable the enhanced support inside FCP.
You will get a P2 like import dialog with the ability to transcode into another codec and framesize.
You will also get RT extreme enabled Redcode.
Redcode RAW can be debayered on the fly. The Wavelets inside a wavelet codec allows it to skip layers to quickly get a half res or quater res image. Based on the performance of the processor and the destination sequence resolution, the codec can "gear down" the resolution on the fly, to keep the framerate. So while the sequence is plying you get a lower res but smooth framerate, and when you stop playback the codec switches to a high quality debayer. This is like the DV codec and DVCPRO codec currently functions inside FCP, it will gear down on the fly, with no user intervention.

If you choose to convert to another codec or framesize before editing, you can always recconect to the original RAW files and then do a consolodate in the mediamanager to get the final timeline in RAW, or you might have to export the timline as an XML and reconnect inside Redcine.

This is just one scenario.

There is really no info on what exactly is holding back in-camera Redcode RGB. Either the codec specs are done and they are waiting for the embedded version to get finalized, or the spec is not compleately finished and both the embedded version and the Quicktime codec are getting finalized.
Of course if it's the latter The quicktime codec will not be available until a later time, and youll have to use another codec, if you want to use an intermediate format.

 

[Nathan Troutman]

Based on the performance of the processor and the destination sequence resolution, the codec can "gear down" the resolution on the fly, to keep the framerate. So while the sequence is plying you get a lower res but smooth framerate, and when you stop playback the codec switches to a high quality debayer. This is like the DV codec and DVCPRO codec currently functions inside FCP, it will gear down on the fly, with no user intervention.

This is the way Final Cut worked even in its current incarnation. The program looks at what you got and makes it work the best it can. This is why I can edit HDV footage on a dual 1.8 G4 and my PC-friend has to conform his HDV footage to AspectHD to do any editing even though his machine is much more powerful. Final Cut lowers itself to the performance abilities of your machine (within reason.)

If you choose to convert to another codec or framesize before editing, you can always recconect to the original RAW files and then do a consolodate in the mediamanager to get the final timeline in RAW, or you might have to export the timline as an XML and reconnect inside Redcine.

Hopefully Media Manager glitches have been fixed with Final Cut Studio 2. I always seemed to have a problem getting media manager to get everything where it was supposed to be.

 

[Anders Holck]

Yes, it's the way it works if the codec is supported. You can edit in every codec that is installed in Quicktime, but only those that are blessed and have the right support hooks can do RT and the on the fly degradation.
Can't wait to get the Open Timeline of FCP 6 though. That will smoothen things up quite a bit.

Yes, the media manager has some problems in it's current incarnation. Usually doing a lot of variable speed is a guarantee for disaster.
I had to consolidate 11x25 min programs a few month's ago. I think it took around 2 days to get everything perfect.