Watch out! ACR 3.3 white balance seems hosed

jlw

Rangefinder camera pedant
Local time
6:53 AM
Joined
Aug 27, 2004
Messages
3,262
I just worked on my first large batch of Epson ERF files using Adobe Bridge and the latest Adobe Camera Raw 3.3, just released a couple of days ago. Although in general it works about like the previous ACR, I ran into one unexpected behavior:

When you double-click a file in Bridge to edit it using ACR, one of the controls available is a pop-up for white balance. There are various presets such as daylight, tungsten and fluorescent; an "Auto" setting, which attempts to guess a white balance based on values in the scene; and an "As Shot" setting, which in previous versions simply passed through the white-balance values that had been set on your camera at the time of exposure.

With ACR 3.3, though, I found that although the other presets work normally, setting the pop-up to "As Shot" actually chooses the "Auto" setting. There doesn't seem to be ANY way to get ACR to use the camera's white-balance values; choosing "As Shot" always yields exactly same results as choosing "Auto."

I haven't yet tried ACR 3.3 with any other digital cameras to see whether it does the same thing with their files, or only with Epson's.

If you decide to upgrade to ACR 3.3, I suggest you follow Adobe's recommendation to save your previous version so you can go back to it if you find you get the same behavior and it would be a problem for you not to be able to use the camera-selected white balance setting.
 
Hi, jlw!
Do you remember?
Adobe's new Lightroom Beta has the same bug ("as shot"="auto" or reverse). It cannot output the real wb value recorded by the camera.
What's going on with Adobe newly?
Regards
 
Back
Top Bottom