White balance needs adjustment in RAW

I have a Canon 60D and shoot with AWB almost 100% of the time. I don't trust my self to switch between settings when moving from sun to shade to inside. On a recent trip I shot in RAW format for the first time. I was very happy with the results AFTER I changed the white balance from "As Shot" to "Daylight" for nearly every outdoor shot. (Using Camera Raw 8.5) The results this way are better than any adjustment I get to the JPG. Does this sound like a camera problem, PE problem, or just the way it is?

fishcad a écrit:
Thanks. It's not a huge problem but it would be nice if PS Elements allowed batch operations since I do this to so many photos. Just had some indoor photos from a wrestling tourney where changing the WB in Camera Raw from "As shot" to "Auto" made a big improvement to skin tones.
To keep the same settings for different pictures in ACR:
- Use the 'previous conversion' settings in the 'basic' tab drop-down menu
- open several images in ACR at the same time and apply the same choice.

Similar Messages

How to apply white balance from jpeg to raw version

I always shoot in RAW + jpeg format. Many times the jpeg will work fine and I still have the RAW if I want to take the time to tweak things a bit more.
But sometimes the jpeg stumbles on a white balance that works well for a particular image. If I want to apply that same balance to the RAW version, I would like to be able to read what that color balance setting (in K degrees I assume) is so I can copy it.
Is there a way to find that info somewhere? The exif will only give you the name of the setting (Flash, Auto, Cloudy, whatever...) but not the numerical info needed to apply it in Aperture's White balance adjustment.
I use a Nikon D600.
Thanks very much for any info!
Bo

OK, progress!
I found out from Iliah Borg on the dpreview.com forum that the utility ExifTool (or its GUI version pyExifToolGUI) will provide the R, B, G1 and G2 values for the white balance setting. They are provided as multipliers or absolute vaules. Example:
WB RB Levels : 1.51953125 1.8515625 1 1
WB GRBG Levels : 256 389 474 256
Now does anyone know how you can enter these type of numberic values in Aperture? The standard White Balance brick does not have input fileds for these types.

Stopping Customised White Balance defaulting when in RAW format

My preferred medium for photography is underwater, so it is crucial the white balance is set to the area and depth of the shot. When I use Photoshop CS3 to develop the shot in RAW, as soon as I click on to the shot in bridge it instantly reverts back to the default white balance, In UK fresh waters this usually means a strong green cast. Can anyone tell me how to stop this?

Hi Brett
Thanks I have now found the ACR within the Camera Calibration TAB, However, there does not seem to be enough adjustment to create the original shot. Also at depth I need to reset the white balance every few meters, so with 20 saved shots I can have say 6 different calibrations so it is pointless generating presets.
I propably should not say this but Capture One 4 recognises the shot the way I took it instantly,which then allows me to edit the original. The frustration is I do prefer Photoshop.

White balance shifting when importing raw files

When I import my raw files from my 5D mark 2 my white balance is set to 5200K, when in Lightroom it shifts to 4850K? Any body know why?

If there are no import presets being applied from the import pane, there's one other way this could be happening. If you're taking advantage of the ability to adjust LR's default import presets (NOT the same as what user web-weaver is talking about which is configured through the import panel) and you accidentally captured a setting other than "as shot" while making the changes, then this is likely your culprite.
This feature is fantastic for automatically applying ISO-specific NR to each file on import, but it can also catch other settings you may not have intended while configuring it. Go back to the files you originally used to set the defaults for each individual ISO, reset the WB to "as shot," and set defaults again. The menu option for this only appears in the develop module. Menu: Develop -> Set Default Settings...
You can also choose to wipe out all previously configured defaults by going to your preferences window, then Presets tab. Look for the "Reset all default Develop settings" button.
Hope this helps you or anyone else who comes along.

Bridge CS5 applies wrong white balance during thumbnail extraction (raw files only)

Hello to all Adobe Wizards,
Hobbiest photographer here. I use a Canon T2i and I have been shooting raw with auto white balance.
After I upload the CR2 files to Bridge, Bridge begins thumbnail extraction. This is when the problem begins: I watch Bridge extracting thumbnail photo after photo, turning them into wrong white balance one by one. After Bridge is done, I open one of these photos in Camera Raw, it shows the photo in "custom white balance". I was able to change it back to "As Shot". But every photo in Bridge now has custom white balance and is difficult to view in Bridge. This screenshot shows what my Bridge looks like after thumbnail extraction....
Yesterday, just out of curiosity, I took some photos with different white balance settings on the camera. I uploaded them to Bridge and Bridge over-wrote all the white balance settings. I then imported the same photos (from the same files) to iPhoto, they show up with correct write balance. Please see the second screenshot.
The third screenshot shows a unedited photo I opened from Bridge to Camera Raw, and the same photo as it appears in iPhoto, both unedited.
Again, this only happens to CR2 files. All tif, jpeg files are fine.
Any ideas?
Thanks!
-Wolfie

Any ideas?
First of all, shooting Raw has the benefit of changing the color temperature (Whit Balance) to what ever you like from whatever you shot in camera.
To me it seems you once have saved a custom white balance as default setting and this is been applied to every new file because you told Bridge to do so. The easiest way to get out of this is open a raw file in ACR and in the basic tab at the right side you see a small icon for sub menu (next to the word basic). Click on it and from the row choose 'Reset Camera Raw defaults' at the bottom.
Also decide whether you want to stay in 16 bit mode (as you are now as shown in the blue line under the preview). If you want to chance it back to 8 bit just click on that blue line and choose your options from that menu. You only have to do this once for the files from that same camera, ACR remembers the settings for you.
Using 16 bit mode has advantages when using critical color corrections (but then you also should change the color mode to ProPhoto in my opinion). The disadvantage is that 16 bit doubles the file size compared to 8 bit
Having set the ACR defaults should effect your thumbs immediately by building new thumbs and previews but if not you must choose purge cache for folder from the menu tools / cache/ purge cache for folder. Now the new settings will be applied.
It may take some time so let Bridge do its work properly before starting other jobs in Bridge (see the activity bar bottom left to check if Bridge is still caching).

Can camera white balance be adjusted?

A friend of mine has taken some images that look like old images that have weathered/faded over time, but they are brand new! I suggested that it looked like the white balance was set wrong. Is there any way to adjust it (it looked like it was set to florescent lighting)?

The default Camera app does not have an adjustment for white balance. But there are other camera apps in the App Store that have this feature. There are also photo editing apps that allow changes to white balance. The iPhoto app is one of many.

Expand white balance beyond 2000K for RAW files

I'm finding, with the mixture of lighting situations I find at weddings (evening venues especially) that 2000K sometimes is not enough for me to get a correct white balance. I'm having to apply a filter on top to get a true white balance.
Is there any reason why 2000K is the current limit? If not, could you expand it past 2000K?
Thank-you!

Try http://robertreiser.photography/articles/proper-infrared-white-balance-in-lightroom/

Setting White Balance in Camera RAW

I have heard and read (what apppears to be) contrary information about using the White Balance Tool in Camera RAW.
I have sometimes heard that I need to select a naturally white point (as opposed to a specular / highlight point); but I have also heard that I need to select a neutral gray point.
I am wondering if it's either / or and that it all amounts to the same thing.
Can anyone assist and explain the differences?

You can use any area that has no colour contend regardless of its tonal value. For instance you can use full black to se WB. Note this is not the same as setting black and white points in ACR

Help! Why does Aperture automatically adjust my white balance?

Hey,
Just wondering if anybody knew why Aperture seems to want to automatically adjust the white balance settings of the RAW .NEF images I've been importing. I mean, on an example image, the in camera white balance was about 5900K with no hue adjustments, but when I imported it into aperture, it looked completely different. Sure enough, Aperture had set a color temp of 5475K and a hue of -22. If I wanted it to be adjusted, I would've asked, but I spent the time getting the white balance right in camera for a reason. I really don't want to have to go back and adjust every image manually. That would defeat the purpose. Please, lend some insight.

I have a D80. Do you think apple will eventually develop a solution to this problem, or some sort of workaround? In the meantime, might I be better off just using the proprietary software, like captureNX? Or, how about adobe camera raw?

Camera Raw crashes with use of white balance eye dropper.

Using PS CC2014.2.1
Since this update, whenever I use the white balance eyedropper in Camera Raw, if placed over an over exposed region, instead of the dialogue box popping up to warn that the area is too bright, the system just freezes. Have to launch task manager and close PS.
If eyedropper is placed on non-over exposed (not clipped) area, it seems alright. Anyone else experiencing this?

Due to the current unavailability of clairvoyants and mind-readers in the forum, we respectfully request you supply sensible, complete details.
BOILERPLATE TEXT:
Note that this is boilerplate text.
If you give complete and detailed information about your setup and the issue at hand,
such as your platform (Mac or Win),
exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
etc.,
someone may be able to help you (not necessarily this poster, who is not a Windows user).
a screen shot of your settings or of the image could be very helpful too.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

After adjusting white balance in ACR, images are opening in Ps at a different size.

Can anyone explain like I'm 5 why this is happening, and how to prevent it? Thanks!
Negatives are scanned at 3200dpi, and 24bit depth. This is the metadata from Bridge.
Default settings in Camera Raw
After opening in Photoshop.

Scanned direclty into photoshop. And if I open the tif from explorer or bridge, bypassing Camera Raw, it opens as the 75mb file size. I thought it might have somethign to do with the color, as Bridge labels bits/channel as 'Bit depth', but the images all are 24bit, even after White Balance correction in Camera Raw.
Thanks for taking the time to help me figure this out. It's been causing a huge problem this week.

White Balance Effect

CS6 Production Premium Suite
Win7x64
Nvidia GForce GTX 470
Intel i7 930 @2.8GHz
12 GB memory
Canon XA10
Does Premiere have a White Balance effect like Camera Raw which adjusts the white balance Kelvin?
If not, why not since Camera Raw has one.
Is there a third party that does?
Thanks in advance.

I use an Expo Disc to manually set the white balance for the Canon XA10. However, the lighting was suddenly changed while shooting. Unfortunately, the XA10 greys white balance changes while shooting. The speaker would have gone ballistic if I asked her to stop for a moment to change to auto white balance. So I was forced to shoot with a manual white balance setting that looked great before the lighting change but looked awful afterward. Hence, the need to make white balance adjustments in post production.

Canon XHA1S white balance

Hello all.Is there a way for me to do an auto white balance that shows up on the LCD screen showing me what color temperature the sensor picked?That way I can check to make sure that I manually adjust the color temperature close to what the XHA1S buildt in meter read.I do'nt have the money for a color temperature meter.I can't find any stores that sell color temperature charts.Thank you.

Wayalive, Unfortunately no, I have as yet found no solution.
I'm still hoping that the issue can be resolved, but we have to keep it alive and not accept that LR/ACR will not handle white balance correctly for CR2 files.
My specific dilemma is that using white balance cards along with IR does not produce the same results as the proper handling of the white balance stored with the image. Specifically, I'm usually setting my white balance to a color such as the green of the leaves in a specific picture so as to produce a unique result. Attempting this using the custom white balance feature of Camera Raw against a CR2 file produces a vastly inferior result. It's the unique element of having both red and in this case green be treated as white that gives the false color images from the camera their specific appeal. This trick is the foundation of false color IR image creation where you trick the camera's internal software into producing what it thinks is a proper color image. Having ACR muck it all up after the fact is a big problem.
Post processing can, with a lot of effort, come close but this is an unacceptable penalty for using a camera and format that is stated to be supported.
Don Solomon,
Thanks for the info on LightZone, I'll look into giving that a try and see if it can clear up my issues as well.

ACR 4: White Balance readings off of a target

In the good old days (ACR 3.7 and previous), I could shoot a white balance target, then open the image in ACR and use the eyedropper to set the white balance. No more. Now, I get a message that states - "The clicked area is too bright to set the white balance. Please click on a less bright neutral area."
Well, I'm using (and have been using) Danny Pascale's White Target that was made specifically for this purpose. (http://www.babelcolor.com/main_level/White_Target.htm)
Something has changed, and it's not for the better. I've tried decreasing the exposure in ACR, to make sure the values are far below 255, to no avail. Interestingly, the first measurement "click" does nothing. The second gives the error. The is very reproducible. Something's not right...
--Rich Wagner

Ok...
"You sure seem helbent on using your White Disk as a target for the white balance in Camera Raw...as you've found out, that's a bit less than optimal if your sensor exposure will likely produce a clipped channel since Camera Raw won't let you."
Well, when I'm crawling around in the mud in Costa Rica, Ecuador, or Peru, soaked, the ColorChecker card doesn't fare well. I've gone through a number of them, and in *my* field use, they suck. Period. In a studio, they're fine. I still own several. I just measured one for the numbers I gave above. I'm helbent on having something that is
reliable in my use. I could care less what it's called or who makes it. On the other hand, you seem insistant that the White Disk is inferior, and I'm trying to figure out why (other than the fact that Mr. Knoll used the ColorChecker card when designing ACR).
"What Thomas has stated and what I know to be a fact, is that the lightest grey of the CC is what the white balance tool is designed to use. It's light enough that it's not too far down the scale but dark enough to not worry about clipping. So, the ideal is to use the same patch that the white balance tool in Camera Raw was designed around."
Really? On my card, the lightest gray on the ColorChecker is
not the most neutral. The
second gray is. You can see the numbers above. Are you implying that Camera Raw will be more accurate making a WB measurement off of a patch that is not neutral, compared to one that is?
"So, what is it about your White Disk that has you so fixated on using WHITE (at the risk of clipping)? Yes, you can use it as long as it doesn't clip...is it optimal? No."
Argghhh... If I shoot a test shot and the White Disk clips, then guess what? I'm overexposing! Time to adjust the exposure before going on. This is easy to see on the White Disk because I get zebra stripes. I'f I'm shooting a gray card, I don't get that feedback and I may later discover that
important stuff was clipped, and it's too late! Sure, I can color balance just fine, but important highlights are gone. Which is most important? I can always eyeball color temperature - it's subjective, anyway. Or I can measure off something neutral in the shot. Clipped channels? Data lost is data lost...
Perhaps our shooting conditions are very dissimilar. I have found the White Disk to be a useful tool, just like many others that I have. It works (against all expectations?) and it works well. If I overexpose a neutral white target, I am often overexposing something else of interest. It becomes a
red flag when checking exposure, since I often cannot even see the histogram on the back of the camera. I am certainly NOT recommending that everyone switch to using a White Disk. I have just been surprised at the response of those who feel that for whatever reason it
cannot work as well as gray. I see no theoretical reason why not - still. Show me the math, or a give me clear-cut reason. My understanding (and experience) says otherwise. Or to put it another way, if it didn't work, I wouldn't use it, and neither would anyone else. If someone frequently overexposes their shots and relies on highlight recovery, it's probably not a good tool for them (unless it helps them correct their exposure).
--Rich

White Balance eyedropper not working?

Hi all,
Has anyone else tried doing a white balance adjustment in Aperture 2.0.1 with the eyedropper?
In 1.5.x, it worked great -- I just clicked the eyedropper, clicked on a known-neutral-grey area of my photo, and the white balance was adjusted very well.
In Aperture 2.0.1, I click on the eyedropper, then click on the same neutral-grey area, and for a second the photo adjusts beautifully -- then the white balance controls seem to randomly adjust back, and I get a photo that is no more color balanced than the original one.
Is anyone else seeing this, and/or does anyone have any ideas why Aperture won't stick with the initial adjustment I'm seeing?
Thanks in advance!
\marc

Still not working. I think the root cause of the problem is the mechanics of using the tool itself; I hope this screen shot shows up below ...
Here I have APPLIED EFFECTS open, and have selected Midtones (Greys) to be expanded so that the eyedropper and other details appear:
Now, just below where it has a box and "Impacted frame area in white" (which I know is a checkbox allowing the area effected to be seen), there is a little color box and an eyedropper.
What EXACTLY do I do to select (activate) the eyedropper and subsequently tell the program what I feel should be grey in the selected clip?
As mentioned before, I can click it and the cursor briefly changes to the same shape as the eyedropper. But as soon as I move the cursor a fraction, it changes back to an arrow (normal cursor) shape. Even then, going to the area I need to select in the image, and then clicking it, does exactly nothing to the appearance of the image shown -- even if the colors start way off. No correction at all. It is as if the tool does nothing. The color wheels below all this DO work however - it's just the eyedropper that doesn't do anything. This just cannot be Adobe's intention. I am convinced there must be some flaw in how I am selecting the tool itself. And the user guide - needless to say - is worthless in explaining the mechanics.
So very frustrating. This appears to be the only thing wrong with the program - nothing else seems amiss.
NOTE: To add insult to injury, this promised white/gray/black balance feature and the three-way-color corrector is the SOLE REASON I purchased the software. Funny.

White balance needs adjustment in RAW

Similar Messages

Maybe you are looking for