ScannerRGB to WorkingSpaceRGB (rendering intents)
ScannerRGB to WorkingSpaceRGB (rendering intents)
- Subject: ScannerRGB to WorkingSpaceRGB (rendering intents)
- From: Terry Wyse <email@hidden>
- Date: Sun, 08 Jul 2001 12:00:28 -0400
I've been following the "PS6 intent setting for softproof" thread with some
interest and it got me thinking (again) about rendering intents,
particularly from "ScannerRGB" to "WorkingSpaceRGB". A few questions and
thoughts:
* The default rendering intent in PS6 Color Settings; I generally think of
this in terms of only RGB>CMYK but I assume it applies to ALL profile
conversions including RGB>RGB, unless of course I use the Convert to Profile
option. Correct?
* In converting from ScanRGB to WorkingSpaceRGB, I've generally gone the
route of converting to a more "print-friendly" RGB working space (usually a
smaller space than the scanner) such as AdobeRGB or BruceRGB. 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.
The other tactic that I've given thought to is to convert from ScanRGB to a
WorkingSpaceRGB profile that's either the same "size" as the scanner or
possibly slightly larger. In this case, would the rendering intent (percept
or relcol) make any difference at all? I assume the smaller space would just
get mapped to the larger space 1:1 so rendering intent is irrelevant. Is
this true or is my thinking flawed?
I'm trying to formulate a method that's relatively foolproof in a prepress
production environment where multiple operators are handling the file
conversions and not all are "clued in" so to speak on color management in
general and rendering intents in particular. I'm thinking that moving the
ScannerRGB data to a working space that absolutely preserves the color gamut
of the scanner may be a better choice, particularly for archiving the RGB
scan, but with the need to move the scan data to "well-behaved" working
space instead of archiving the scan with the ScannerRGB profile embedded.
Thoughts?
Terry
_____________________________
Terence L. Wyse
Resident Color Geek
All Systems Integration, Inc.
http://www.allsystems.com
email@hidden
_____________________________