Quicktime Proxies vs. REDCINE-X

[Jeremy Morrison]

There seem to be a lot of posts scattered around about this so my apologies if this has been addressed before, but I was unable to track down a final solution.

In the past I've used footage shot on the RED, cut in FC using proxies, sent to color, rendered ProRes files and back to FC to output without any problems. I'd like to be able to use this same workflow but...

The quicktime proxies are noticeably different when opening in Quicktime or FC than when I open the clip into REDCINE-X. I believe this is a quicktime gamma issue which has been mentioned a bunch of times from the thread searching I have done, but is there a solution?

My footage has been shot with the MX chip, REDCODE 28, and should have a REDcolor color space and REDgamma gamma space. I'm using FCS 3, RED QuickTime codec v4.2.0, Log and Transfer plug-in for FCP v30.0.0, REDCODE plug-in for Color v4.2, Quicktime X on an Intel macpro – all the latest and greatest as far as I know.

Here is a side-by-side comparison of what I see on my end:

Any thoughts on what I'm doing wrong or if this can even be corrected? Thanks so much.

 

[Deanan]

Make sure you have the latest quicktime component.

 

[Jeremy Morrison]

Is that included with one of the installers from the support page or something I download separately elsewhere?

Right now my REDCODE.QT.component is v4.0. It lives inside my library/quicktime/ folder. Root, not user. Is that correct?

 

[Mark Phelan]

Why did you shoot using the MX sensor with Redcode 28?

 

[Jeremy Morrison]

@Deanan: putting the component into my user/library/quicktime fixed the problem. Thank you, sir.

@Mark Phelan: you'd have to ask my DP.

 

[Nick Gardner]

As the DP, I shot Redcode 28 because I didn't feel the masturbatory need to have more "Ks" and "24ps" when shooting a TV show ;-)

 

[Mark Phelan]

Well there you go. Always an answer for every question.