KirkS518 wrote in post #16286769
My questions are -
1. What are the grey pixels representing along the bottom of the Colors Histogram?
In the "Colors" histogram display, when the R, G and B histograms overlap, they produce the resulting "mix" of the overlapping colors - so, for example, if G and B curves overlap, they produce C (cyan) - if the R and G curves overlap, yellow and if R and B overlap, magenta. If all three (R, G and B) overlap they produce gray - i.e., equal parts R, G and B. This does not mean that there is any of the mixed colors present in your image, per se.
2. What does it mean (in any of these histograms) when a color (or even a luminosity) goes above the visible chart?
The Y axis is pixel count - there is no explicit upper bound, but when the particular histogram bin hits the top of the plot, it means "a lot of that pixel" it's not a bad thing. Imagine, however, if you had a lot of one particular value but wanted to see details about the other values across the histogram. If the Y axis scaled to the value of the greatest bin, then you would not be able to see any of the other bins' details. It would be like plotting a bar graph of 10 people and their age - if one person was 102 years old and the rest were infants of various ages between birth and 1 year of age, you would not be able to tell the difference among all the infants if the Y axis (age) was scaled to 105 years of age (max axis value) to depict the 102-year-old person's age.
3. Using this example, I interpret it as the red channel is blown, because the pixel representation is climbing the right side, although the image itself isn't appears to be exposed correctly (according to the luminosity histogram). How do you correct for this without changing the image's coloring, or do you leave it alone?
The red channel is likely fully saturated and clipped due to the content of the image. Your camera's meter "sees" the reflected light from the scene a lot like the Luminosity histogram shows you, so the exposure was "correct" for the average gray value of the scene (or spot, or however you metered). But, in this case, there are strong bright reds and magentas in the scene and, if you want to capture them accurately, you have to consider these scene-specific elements in your exposure determination. To see if your camera actually captured the red channel fully, and if you shot raw, you can use a raw analysis tool like Raw Digger. In such an application, you will able to see if the R channel of the sensor reached saturation (actual raw data clipping) - If it did not, then the clipping in the RGB image is due to the conversion of the raw file or the use of an RGB color space that could not contain the R data fully.
Some applications can reconstruct these highlight values if the other two channels are intact, but color reproduction usually suffers because the recovery is for luminosity reconstruction. These algorithms do not, of course, know what the clipped values actually were, but they can often reconstruct the luminosity and then propagate a guesstimate of the color that those pixels were into the reconstructed pixels.
The histogram is an extremely useful tool if you are interested in image processing and automation. Sure, we can all edit "by eye" and achieve something we like. But, if there are aspects to image editing that can benefit from analyzing the image content, then the histogram is a nice way of visualizing and implementing these techniques. For example, as of PSCS6, if you use Auto in "Enhance Brightness and Contrast" mode (auto levels, auto curves, auto brightness-contrast) the auto algorithm does not simply bring in the black and white points to the edge of the histogram, within the tolerance you specify - it compares the histogram of YOUR image to a database of image histograms and applies an automatic correction to YOUR image that was deemed optimal for the database image. For auto curves, it will apply a multi-point curve, not simply a straight-line black-white point adjustment. That is pretty slick and may provide a starting point that would have taken minutes of "by eye" correction to achieve.
kirk