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

Simple RED proxies FCP > Color problem

D'Arcy Foley-Dawson

Well-known member
Joined
May 14, 2008
Messages
119
Reaction score
0
Points
0
Location
Melbourne, Australia
Website
www.charliepigdog.com
this is a very simple and straightforward issue and i'm sure it's been dealt with here before, and i did do a search but as i'm sure you can appreciate it can be hard to find exactly what you're looking for in a popular sub-forum such as this one. so please forgive me if there is already a well-known solution for this problem and point me in the right direction!

OK, so here's the deal:

4K 4096x2304 16:9 RED clips, i am fairly sure they are REDcode-28 as opposed to 36; as for the build i don't know but they were shot on the 6th june this year. most of them were shot at 36fps, a handful at 50 and 25. being in PAL land they will be finished at 25.00fps.

whenever i try to SEND TO Color a sequence of H quality proxies, Color won't reproduce the sequence properly. the problems are:

1) all the clips in the Color sequence start at their very first frame, ie. the very first frame of the actual R3D file, and continue for the duration of the clip as it was edited in FCP (then the next clip starts at it's first frame, then the next, etc.) in other words, most of the clips in the Color sequence are just shots of the slate!!

2) despite any changes i make to the rsx file with red alert! Color will not recognise these changes. we shot to deliver the finished video in black and white, so the metadata on set was recorded with a saturation of 0.00, but i want to have a play around with the colour values as recorded on the day BEFORE desaturating them, ie. adjust colour values in the Primary In tab and then desaturate everything in the Primary Out tab.

FCP will display the correct metadata based on any changes i make in red alert!, ie. the clips will show up in full colour in FCP. but when i send the very same clips to Color, they appear desaturated again, ie. reverting back to the original recorded metadata.

can anyone please shed some light on this? i'm running FCP 7.0.1 and Color 1.5.1, on an iMac with 3.06 dual core, 4gb ram, nvidia geforce 8800 gs.



i should also point out that this is not an urgent problem because this project (music video) was finished and delivered months ago, i have my own workflow of rendering out extremely high bitrate clips from RED via redcine and then grading them in photoshop; but i've been playing around with Color recently and wanted to have a go at grading RED with it now that it can access the R3D data.

i know most people find it very easy sending proxies from fcp to color so i guess these problems i've having are the exception to the rule....?
 
1. Did you work with proxies in FCP? In that case use Colorfixer (or the same function in Clipfinder) by H. G. Daun (free).

2. Color doesn't recognize RSX files, you'll need to use the RED room.
 
Thanks Uli.

Yes I edited proxies in FCP.

So I downloaded Colorfixer and followed the instructions - saved the Color project, opened that up in Colorfixer, ran the program, closed, opened the project up again in Color - but no luck!! Still the same.

What am I doing wrong?

EDIT: Updated to Clipfinder 2.2 but can't even find the fix looping bug function in that program! Googled for instructions that say it's in the Tools menu, but mine doesn't have a tools menu!

Sorry for the annoying dumb questions, I appreciate the help....
 
Sorry, but in my Clipfinder 2.2 "fix looping bug" is the last entry under "Tools".

Could it be that your system is screwed up somehow?

BTW, it's not such a good idea to edit with proxies. Apple is discouraging it in the whitepaper (as is Noah Kadner in his book), and we observed other problems than the bug you described in Color even after running Colorfixer.
 
Dammit!! i guess it's possible.... but how? why? seems really weird.

i don't think i would edit with proxies again, i see now that transcoding to prores saves more time in the long run.

i just wanted to test the fcp > color workflow to see how it compares to what i've done in the past. i'm glad i'm finding this out now, and not when i actually have to deliver something to a client.
 
Back
Top