Use a CCSS file created with that spectrophotometer for your two colorimeters. IMHO, I would not trust that CCMX if it was created with a 10nm graphic arts spectrophotometer. You are using different colorimeter corrections for different devices and different profiles. If you don’t care about those artifacts you can forget this paragraph. Some image editors perform better than others because they cause less rounding errors, or use high bitdepth output paths or because that app does “in app” dithering. It is very useful that after a calibration and a measurement report like yours, draw a grey gradient in your prefered image editor and look for that issues. In that situations and in order to avoid color cast in gradients you may want to use “single curve” matrix profile because those profiles store TRC that are neutral (actual L* measured data but a*b* forced to be 0). If you check “Evaluate gray balance through calibration only” you will be able to see that in report.Īnother example: if you had a visually good and neutral grey gradient in non color managed enviroments, without banding or other calibration artifacts, but you experience green/magenta cast in grey gradienta when in color managed apps, then “Evaluate gray balance through calibration only”=checked may report good results but the unchecked report may be not so good (there are situations where checked and unchecked are good and you see bands or color cast in gradients in color managed apps). Your are not evaluating if calibration is good.īut such accurate profile may store a bad calibration with color tints in grey and huge shifts in green-magenta across a grey scale. That is because you are evaluating if profile matchs monitor’s calibrated behaviour. Measurement report will plot very low dE, dC and such (an exception is “assumed whietpoint”). This means evaluate if color of grey is neutral to its white.įor example you could have an extremely accurate XYZLUT+matrix profile that stores monitor behavior in high detail. With this option checked “grey range” will report actual color shifts in grey from against the color of white 255. This is a way to check calibration “color tints” (usually magenta and greencolor cast but also blue) in grey ramp (but usually there are too few measurements to find “calibration induced banding” because of low bitdepth LUTs or lack of dithering, better use visual inspection for this task). If you check “Evaluate gray balance through calibration only:” then evaluation runs against a “perfect” neutral grey (a*=b*=0) but measured brightness (dL*=0). It takes maximum shift in da* and db* as a measure of total/worst color shift in grey, hence the name “range”. “RGB gray balance (>= 1% luminance) combined Δa*00 and Δb*00 range” (also called “a*b* range” or just “range”/”grey range” in other software or reviews) tells you if there are big shifts between measured data and TRC data. “RGB gray balance” answer the question “Does measurements in gray scale track what is recorded in profile’s TRCs?”
0 Comments
Leave a Reply. |