Re: Save IT8 scans: which RGB color space?
Re: Save IT8 scans: which RGB color space?
- Subject: Re: Save IT8 scans: which RGB color space?
- From: Andrew Rodney <email@hidden>
- Date: Tue, 15 May 2001 19:49:22 -0600
on 5/15/01 7:07 PM, Wim Melis at email@hidden wrote:
>
This is a question that's been bugging me for some time: if you make an
>
IT8 scan, for processing in a profiling app, what RGB space should you
>
save that scan in?
Scanner RGB. That is, the "raw" RGB the scanner provides. Once you profile
that recipe of RGB, you now define it with that profile. Or to put it
another way, you don't want to scan into a space other than what the scanner
provides in it's virgin state (if possible).
>
I've been able to avoid the question sofar, since both scanner software
>
packages I used (first Linocolor, now Colorquartet) have an option for
>
making a calibration scan.
The scanner software is smart enough to request and provide "raw" scanner
RGB with the goal of profiling that RGB.
>
But for some debugging I now need to make an IT8 scan as if it were a
>
normal scan, and I can't fake it anymore...
What is a normal scan? Can you lock the scanner down to at least get
consistent behavior out of the scanner to profile that recipe of RGB? If
not, profiling it isn't going to work. You certainly don't want to do
anything like attempt to alter the RGB into some predefined Working or
Output space. You want to attempt to get that "raw" RGB. Sometimes that's
not possible. It's all due to the software driving the scanner and how
difficult it is to get to this "raw" RGB. Notice the quotes around raw. It's
quite possible that the RGB provided has been run through a number of
processing steps.
Andrew Rodney