Re: ScannerRGB to WorkingSpaceRGB (rendering intents)
Re: ScannerRGB to WorkingSpaceRGB (rendering intents)
- Subject: Re: ScannerRGB to WorkingSpaceRGB (rendering intents)
- From: neil snape <email@hidden>
- Date: Sun, 08 Jul 2001 18:41:13 +0200
on 8/07/01 18:00, Terry Wyse at email@hidden wrote:
I assume the
>
preferred intent here would be perceptual not relative colorimetric. The
>
subsequent WorkingSpaceRGB to PressCMYK is then *usually* done with a
>
relative colorimetric intent (just seems to work better for most images). In
>
any case, you're needing to deal with out of gamut colors in same way.
Scanner profiles are uni-directional and the default rendering is
perceptual. It doesn't make sense to have colorimetric matching to unwieldy
source. Even though there are some scanner profiling apps that include a tag
for relative most of these are actually reference tags to/or duplicate
perceptual tables.
Question of scannerRGB to a linear working space. Good question indeed. The
most standardised for covering most of the film color, and most of the CMYK
space is Adobe 98. For a space to cover all the bases it'd be too big to
give heavy edits to in 8 bit. You said production workflow so I assume 16
bit isn't possible. Lab 16bit isn't officially there yet either. So you're
probably made the right choices already by default. You might like to try
JHolmes Ektaspace which covers all the film gamut for images that might be
re-purposed for photographic or large gamut printing. ECI have an rgb space
that should work well for cmyk production as it covers the whole cmyk gamut
but not quite the inkjet maximum gamut.
Neil Snape email@hidden
http://mapage.noos.fr/nsnape