Thanks a ton in advance!
Thanks a ton in advance!
The histogram as it stands shows you what the color science is actually doing to the data.
I filed a support ticket not long after I received my Epic X for just this problem. After several weeks of back and forth they concluded nothing was wrong. Then I contacted my Bomb Rep. and explained the problem and sent in it. They sent it back saying nothing was wrong. Finally I spoke to an individual who admitted it was a bug they thought they had squashed. This was two firmware releases ago.
My question Matt. Is the camera recording the full range capable and displaying it truncated? The highlight data in RAW or at 320iso never go beyond around 85-90%. Or is it recording a limited range of data and then the color science is stretching it back out to 100%? Thanks.
So now there's a new page about exposure tools in the "Learn" section of RED.com: http://www.red.com/learn/red-101/red...exposure-tools
After reading it I'm more confused than ever about how to use the histogram. The text makes no mention of how the histogram behaves when monitoring in RAW mode (i.e. "OFF" is highlighted on the OSD). In fact, the text kind of implies the histogram is always affected by current ISO and look settings, as if there's no RAW mode at all. The last paragraph reads, "Furthermore, ETTR can be misleading since the live histogram doesn’t represent raw image data."
And yet I can see the histogram changes visibly when switching to RAW/OFF monitoring.
Also, the page does not clarify the strange behaviour reported by some users in this thread. Like how the histogram shows no gap on the right for a while, and then suddenly the gap appears again.
Someone educate me, please.
Just updated to the last release firmware and it appeared on my Scarlet.
In my case the left side is ok, but on the right there is a gap.
It wasn't there before on older firmwares.
EDIT: No gap on higher ISOs
I'm not sure I totally understand WHY the histogram NOW has gaps before the clip points. I understand that it is reflecting the metadata and that the different gamma selections roll off the highlights in a different way so I think that's why there is a gap. RG3 never lets values get to 100. (nor does RG2). When I load a clip into RCX with severe overexposure the whites never get beyond 97 or 98 on the waveform. My question is:
WHY NOW? It did not used to be like this just a few months ago. So why the change? I find it extremely frustrating that a change like this is made, which to the end user represents a significant change in the way we use and understand the histogram tool. Yet it gets a half sentence line in a release note. This is yet another reason this camera is viewed as unreliable or confusing to many. I'm all for improvement but it's impossible to test every feature of every new build every time the camera is updated.
Furthermore, the zebra function doesn't work. Shooting a clearly OVERexposed scene with zebras set to 98 to 108. Look at the following images. Redgamma 2 is selected. At ISO 500, zebras are present and Exposure check shows red overexposed areas. At ISO 400 zebras disappear but exposure check still shows red overexposure. Is this a known issue?
http://en.wikipedia.org/wiki/IRE_(unit)); This is operating on the cooked data (meta data is applied).
The exposure check mode shows where the raw data is being clipped (or in danger of being clipped).
It is expected that they would behave differently based on your meta data settings.
Also, can you please tell me why the change was made on the histogram? It used to go from goalpost to goalpost in a full exposure in rg2. I shot hundreds of days that way. Now, when the histogram approaches highlights there is a gap between the brightest it can represent and the goalpost in rg2. Why the change?
Thanks for your replies.
It's only counterintuitive if you think about the Scarlet as if it's a video camera...it's not. What you say makes perfect sense for something like an EX1 or F35, which don't record raw sensor data and have no concept of metadata.
It seems as if you're thinking that the IRE values are somehow a subset of the wider sensor values on the same scale and that's not the case. One can inform us about the other but they don't drive one another, at least not in the way that you seem to think. They measure different things at different stages.
After you set your frame rate and shutter angle/speed, the ONLY other on-camera control that has an effect on how the sensor gathers light is the aperture control. If you set up a scene where you're shooting an evenly lit, pure white background but you're not clipping the sensor because you've adequately stopped down to just below the clipping level, you can crank the ISO all the way to 12,500 and make the zebras scream but it will not overload the sensor because you're merely changing the metadata. The only ways to clip are to open the aperture or add more light to the scene.
Well, the converse is also true, which is your situation. You're blowing out portions of the sensor but you can get the zebra to go away if you lower the ISO. The zebra is based on IRE values which ARE driven by ISO (they have to be), but the ISO value and the REDgamma settings are metadata. The metadata has no effect on the raw sensor data.
It may help to think of it like this: raw sensor data --> metadata --> video data. The IRE and zebra values are downstream of the metadata and therefore the metadata is cooked (as Trent put it) into those readings, but they're only really relevant at the video outs. That explains why you can lower the ISO and eliminate the zebra but still have a clipped sensor. IRE just cares if you're going over 100 at its stage, not about what happened upstream.
"What happens upstream is none of my business." - IRE
Again, RED's cameras understand video but they're not video cameras.
Zebra and IRE are relevant to any VIDEO signal present at the Scarlet's VIDEO outputs, namely the SDI, HDMI and lcd/evf ports. At that point, signals must conform to video standards and it's where it makes sense for the metadata to have its impact because that's where those settings "stick", whether they're going out to an external monitor or recording device. It's a different space than the raw data.
IRE (video space) doesn't care if you have headroom in the highlights or not - go above 100 and you're clipping. If you're not clipping the sensor but you are above 100 IRE you can bring the levels down and reclaim the highlights in post.
Exceed 100 IRE but clip the sensor and bringing the levels down will do you no good in terms of reclaiming the highlights because they're simply not there.
Do what you have to do to to get your video feed looking right for monitoring or external recording but, by all means, protect your "negative" and don't clip the sensor unless you can live with the outcome.
|« Previous Thread | Next Thread »|