REDrushes vs Log and Transfer

[Sam Roberts]

What are the differences, if any, between FCP Log and Transfer and Redrushes when it comes to picture quality (both set to ProRes 422 HQ) and speed of transcode?

[Kenn Michael]

FCP can't saturate all CPU cores like RedRushes can.... And the FCP transcode still has the gamma shift like the proxies. RedRushes gives more output options and the ability to burn timecode as well as set debayer quality.

I'd use RedRushes over FCP L&T all the time.

[Uli Plank]

Or have a look at Clipfinder…

[Kaku Ito]

Since ClipFinder can read edited XML from FCP to choose only the necessary R3D files AND by double clicking to open it with REDAlert! to do some one light color correction and save it as RSX that can be applied in ClipFinder's quick render future, I've been using ClipFinder more than REDrush nowadays. I'm not really a big fan of L&T.

[scottaettin]

According to the RED/FCP White paper that you get from RED when you download the L/T plugin, I thought that the original camera settings/look were preserved during import:

The Color, Color Temp, and View RED camera settings in use while shooting are stored as metadata within each recorded R3D file. When you transcode R3D media to ProRes 422, this metadata is used to preprocess the color and contrast of the transcoded media as long as the “RED FCP Log and Transfer plugin” submenu of the action menu is set to Native, which is the default setting. The result is that each transcoded clip visually matches the image that was monitored during the shoot. This preprocessing is “baked” into each ingested clip. If you want to later reapply a different type of image preprocessing to a clip, you need to reingest it.

Are you stating that luma & chroma are altered during the L/T process even when you choose NATIVE as the import method?

Thanks.

Scott