Hi Chris,
lists(a)colorremedies.com wrote Fri, 12 Dec 2003 15:37:42 -0700
[...]
If you're going to take a given set of RGB numbers
and merely assign
ECI-RGB, then convert to CMYK; go back to the same set of RGB number
and assign Adobe RGB and convert to CMYK, then sure the ECI-RGB will
invariably look better (in terms of saturation). But those colors that
exist in ECI-RGB but not in Adobe RGB but could be printed (especially
to a press) are not very common.
if I try to take your reasoning one step further, in lieu of better (and
readily available) gamut mapping paradigms, it may be useful to have
let's say a set of RGB editing color space/profiles, each of which is
targeted at a certain class of output devices, e.g. one for newsprint,
one for web offset, one for commercial printing and one for high quality/
large gamut ink jet devices (list definitely neither exhaustive nor
necessarily representative...).
If I knew I am only going to do newsprint and web offset for a given
image, I'd maybe use the web offset oriented flavor of that RGB editing
color space/ICC profile, and would increase the probability that what I
see on my screen (colors, detail, etc.) can be output at least more
predictably, than if I used an RGB editing color space/profile instead
that comprises all the colors for commercial offset printing on glossy paper.
A question that comes to my mind: let's assume I have a digital camera
shot covering quite some gamut, and I also have some way to get the image
data out of the camera without spoiling it by some early/inadequate
conversion into some questionable color space/ICC profile. If I convert
such data to a 'smaller gamut' RGB editing color space - how do I control
the gamut mapping strategy (only printer profiles really support
rendering intents)? If all goes bad, I have already "lost everything"
when I reach my process specific editing color space.
Olaf Druemmer