Re: Weird Color Behavior?
Re: Weird Color Behavior?
- Subject: Re: Weird Color Behavior?
- From: Roger Breton <email@hidden>
- Date: Sat, 21 Feb 2004 22:05:40 -0500
>
Document white is always displayed as monitor white, and all other
>
colors are adapted to monitor white. This is as it should be.
Why make an exception for the document white? I, personally and a host of
other people I can think of, would not be offended by an sRGB document
appearing slightly bluish on a D50-calibrated monitor and a ProPhotoRGB
document appearing slightly yellowish on a D65-calibrated document. It isn't
like the infamous scum dot exception, you know.
First of all, the degree of resultant 'bluishness' or 'yellowishness'
appearance on screen would not be that terrible in absolute terms: as a
matter of fact, an image containing no white whathsoever would not be
displayed any differently, if I am not mistaking. Secondly, wouldn't we'd
readily adapt to it anyway?
>
An imaging system that displayed Colormatch as yellow and Adobe RGB
>
as blue simply wouldn't be useful for anything except showing you how
>
colorimeters and spectrophotometers would see the image.
Yellow and blue are strong words. We know it is not "yellow" as a lemon or
"blue" as the color of the sky. More like warm white and cool white. It is
not a secret, Bruce, that you and many other users spend all your time in
front of D65 'cool white' monitors while myself and many other users choose
to spend all of our time in front of D50 'warm white' monitors, and it seems
neither of us are complaining about the absolute warm and cool look of our
monitor white? We could argue the relative merits of each calibration. But
that's not the point. In my opinion, there isn't anything 'unatural' with a
system that warns the user, visually, when a white point mismatch occurs
between a document white and the monitor calibrated white setting. To me,
this would only serve to heighten user's awareness of the impact of monitor
calibration on color assessments. Further, I figure that if the ICC gave us
relative and absolute rendering intent, why limit its application to only
proofing? The same way as there are two camps when it comes to proofing,
those that swear by relColimetry and those that swear by absColorimetry, I
see a need for an alternative handling method of proofing to the screen. At
the very least, I'd like it to be an option in ProofSetup when proofing an
RGB document : we already have it for CMYK, what's so wrong about having it
for RGB too, I ask?
>
If your work
>
is destined for human eyeballs, you want Photoshop to take account of
>
human white point adaptation...
Of course, and I'd love to see Photoshop do it to perfection. I bet you if
you ask Thomas he'll tell you it's only two lines of code to change...
Roger Breton | Laval, Canada | email@hidden
http://pages.infinit.net/graxx
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.