On May 29, 12:31 pm,
nos...@nospam.com (Paul Ciszek) wrote:
> I went ahead and bought Photoshop Elements. It turns out that the
> ability to separate color channels is present but inaccesible to the
> user, so I spent another $12 on an extension called Elements+ which
> was recommended by several sites. Elements has a nice, easy-to-use
> tool for adjusting the contrast scale of any color channel arbitrarily,
> but once I use it, the next time I look at a histogram of that color
> channel, it consists of a set of evenly spaced spikes--what I would
> expect to see if I stretched the contrast of an 8 bit channel. I
> have my doubts as to whether I am really working in a 16 bit per
> channel color space. If I were, I should be able to stretch the
> contrast by a factor of four as I have been doing and still have too
> many levels of brightness to be able to count them in a histogram.
> The explanations that seem most likely are:
>
> 1) Some of the Photoshop Elements tools operate in 8-bit mode
>
> 2) While Photoshop Elements is willing to import RW2 images, they
> pass through an 8-bit-per-channel format along the way
>
> 3) The RW2 format itself does not have as much dynamic range as I
> thought it did.
>
> I have been googling for details on the RW2 colorspace and all I have
> been finding is lists of programs and converters that can handle it.
> Is there a good description of the RW2 format anywhere?
I'm not an expert in using PSE in the way you describe, but you ARE
seeing the effects of posterization/destructive editing. I don't
believe the problem is with the RW2 format, it is photoshop, itself.
Some/many PSE (and PS) tools/filters certainly operate only in 8-bit
mode. What makes you think you were in 16-bit mode? Did you
explicitly set it? I believe 8-bit is the normal default. I believe
the tool generally will prevent you from doing 8-bit operations if you
are in 16-bit mode, and usually will ask if you want to convert to 8-
bit.
ACR (the raw converter) is the non-destructive part of PSE (and PS).
You should do as much work as possible in ACR, especially things like
white balance or adjusting contrast, etc. After you go into
photoshop, operations are generally destructive, so it is important to
use layers to protect the original. "Smart objects" allow you to
build a non-destructive flow in PS, but only works with a limited
number of tools/filters. Not sure if smart objects have made it to
PSE, yet.
Unfortunately, the capabilities available in ACR in PSE are not as
extensive as what you get in ACR in PS or the ACR engine built into
Lightroom. Actually, I think the engine may be the same in PSE, but
the necessary info in the side-car is missing in PSE (that is what an
Adobe support person told me). For example, the noise tool and
perspective adjustment aren't available in ACR in PSE (or at least
weren't a couple years ago when I tried it).
One of the reasons I use Lightroom most of the time is it is
completely non-destructive. When I have to pop over to CS5, I use
smart objects to preserve the non-destructive pipeline as much as
possible. If I have to use tools that are destructive in CS5, I save
those steps for last.
As far as 8-bit vs 16-bit is concerned, I have found that 8-bit for
the destructive edits are usually fine, as long as you have already
made the white-space and histogram adjustments non-destructively in
ACR or LR first.