Remember,
in general, if you want to impact high values of some component
but not so much the low values, use gain (multiply/divide).
If you need to alter low values, typically to increase them,
use shift (add/subtract).
For
our first example we will use the Shift Operation on the
saturation component. One of the classic deficiencies of
electronic image/video capture is the rapid transition from
good, saturated color to washed-out color. This contributes
to, what I call the ‘tinny-look’ of digitally
captured images or video. An easy way to correct these types
of images is to fill-in some saturation using shift. That
is, make the saturation transition smoother.
Consider
the following image, taken by a digital camera:
To
fill-in some color saturation where it is lacking, we could
use the Asiva Shift Operation to shift upwards the lower
saturation values. Shift would be more appropriate than gain
here because we are trying to impact lower values. The screen
capture below shows how we would set the curves and the Saturation
slider to get the results we desire.
Notice
the Saturation curve in particular. What the curve shows
in general is lower level saturation values should be selected,
or impacted, more than higher level saturation values. In
particular, fully saturated pixels should not be touched
at all, nor should 0% saturated pixels - that is our grayscale,
and we certainly do not wish to throw off the white balance.
Also notice the Hue Map is flat-lined at “Full On”.
This means the saturation will be filled-in for all hue’s.
If we wanted to impact reds more than blues, or omit greens
altogether, we could set this curve appropriately.
The
Saturation slider has been set to about a 15% increase. All
other sliders are at zero so they will not impact the image.
I
encourage you to experiment with this basic use of the Shift
Operation on the saturation component. Tweak the Saturation
curve, and try different Hue curve settings, as well as Saturation
slider amounts.
Our
next example will use the Gain Operation to gain down some
of the higher level brightness values in a digital image.
Similar to the rapid color saturation transition, electronic
images are notorious for a rapid transition of light levels.
This also contributes to the poor aesthetic of digitally-acquired
images, in general.
Looking
at the image below, lets just say we choose to smooth-out
the brightness transition and also treat different basic
colors unequally. I mean, lower the brightness levels in
the reds and yellows more than in the cyans and blues.
To
accomplish the changes I described, we could use the Asiva
Gain Operation to gain down the brighter values. Gain would
be more appropriate than shift here because we are trying
to impact higher brightness levels more than lower brightness
levels. In fact, we do not want to touch the shadows at all
because that would actually contribute more toward a ‘contrasty’ image
- not what we are trying to achieve here.
The
screen capture below shows how we would set the Gain Operation’s
curves and the Value slider to get the results I described.
The
Value slider has been set to 0.80. This is the base number
the applicable Value components will be multiplied by. I
say “applicable” because the three curves will
select the pixels in the image to be affected.
Notice all other sliders are set to 1.0 so they will not impact
the image. This is due to the fact any number multiplied by 1.0
is equal to itself.
Pay
special attention to the last curve, Value. What this curve
shows is for the Gain Operation to affect high level brightness
values. The middle curve, saturation, is highest around 25%
saturation. We know by definition that the brighter pixels
we desire to change will tend to have lower saturation amounts.
Also notice the Hue Map is set to mostly change red to yellow
pixels and to a lesser degree, cyan to blue pixels.
The
results of gaining the brightness down, using Asiva’s
Gain Operation settings shown above, would tend to smooth
the transition from dark to bright areas. The best aesthetic
is something you will have to judge for yourself.
Written
by: Kevin K. Gordon, Chief Technology Officer SCGI |