View Full Version : quicktimes from redcine X look washed out on ther own but look fine in FCP
Nate Clapp
04-04-2010, 06:23 PM
Hi. Camera guy not really a post guy, but thanks to RED i am going a little deeper down rabbit hole than I would normally.
Shot some tests in Build 30, used redcine build 183 to render out half res good quicktimes in redcolor. (no red rocket)
When I play the quicktimes on their own they look washed out- no real blacks. worse than the quicktime gamma shift problem (I think)
Funny thing is same clips brought into FCP 6 look great. and Tiffs saved from redcine 183 also look great.
I am not too worried as it looks good in FCP but what is going on?
Be gentle and speak slowly in post speak I am only really fluent in camera. Thanks.
-Nate
M Most
04-04-2010, 07:06 PM
Hi. Camera guy not really a post guy, but thanks to RED i am going a little deeper down rabbit hole than I would normally.
Shot some tests in Build 30, used redcine build 183 to render out half res good quicktimes in redcolor. (no RED Rocket™)
When I play the quicktimes on their own they look washed out- no real blacks. worse than the quicktime gamma shift problem (I think)
Funny thing is same clips brought into FCP 6 look great. and Tiffs saved from redcine 183 also look great.
I am not too worried as it looks good in FCP but what is going on?
If you're on Snow Leopard, and you're using the "default" Quicktime player (which would be Quicktime X, which plays movies in a window with no borders) that's the source of your problem. Try playing them in the Quicktime 7 player (available in /Applications/Utilities, provided it was installed, or via download) and that will likely display them "correctly."
Nate Clapp
04-04-2010, 07:25 PM
I'm not on snow leopard. (trying to stay compliant with p2 duel adapter) but that might still be a good tip. In any case it is probably my QuickTime player then?
JosephArthur
04-04-2010, 07:31 PM
I'm not on snow leopard. (trying to stay compliant with p2 duel adapter) but that might still be a good tip. In any case it is probably my QuickTime player then?
What is you were to chose just REDSPACE for your color. and look at your proxies from there. Film in Redspace and make sure color editing in Redspace. And conform from there. (preview first).
David Battistella
04-04-2010, 07:43 PM
Also,
While QT is quite flakey, you might get the best results with prores codecs.
If you use Prores 4444 make sure you turn off the option that sets the gamma space to automatic.
Uncompressed and DVCPRO HD will do the washed out thing.
This is what I have noticed in my testing.
David
Nate Clapp
04-05-2010, 10:29 AM
ok- as I suspected I am an idiot.
at some point I had unchecked "enable final cut studio compatibility" in QT preferences.
I also had my screen setup with 2.2 gamma.
checking that box made everything look a lot better.
But here's a question, checking that box makes stuff that should be displayed at 2.2 get properly displayed in 1.8. so does that mean i now should have my monitor (laptop screen) set back to 1.8 gamma? I ask because w out that check box checked it looked like i was getting "double" wrong gamma applied. I could even see two steps applied when i clicked back.
also FYI I was doing prores 422 SQ. Also rendering out to Red space seems to be wrong for build 30, among other things defeating WYSIWYG of stuff on set. Plus I never really liked redspace- too contrasty and "metallic rust" rust color to it.
Thanks for everyone's help.
Sidney L. Plaut
04-05-2010, 11:25 AM
I leave my gamma at 1.8. ran into alot of problems when I changed it to 2.2. like "double trouble."