Scott Simmons has the scoop on rumors that FCP will soon offer native Red camera .r3d support. To date, editors have had to either edit with the QT proxies, or use RedCine / RedRushes to transcode to ProRes or another editing format. The former option is not recommended by most users, the latter can involve a very time-consuming transcoding process. So native support of R3D’s in FCP would be a big deal indeed, even if Adobe beat Apple to the punch. Firm details are sketchy right now, but Scott outlines the possibilities in his post. Check it out.


5 Responses to “Native Red R3D support Coming to FCP Real Soon Now”  

  1. 1 editblog

    I sure hope I’m reading those comments wrong or those commentators on Reduser just missed it as it really seems like Apple ain’t gettin’ it!

  2. 2 Matthew Jeppsen

    Yeah, it looks a bit dicey right now. ‘Course it’s all rumormill until it ships from Cupertino…

    -MJ

  3. 3 George Kroonder

    So… I guess it was my comment on PVC that started this bit.

    I must state that it was a short demo and I didn’t follow up on it (maybe I should have, eh).

    The way it was explained was that the raw red files (including 4K) would be re-wrapped (just a copy, so much faster than real-time, no transcode) in a Quicktime container. That makes sense to me; it makes no sense to use the _M files or to rewrap those.

    Apple also claimed that playback from the timeline would downres “on-the-fly”; to me this precludes the use of the RED proxies. In fact the proxies were not mentioned at all (also not as ‘required’).

    The hardcoded ~2K limit for FCP projects remains unchanged.

    To me this looks like the proper workflow for FCP. Just pour the R3D into the required QT container to work with them “directly”.

    Anyway, until Apple provides me with an advance copy of the new FCP and a Red camera to play with I’m all out of further info…

    George/

  4. 4 Kendal Miller

    George if thats all they do then this marketing hype and not much improved over their current workflow at all and definitely not “Native” support IMHO. Unfortunately I fear Red is becoming known for this type of marketing double-speak.

  5. 5 Ben Balser

    FCP is a QuickTime application, so it rewraps in a QT wrapper, so what? I’d rather have a stable, consistent system, than have to jump hoops for every codec on the market. Just like P2, I think the MXF file format is too trashy, thank goodness for the FCP QT rewrap! Makes things much easier to work with. And with FCSvr’s metadata tools, I’ve got no problems with any sort of deal working with files inside QT wrapers.

Rodney's Adsense-Deluxe Add ons plugged in.