Re: Clipping when converting from scanner space
Re: Clipping when converting from scanner space
- Subject: Re: Clipping when converting from scanner space
- From: Roger Breton <email@hidden>
- Date: Tue, 05 Apr 2005 11:51:34 -0400
>
>> If it does, mike, that means that your above statement is on the money
> and
>> the redistribution of the histogram is just a natural part of the
>> conversion. Now, a better question, IMO, would be for Lee to compare
> his
>> custom scanner profile in 3D to his choice of RGB working space to see
>> whether the gamut clipping is visible there. If it is then, logically,
> the
>> choice RGB working space should be iterated until he finds ne that
> does
>> NOT result in any clipping.
>
> That's logical, but I think you'd be hard pressed to find a working
> space that encompasses the entire scanner space, and editing in such a
> space might be problematic (uniformity, display accuracy) and not
> readily accepted by others. I would verify the scanner profile is valid
> and use a working space such as Adobe RGB or ECI RGB and not fret to
> much on the histogram shift, which essentially changes with the shift in
> RGB values from one space to the next.
>
> mike
Wouldn't you then choose NOT to convert to any RGB Working space? And
instead convert directly to your choice of Output profile? Which can handle
out-of-gamut conversions better than through a dumb TRC/matrix shaper
clipping. Is ECI RGB Lut-based or TRC/matrix based like AdobeRGB?
Regards,
Roger Breton | Laval, Canada | email@hidden
http://pages.infinit.net/graxx
_______________________________________________
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