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 :)

FCP Log & Transfer disgards Red's metadata

Joined
Jun 11, 2009
Messages
1
Reaction score
0
Points
0
Hi all,

My first post so be kind ;-)

Have browsed the forum for a solution to my problem but no luck.

Here's my delemer:

When using FCP's log & transfer to transcode the R3D files to proresHQ for offline/online editing, I noticed the transcoded QTs were either looking extremely over or under exposed. After discussions with the DOP he advised that he had made a number of tweaks to the camera to achieve his desired look and that this info was then stored as metadata in the R3D files.

After opening one R3D file in Red Alert and selecting the 'metadata' tab, I could see the look he had shot. However this was not the look my proresHQ files were showing in FCP, even after following the below instructions:

According to Red FCS whitepages:

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.



So my question: has anyone else experienced this colour/gamma discrepancy between the transcoded files and the R3D files and if so whether you have found a workable solution to using log & transfer whilst maintaining the metadata?

BTW - I have installed all the latest plugins from red.com and am running FCP studio 2 v6.0.5

Many thanks for any assistance.

cheers

MM
 
So you're saying that you have selected "Native" in the FCP L&T Window when transcoding to ProRes and you're still not seeing the proper "look" of the baked clips?

As a test, try running your clips through RedRushes instead of L&T.
 
Michael, you can use the free ClipFinder to import your clips with the metadata intact:

http://www.daun.ch/software/

Grab the latest beta version and have a read of the instructions for more detail on how the process works, or jump into the ClipFinder thread here in the workflow forum.

HTH

Paul
 
Sounds like the dreaded playback/gammaspace bug (rec709/redspace). From the literature this has still not been addressed in build 20?

Check out this thread for the solution. (Mike Burton, that bottle of wine kicked ass!!!)

http://reduser.net/forum/showthread.php?t=28380
 
Back
Top