Thinking...thinking...oh yea, I'm not sure this is exactly right.
Please correct me if I'm wrong, but I assumed it was L*a*b* numbers
that were sent through the monitor profile, converted to RGB, sent to
the display and then measured with the colorimeter/spectro with the
resulting L*a*b* values compared back to the original L*a*b*.
I'm pretty sure this is the case with Monaco PROFILER's and OPTIX
monitor+profile evaluation routine because I'm looking at the
reference file they use for monitor evaluation (Macbeth ColorChecker)
and it's a list of L*a*b* values.
Of course, I assume other monitor verification tools could do just the
opposite.
Regards,
Terry Wyse
On Dec 2, 2007, at 4:05 AM, Marco Ugolini wrote:
he verification procedure starts with a list of RGB numbers that are
being
sent to the display: at their origin, these RGB numbers are simply
numbers,
and have no *inherent* colorimetric appearance. It's only by virtue
of the
active monitor profile that they assume a definite colorimetric
appearance.
Next, the verification procedure takes measurements with the
colorimeter;
after that, it normalizes and adapts the measurements chromatically
to the
monitor profile's white point.
Finally, it produces two lists:
(1) A list of the L*a*b* numbers that are derived from the initial RGB
numbers when the active monitor profile is assigned to them (reference
values);
(2) The colorimetric values *actually* measured off the display
(normalized
and chromatically adapted).
The resulting DeltaE numbers are calculated from the comparison of
these two
lists of colorimetric values.
