Re: On the use of wide-gamut RGB working spaces [was: Photography editing spaces]
Re: On the use of wide-gamut RGB working spaces [was: Photography editing spaces]
- Subject: Re: On the use of wide-gamut RGB working spaces [was: Photography editing spaces]
- From: Marco Ugolini <email@hidden>
- Date: Tue, 07 Oct 2008 14:53:57 -0700
- Thread-topic: On the use of wide-gamut RGB working spaces [was: Photography editing spaces]
In a message dated 10/7/08 1:55 AM, Karsten Krüger wrote:
> If you start tweaking colors that you can not see on the screen
> anything can happen - and your screen is becomming the reference for
> your color (I guess this is what Ken tried to say).
Karsten,
As I mentioned earlier, that must not be necessarily so.
We are talking about losing detail in saturated colors, really. Even with a
limited display device, I indicated ways to keep a watchful eye on those.
So, saying that "[one's] screen [becomes] the reference for [one's] color"
sounds only partially correct to me.
> If your input device's gamut is shaped like a banana like some PhaseOne
> cameras, color rendering might get things wrong due to non continuous areas
> and a blue is printed purple (we had the discussion on this about 2 years ago
> on the list).
I don't recall that discussion in detail right now, and don't wish to rehash
it -- but mapping colors from a larger source space to, say, a much smaller
offset output space often forces the user to go somewhat "purple" from what
originally looked more blue, since there are only so many colors available
in the destination space that one can choose from at conversion time (even
with the aid of adjustment layers such as H/S, Selective Color, etc.).
> So there are advantages on both ways and a well educated decission
> has to be taken.
No doubts about that.
Marco Ugolini
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden