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

Gamma Handling in Color 1.5

Kaku Ito

Well-known member
Joined
Feb 20, 2008
Messages
2,803
Reaction score
3
Points
38
Age
65
Location
Chiyoda-ku, Tokyo
Website
www.dittok.info
As Nick mentioned in other thread that Apple had worked on the gamma handling in FCS3, I tested to find out it works opposite to what it was in FCS2.

Monitoring:
Now if you have native R3D on the Color 1.5 timeline, it's displaying the picture through Matrox MXO or Blackmagicdesign Multibridge Pro with 2.2 gamma.

Rendering:
When you render to Prores4444, it renders as you see it on the monitor. No gamma shift. This was so with Prores422 on previous version because Apple had specially made it that way.

When you render to Uncompressed 10-bit, it renders very close to the Prores4444 result. I recognize the gamma shift on the green channel a little.

When you render to DPX, it renders darker, so you would have to add something like 1.1875 (not 1.22222 like supposed to be) to the master gamma. It gets very close but unfortunately, it is not the same. Previously, Color didn't shift the gamma when R3D was rendered to DPX, but it was displaying at gamma 1.8, so you had to put it back to 2.2 by putting 0.818181 to the LUT (in case you have that like Multibridge Pro) or master gamma parameter while editing (then turning back when you render). The waveform monitor don't match comparing to the Prores444 or Uncompressed, because I see there is little bit of color shift on red and green in the lower middle range. Please also remind yourself that Color 1.5 displays R3D picture correct on the monitor. The master gamma manipulation has to be "on" ONLY when you render, not while you're grading.


So this is what I found so far.
 
Hey Kaku,

When finishing to 2k or 1080, do you have access to the full 4k resolution for resizing and cropping shots? Thanks.
 
Hello Jeremy,

I tried setting the project as 4k with 4k footage, then tried to render at full resolution but it doesn't render as people are mentioning in other thread. I can only render 2k or HD project as half resolution. Also, proxy and grading resolution seems have to stay at half resolution to be able to display picture.
 
By the way, the rendered Prores4444 result from Color 1.5 are very much identical to the proxy on FCP7.

Also found a bug that FCP7's vector scope is displaying strange with uncompressed 10-bit as sequencer's compressor choice.
 
Hi Kaku,

Have you tried bringing 3K off-speed shots in Color yet? I'm very interested to see whether or not this limitation has been removed in v1.5, as it is one of the biggest reasons for not finishing in Color at present, for me...

Cheers!
Dom.
 
I have 2k over crank clips that I can test. 3K, I have to look for it.
 
Hello Jeremy,

I tried setting the project as 4k with 4k footage, then tried to render at full resolution but it doesn't render as people are mentioning in other thread. I can only render 2k or HD project as half resolution. Also, proxy and grading resolution seems have to stay at half resolution to be able to display picture.

For whatever strange reason when I do set the render to half res I can output a full 4K 4096 x 2304 dpx or cin file. The appear to be full res. Can anyone else test this and confrim?
 
Hello Jeremy,

I tried setting the project as 4k with 4k footage, then tried to render at full resolution but it doesn't render as people are mentioning in other thread. I can only render 2k or HD project as half resolution. Also, proxy and grading resolution seems have to stay at half resolution to be able to display picture.

Thanks for the reply!
 
I'm curious about the 3K shots as well. I'd also like to know how well it round trips from FCP compared to now.

David
 
I placed a 3k clip then sent to Color 1.5, but it doesn't even playback the clip. I'll try with other clips.
 
The new FCS3 installer is released and the quality setting now seem to work as normal.
 
Also just to confirm, is the new FCP3 plug in accessing the build twenty color science? The release history does state "Supports RED ONE cameras up through Build 20."

Also, any other changes with the new v3.0 REDCODE plugin for Color? I've been hoping for more processing control, such as OLPF etc.

Any confirmed 4k renders out of color?
 
Actually, the plugin for Color indicated 2.9beta, not 3.0. And unfortunately, it does not offer OLPF.

And yes, it does render out 4k. As far as the debayering level, Kaya, I have to output with other app and compare the quality, but in the white paper says it does.
 
Hi Kaku,
Thanks for the quick response. I labeled the new Color plug in v3.0 because that's what I saw on the Red release history. Maybe there's some discrepancy between this and the labeling in Color.

So are we accessing the Build 20 color science with this?

I know Sean, I saw that, too. I guess they meant to update to 3.0 soon, that is what we can hope.

when RED says supports up to Build 20 then it must support new color science that is what I imagine.

I have a little fever at this moment and can't think well but how can we find out if Color 1.5 supports the new color science without having build 20 footage?
 
Back
Top