C300: C log 2

Mestizo Devon

Well-known member
Is it possible for C log 2 to be added to the rest of the c line of cameras 100 300 500
Not that Canon would but is there a limitation
 
Not sure....but remember, the MK II has 2 "engines" (Digic 5s) where the original has one (Digic 3)....theC100 MK II has the Digic 4 so maybe it could do/handle more....

Jim Martin
EVSonline.com
 
Log 2 is designed to distribute 15 stops of dynamic range across a 10 Bit space.

Even if you could put Log 2 onto an original C300, you would loose detail that you simply could not retrieve, specifically in the shadows when you compare the curves.

We need to stay out of the mindset that Canon Log 2 is somehow better than Canon Log. It is simply better for the new high dynamic range sensor of the C300 Mark II.
 
You are corrrect...and that was explained in detail on Saturday at our seminar.....if I was just paying attention!

Jim Martin
EVSonline.com
 
The 500 has 10 and 12 bit

This is true, and I weighed touching on that in my initial response.

Maybe there could be something to gain by putting it in the 500, however, the 500 is still the same 12 stop sensor as the C300MKI/C100 and Canon does a pretty good job of milking their tech as much as possible, while still keeping that balance of reliability:innovation.

I've gotta believe that if there was more to offer in the C500's sensor, they would have done it when sales were dismal.

Jim-

Who was speaking at your event? Just curious, probably should have gone.
 
So, from that we shouldn't exptect to see it in anything without 15 stops...
Curious to see if Canon will support "older" cameras or just ommit functions/features because the put out new cams.

I will say RED is good about adding gammas/Log, color to past generation cams
 
C-Log 2 would seriously hurt the C100, C100II, C300, 1DC, XC10 images. C-Log is designed for you specific camera don't worry about it.
 
Now here is something that I've been trying to understand better.

With the new C-log2, we get the 15 stops of DR. And the way the wavewform reads it, it clips the highlights at 92 IRE. At first glance I get it, and the overall response that I've been hearing around is to continue lighting the same way, just treat 90 as the new 100. But if I think about it in detail I honestly don't fully understand it. What is it doing exactly?
- Is it bumping everything down on the waveform?
- Is it doing some sort of higher compression at the highlights?

For example, if I was shooting a scene with the c300mkI and wanted skin tones to land on 45 IRE and I want my highlights to end at 82 IRE, how would this translate to the mkII? And why?

Any of this making sense?
 
Back
Top