histogram not re-calculated for new o/p profile?

Comments

2 comments

  • dlashier
    > 2) Which profile _is_ C1LE using to construct the histogram?

    Unofficial answer - it's using its internal working space. Personally this is the way I prefer it although I wouldn't mind an option to display in output space I certainly wouldn't want this as the only choice. I understand your point re detecting clipping, but imo if you frequently find this to be a problem you should just switch to prophoto (or whatever) output as a policy rather than selecting only for 'problem' images. Are you certain that these colors aren't going to be clipped later anyway? My profile plots show that with my printer (2200) and papers Adobe RGB encompasses almost the entire capability of the printer anyway and for many output methods gamut is going to be even more restricted.

    - DL
    0
    Comment actions Permalink
  • alanrew
    [quote="dlashier" wrote:
    > 2) Which profile _is_ C1LE using to construct the histogram?

    Unofficial answer - it's using its internal working space...

    - DL


    Don,

    Thanks for the info. Great web site, BTW!

    I suppose the problem I have is understanding whether or not the data is really clipped.

    For example, let's suppose that the histogram on opening the RAW file displays warnings about the image being 'over exposed'. Usually, I can use the EC slider to move the histogram to the left, at which point the 'over exposed' warning disappears. This leads me to conclude that the original data wasn't really over-exposed; rather, the default conversion from the RAW data to the RGB output space, using the default value 'EC=0', was clipping.

    So, does the warning message tell me that the RAW data is clipped, or is it simply telling me that I'm not using the 'best' EC value?

    TIA

    Alan
    0
    Comment actions Permalink

Please sign in to leave a comment.