gh4_storyteller
Active member
Heyo! This is my first post in the Canon Cinema EOS corner of DVXUser. I just recently switched from the Panasonic GH4 to the C100 since my projects increased in volume; and I needed a workhorse over 4K.
I've been super excited about using C-Log on the C100, and yesterday I went out to get some test shots. From what I understand, C-Log intentionally under-exposes the image in an attempt to squeeze as much out of the highlight's as possible. Which in theory, is fine. The camera shoots middle grey at 32 IRE, so midtones simply need to be brought back up to 50 to put the image back at normal exposure. Then the whites or the over-exposed part of the image is brought up or down to sit right at 100 IRE. Last blacks are brought down to 0 IRE and now you have a proper exposure-corrected image. However, on the internal codec, that amount of post work is pushing the codec beyond what it can handle. I think that C-Log is maybe attempting to retain too much information for it's own good.
I'm assuming the only real way to fix this is to expose the image a little brighter than what Canon suggests, but I hate that I'm waisting a few stops of light to simply go around what the C-Log is doing.
I'm not trying to find a definitive answer on how I should expose; I just really want to know what you guys are doing and how you're exposing when shooting C-Log on the internal codec.
I've been super excited about using C-Log on the C100, and yesterday I went out to get some test shots. From what I understand, C-Log intentionally under-exposes the image in an attempt to squeeze as much out of the highlight's as possible. Which in theory, is fine. The camera shoots middle grey at 32 IRE, so midtones simply need to be brought back up to 50 to put the image back at normal exposure. Then the whites or the over-exposed part of the image is brought up or down to sit right at 100 IRE. Last blacks are brought down to 0 IRE and now you have a proper exposure-corrected image. However, on the internal codec, that amount of post work is pushing the codec beyond what it can handle. I think that C-Log is maybe attempting to retain too much information for it's own good.
I'm assuming the only real way to fix this is to expose the image a little brighter than what Canon suggests, but I hate that I'm waisting a few stops of light to simply go around what the C-Log is doing.
I'm not trying to find a definitive answer on how I should expose; I just really want to know what you guys are doing and how you're exposing when shooting C-Log on the internal codec.