Filmscanners mailing list archive (firstname.lastname@example.org)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: filmscanners: which space?
The complexity comes in when you add translation into another device.
Lets say your original RGB values were 128,64,168, then after mapping
through CYMK and back to RGB you now have 138,16, 186 (I'm making these
numbers up, but they're somewhat believable. Now you want to print to a
printer that tends towards green and only takes RGB as input. So you print
a test print and low and behold its too green. You only have 16 levels of
green left to futz with.
From: "Maris V. Lidaka, Sr." <email@example.com>
Sent: Saturday, May 26, 2001 11:58 AM
Subject: Re: filmscanners: which space?
> Which is fine by me - so long as RxGxBx look the same as Rx'Gx'Bx' my
> will be what I want it to be.
> ----- Original Message -----
> From: "Karl Schulmeisters" <firstname.lastname@example.org>
> To: <email@example.com>
> Sent: Saturday, May 26, 2001 2:23 AM
> Subject: Re: filmscanners: which space?
> | That's not exactly the case. What is the case is that a particular Hue,
> | Intensity value - what our eyes perceive as a unique 'color value' can
> | rendered with multiple combinations of RGB. The same is not true for
> | So when you map from RGB into ANY color space, you essentially lose some
> | information. Namely you lose the mapping back to the original value
> | settings. That doesn't mean you can't get back to an RGB triplet that
> | look the same, but it does mean that say if you had set the RGB triplet
> | value to Rx,Gy,Bz then mapped to CYMK and you went back, Rx',Gy',Bz'
> | not have
> | x=x',y=y',z=z'.