Re: Eye-One Pro and Profilemaker 4 Emissive Meaurement Errors
Re: Eye-One Pro and Profilemaker 4 Emissive Meaurement Errors
- Subject: Re: Eye-One Pro and Profilemaker 4 Emissive Meaurement Errors
- From: Chris Murphy <email@hidden>
- Date: Sun, 24 Nov 2002 23:42:35 -0700
On Sunday, November 24, 2002, at 11:02 PM, "John Hollenberg"
<email@hidden> writes:
Fascinating, but not sure it applies to my example. I created the color
patches in photoshop in L*a*b* mode, rather than creating in RGB mode
and reading the L*a*b* values with the eyedropper.
Nope, then it doesn't apply. The eye dropper tool always shows actual
values in a file the same regardless of rendering intent setting. The
rendering intent setting only affects the numeric values in the info
palette for a mode that is not the same as the mode of the document
being sampled.
Also, while your example does work with Adobe RGB, if I choose
Ektaspace
as my RGB space it doesn't matter whether I use Perceptual or Absolute
Rendering in the Color Settings.
It's a D50 based space, so this is normal.
Still, it strikes me as very strange that two different explanations
(D65 vs D50,
perceptual vs absolute) would match the numbers I have!
The two explanations are are related. D65 vs. D50 is the real issue,
but in the case of perceptual, relcol or saturation intents that issue
is totally ignored so you get a discrepancy between info palette
numbers and measurements. When the whitepoint issue is taken into
account using abscol rendering, then there is no discrepancy.
Chris Murphy
Color Remedies (tm)
Boulder, CO
www.colorremedies.com
_______________________________________________
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.