Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Native R3D support in FCP coming soon:

Jason Badham

Well-known member
Joined
May 17, 2008
Messages
58
Reaction score
0
Points
0
I read this over at PVC (http://provideocoalition.com/index.php/aadams/story/red_workflow_redux/), and a commenter had this to say:

"At the LAFCPUG Supermeet at IBC yesterday, Apple demo-ed RED support in FCP for the upcoming update.

FCP will be able to work with the RED files directly. It will allow you to create 2K projects using 4K RED footage.

Log and Transfer will rewrap the 4K R3D in a QT (no transcode) and preserve all metadata (as well as what you add). On the (2K) timeline FCP will do on-the-fly downrez.

When you send a timeline into Color all RAW parameters are available in the Primary Room in a “Red” tab. There you can edit the RAW parameter like WB, exposure, etc.

Should be something to look forward to…"

Can anyone else confirm this? I already posted this in the Scarlet 3k forum, but this sounds really exciting.
 
Well, they did not demo it, they announced it. First time I saw a software guy that had tatoos, and arms that could have a chance at wrestling with Jarred ;)

In the update, FCP will be able to import R3D files natively, via the Log and Transfer function. A bit slower than realtime to get it wrapped into a QT wrapper.

It will work only in 2k, no support in 4k as of yet.

When going via Color, then everything will be transcoded into ProRes.

No announcement as to when this will become available.

Meta data from the Red One will be preserved.

(Everything served from memory, I might have misunderstood something...)
 
Can't confirm, but that sounds like a pretty good solution to the FCP only working with QT thing. It almost sounds like what RED did with QT proxies, only if Apple were to do it inside of Log and Transfer.
 
In the update, FCP will be able to import R3D files natively, via the Log and Transfer function. A bit slower than realtime to get it wrapped into a QT wrapper.

I don't have an HVX myself, but is this similar to how FCP currently handles P2 footage? If so, it doesn't sound too bad...
 
Better than things are now, certainly, although I'm a bit disappointed (if this stays true) that Color won't have full R3D support, I was really hoping to have full access to the RAW inside Color. But, nice to know more is coming, now if only someone at Apple would be kind enough to actually engage the community here and be a source for this type of info like Adobe, Avid and Assimilate.
 
maybe that meant it would be trancoded to ProRes on the way OUT of Color, not IN. Otherwise you wouldn't need the RED tab.
 
maybe that meant it would be trancoded to ProRes on the way OUT of Color, not IN. Otherwise you wouldn't need the RED tab.

I'm wondering about that as well. Other people who saw the actual demo at IBC said that Color handled the RAW files. I hope that that is the case. Also, the first post mentions that Color has access to all of the metadata in the Primary room. Is that only the Primary room and not the Secondaries? That seems odd.
 
I don't think it sounds that odd, they probably need to dispense with the raw processing as soon as possible and just start working with a standard image.

Also, once you have your color temperature and exposure right in primary, why do you need access is secondaries? Couldn't you just use the normal controls to push and pull it where you want?
 
A special Red room wouldn't make much sense if they converted to ProRes on ingest.
 
Sounds good to me! I just hope we don't have to shell out another $499 'cause they tag it FCStudio 3 :angry01:
 
I'm wondering about that as well. Other people who saw the actual demo at IBC said that Color handled the RAW files. I hope that that is the case. Also, the first post mentions that Color has access to all of the metadata in the Primary room. Is that only the Primary room and not the Secondaries? That seems odd.

Why would you need to know the color temp. decision made on-set in the secondary room?
 
Sounds good to me! I just hope we don't have to shell out another $499 'cause they tag it FCStudio 3 :angry01:

I don't think they'll charge us another $499 for that functionality. But they will charge us $499 for Phenomenon. Maybe they'll do an update for FCS 2. Didn't they do that when they added P2 support (made it as an upgrade to FCS1 as well as incorporating it into FCS2)?
 
Sounds good to me! I just hope we don't have to shell out another $499 'cause they tag it FCStudio 3 :angry01:

I'm sure they will and the truth is, if it does what they say they probably deserve it! :wink:

I don't think they'll charge us another $499 for that functionality. But they will charge us $499 for Phenomenon. Maybe they'll do an update for FCS 2. Didn't they do that when they added P2 support (made it as an upgrade to FCS1 as well as incorporating it into FCS2)?

Now that would be cool...
 
Rewrapping the R3Ds in a QT wrapper is great, and makes sense, but I'm gonna just assume that in terms of editing performance, there won't be much improvement, if any, over editing with proxies in FCP.

As a colorist, I'm super-excited about the prospect of being able to simply send the offline sequence straight into Color, without having to wrangle it through Crimson & RC. But the issue of poor offline editing performance (without transcoding to ProRes) still needs to be addressed. My guess is that this doesn't address it. :(
 
I saw the demo yesterday and this is how it works: You use the Log and Transfertool as today except that FCP won´t transcode the files into ProRes but just copy the files to your scratchdisc and importing the _M.mov referencefile. Then you edit using the referencefiles like you do today. When sending your edit to color it will relinc the files to the r3d files wich you have full access to in color. You can change almost the same things as in RedAlert. Color will have a "RED" tab in the primary section where you can set all the file parameters. The you render it out to .dpx seguence or QuickTime-files for going back to FinalCutPro. Nice in my opinion... Cutting using the refrencefiles are still heavy and have some issues.
 
I saw the demo yesterday and this is how it works: You use the Log and Transfertool as today except that FCP won´t transcode the files into ProRes but just copy the files to your scratchdisc and importing the _M.mov referencefile. Then you edit using the referencefiles like you do today. When sending your edit to color it will relinc the files to the r3d files wich you have full access to in color. You can change almost the same things as in RedAlert. Color will have a "RED" tab in the primary section where you can set all the file parameters. The you render it out to .dpx seguence or QuickTime-files for going back to FinalCutPro. Nice in my opinion... Cutting using the refrencefiles are still heavy and have some issues.

Thanks for confirming that Christian... that sounds pretty cool...
 
Thanks Christian, that sounds exactly what I want for Color, so super happy now. We've been using the proxies, _M, and even if it's just a tad better than it is now, well worth it for that Color support.
 
This is cool and all but why would they make you go through the L&T utility to essentially make proxies similar to what the camera already creates for you which allows you to instantly begin editing without conversion of anykind and still have to deal with the computer processing overhead? Many will want to continue to work with ProRes files, which it sounds like will not work in the conversion back to the RAW files in Color (someone correct me if I'm wrong).
Also, will you be able to assign an RSX file in the L&T for a one light to edit with, another feature that many will want to harness from REDALERT / REDRushes?
I'm not knocking this solution what so ever just curious how and for what type of jobs this workflow will best suite. Regardless, it's good to see apple making progress in one way or another!
 
Thanks for the update and details. I'm really happy about their continued development of Color. I knew Apple had to have something in the works. Their secrecy is frustrating, but understandable I suppose.
 
Back
Top