Re: Euclidean distances in L*a*b* - problem!
- From: philip@xxxxxxxxxxxxxxxxx (Philip Homburg)
- Date: Fri, 8 Jul 2005 09:40:14 +0200
In article <1120799928.513330.147090@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
kalfholo <mdmcgr@xxxxxxxxx> wrote:
>The relationship is the following. To minimize the data storage
>requirement and maximize the preservation of visual detail, we should
>store images in a perceptually uniform format.
That statement may be true when storage costs are very high. If you
can afford 8-bit/ch tiff (with whatever encoding you use) you can in
many situations just as well afford 16-bit/ch linear storage.
I guess it would be nice to have a jpeg version that can deal with LAB.
>In some cases it's
>convenient to perform image operations directly in that format. For
>example one can do a tone correction by manipulating L* with minimal
>effect on hue and chrominance--within the limitation of gamut of
>course.
Assuming that with 'tone correction' you mean changing the brightness,
you can do that in just about every other commonly used space (both linear
and gamma corrected) as well. I don't see the advantage.
>The crank position is that linear data _is_ perceptually linear
>and that all image processing operations should be performed only in
>linear space.
I think there may be some truth in the second part of the statement.
('should' is not as strong as 'can').
Lots of operations related to the underlying physics and math of light
can only be understood (easily) in linear space. What kind of MTF
do you get when to perform sinc based interpolation in LAB?
>You are quite right that _some_ operations do need to be
>done in linear space--matrix operations, white point correction etc.
>But in many cases but not all, it's not hard to do this with images in
>non-linear space with lookup tables. They are calculated with floating
>point math which effectively passes through linear space but input and
>output are non-linear.
I can't see the advantage of doing complicated operations in LAB using
lookup tables, when you can just as well convert first to linear space,
perform the operations and then convert back.
Assuming that monitors are profiled in addition to being calibrated,
you may want to do a matrix multiplication before displaying data anyhow.
--
That was it. Done. The faulty Monk was turned out into the desert where it
could believe what it liked, including the idea that it had been hard done
by. It was allowed to keep its horse, since horses were so cheap to make.
-- Douglas Adams in Dirk Gently's Holistic Detective Agency
.
- Follow-Ups:
- Re: Euclidean distances in L*a*b* - problem!
- From: Chris Cox
- Re: Euclidean distances in L*a*b* - problem!
- References:
- Re: Euclidean distances in L*a*b* - problem!
- From: Mike McGuire
- Re: Euclidean distances in L*a*b* - problem!
- From: Philip Homburg
- Re: Euclidean distances in L*a*b* - problem!
- From: kalfholo
- Re: Euclidean distances in L*a*b* - problem!
- Prev by Date: Re: Euclidean distances in L*a*b* - problem!
- Next by Date: Re: Euclidean distances in L*a*b* - problem!
- Previous by thread: Re: Euclidean distances in L*a*b* - problem!
- Next by thread: Re: Euclidean distances in L*a*b* - problem!
- Index(es):
Relevant Pages
|