White balance in photoshop cc

I only get auto, custom and as shot in choices of white balance in photoshop cc. I don't know why.

Is this with a RAW file, and if so, what camera was it taken with?
[EDIT] Please always give as much information as possible when asking questions.

Similar Messages

White balance feature in Photoshop CS4?

Is there a white balance feature in Photoshop CS4 [like in Lightroom]?

WB is a bit of misnomer... what your fiddling with is temperature. And it's not always in balance or using white (what is white in higher dynamic range images anyway?).
To be honest I find the wb approach a bit cludgy in PS and far prefer to look at it in ACR if I can.
Curves in LAB has th best response for me to correct colour casts... the colour balance tool in RGB is really doesn't live up to its name...as per the photo filters that dont. As ACR shows, you cant just slap orange over an image and say its warmer.

Imported images are given "flash" as white balance

Since I implemented LR3 and played around a.o. with some presets, all of my images (RAW) at import are transformed to the "flash" white balance, as shown in the Library right colomn and as can be seen in the image.
The images come out of the camera with a wb-info as the one set to the camera when shooting the image, so no problem with the camera. So I suspected some initial preset, but couldn't find it. Then, I imported the files into Photoshop 4 and Elements, and exactly the same thing happens: they convert immediately to the flash WB. So, is there a settings file that is shared by all three programs?
I checked the same files on my lap-top with LR3, and there LR shows the wb settings that I set on my camera; so the problem is with settings on my one PC.
Has anybody any idea how to get rid of this setting?
Rob

robijsselstein wrote:
My surprise is that the other programs use the same defaults apparently
The Default you set in LR is valid for ACR, no matter whether used under LR or under PS/PSE. Their values are also stored in the Camera Raw settings directory, not in the LR directory.
Beat

White Balance Tool

I am using the following:
latest CS4 version
latest camera raw version
MAC 10.5.5
Can anyone help please - I open bridge, then open a raw file in camera raw. I then use the white balance tool. I go over the image with this tool to see the pixel values - but there are no pixel info showing on the R G B settings on the right (just below the graph). In Photoshop, this tool is working fine.
Is there a preference setting to activate this tool to work properly in camera raw?

Well, I have tested it again and the preference to start Bridge at log in, seems to be doing it. I ticked this off, closed down and started Bridge manually and the tool fully works OK with my work space. But could be something else, I don't know, but starting Bridge at log in on my computer seems to be this.
The saved work space I have set up as follows - on the left side of screen I have placed my favorites, folders, collections panels at top left, then underneath these, I have placed filter, metadata, keywords panels. I have no panels on the right and just have big thumbnails on the main area.
Anyway, thanks again, I can live with this now, I just start Bridge manually :-)

White Balance Setting Problem

APPLE COMPUTER:
THREE BASIC QUESTIONS THAT NEED TO BE ANSWERED.
1. HOW DOES THE WHITE BALANCE TOOL WORK IN APERTURE?
2. HOW DO YOUR SOFTWARE ENGINEERS AND "PHOTOGRAPHIC CONSULTANTS" USE IT TO SET WHITE BALANCE?
3. WHAT ARE THE SIMILARITIES AND/OR DIFFERENCES IN ITS USE AS COMPARED TO SIMILAR TOOLS IN CAPTURE ONE PRO AND ADOBE PHOTOSHOP?

Test Results:
Aperture 1.1:
Image Temperature: 3594
Tint: -17
When using the white balance tool on a white section of a photo, the RGB values changed from R 255 G 234 B 192 to R 255 G 230 B 197 and the Temperature changed to 3946 and Tint to 12.
The photo still remained unacceptable.
When usint the white balance tool on a grey section of the same photo, the RGB values cahnge from R 211 G 178 B 126 to R 208 G 180 B 162 and the Temperatue changed to 3154 and Tint to 2.
The photo still remained unacceptable but was notably improved.
Using Capture One Pro, the results were as follows:
Temperatue: 3850
Tint: -10
When using the white balance tool on a white section of the same photo, the RGB values changed from R 255 G 241 B 200 to R 244 G 244 B 244 and the Temperature changed to 2500 and Tint to -16.
Photo was very acceptable with no perceivable colour cast.
When using the white balance tool on a grey section of the same photo, the RGB values changed from R 190 G 153 B 108 to R 153 G 153 B 153 and Temperature to 2550 and Tint to -2.
Photo was very acceptable with no perceivable colour cast.
From this quick test on a photo, I can draw the following conclusions:
1. Aperture interprets temperature and tint data differently from Capture One Pro, although this likely due to the use of a camera profile within Capture One Pro;
2. Using the white balance tool in Aperture on a "white" section does not neutralize the RGB values;
3. Using the white balance tool in Aperture on a "white" section does not correctly remove a colour cast within a photograph;
4. Using the white balance tool in Aperture on a "grey" section does not neutralize the RGB values; and
5. Using the white balance tool in Aperture on a "grey" section does not correctly remove a colour cast within a photograph, although it does work better.

White Balance in Camera raw

Every time I open an image from Bridge in CS6, into camera raw the white balance always defaults to fluorescent. How can I change default opening to read as"shot as"?

Hi there! Because the forum you originally posted in is for beginners trying to learn the basics of Photoshop, I moved your question to the Camera Raw forum, where you'll get more specialized help.

Wrong white balance in Bridge

Since I reinstalled my computer I have a problem with displaying Canon CR2 files in Bridge - white balance in just incorrect. When I open it in Camera RAW, for about 1 second it displays still incorrectly, but then colours of the picture change and white balance is correct - I can even see that histogram changes slightly at the same moment. Than it opens in Photoshop correctly too. White balance is set to "as shot". I have PS CS6 and ACR 8.1 as part of Creative Suite 6 Design & Web Premium (all updates are installed). Anyone can solve the problem? I can say that I tried to install Creative Suite on 2 different computers and the problem is in both cases.

But when I open fool preview in Bridge (space, then left mouse click), after a short time when preview renders, the picture becomes fine. So I wonder what picture is displayed in Bridge non-full-screen preview?
Let's first focus on your preference settings. Try these settings:
In Bridge under Adobe Bridge CC open the Camera Raw preferences.
In the section 'Default Image Settings' make sure the the above 2 are NOT checked (Auto tone and auto grayscale)
It is useful to have checked defaults to specific serial number when you did generate a custom default in ACR and iso specific is only useful if you have saved all different iso settings as different ACR defaults.
Then go to same menu and open Bridge Preferences.
In the section Cache under options have only a checkmark in front of 'Keep 100% previews in Cache', don't use the option to export cache to folder.
Also increase the slider for cache size a bit, somewhere half way or left to halfway should be good enough.
Under Advanced / miscellaneous only have a check mark in front of generate monitor sized previews, leave the other 2 blank.
Then in the content window with the problem files be sure to have no hidden cache folders. Use menu view / show hidden files and search for document icons with BridgeCache and BridgeCacheT. If they are here delete both to the trash.
Then restart Bridge and try again
Also might be related to not having synced the color settings in Bridge when having more Suite apps installed from CC.
Any advice how can I check it?
When you have only PS installed Bridge uses the color settings you have saved in there, otherwise you should sync the Bridge color settings for correct colormanagement.
In PS go to the menu edit / Color settings
Check if your settings are what you want and either read the name already given or save these settings under a proper name.
Then in Bridge use the same route (edit/Color Settings and check if the saved settings file is active in the list (Bridge tells you in this menu if the settings are synced or not so that should be easy to check.

Adobe DNG converter is corrupting NEF files. The color is way off and it's not the camera white balance.

I was using the converter for a few months and it was working fine. Now it will convert the files, but the color is really messed. I know it is not the white balance, because the same files convert fine to TIF files through Nikon's software. I am using this converter for Nikon d610 NEF files. Here's a sample DNG and the same image in TIF. Can anyone help? Thanks!

When you use the DNG Converter to make a DNG from an NEF, the DNG Converter applies the default Camera Raw settings. When I open your DNG it looks fine, but when you open it, it looks off. That is because you've some how set your Camera Raw defaults to have a bunch of customized settings specific to a particular picture, instead of having them all be normal settings. Below you'll see what Photoshop is saying the settings of the DNG-Converted-JPG are, with the non-defaults marked in bold. The main problems are the WB being custom and a bunch of HSL setting changes.
Here is what Photoshop reports that the JPG was created using:
      <rdf:Description rdf:about=""
            xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
         <crs:RawFileName>hug_8290_0215_1.dng</crs:RawFileName>
         <crs:Version>6.0</crs:Version>
         <crs:ProcessVersion>5.7</crs:ProcessVersion>
         <crs:WhiteBalance>Custom</crs:WhiteBalance>
         <crs:Temperature>5732</crs:Temperature>
         <crs:Tint>+26</crs:Tint>
         <crs:Exposure>0.00</crs:Exposure>
         <crs:Shadows>5</crs:Shadows>
         <crs:Brightness>+50</crs:Brightness>
         <crs:Contrast>+25</crs:Contrast>
         <crs:Saturation>-4</crs:Saturation>
         <crs:Sharpness>90</crs:Sharpness>
         <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing>
         <crs:ColorNoiseReduction>25</crs:ColorNoiseReduction>
         <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
         <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
         <crs:VignetteAmount>0</crs:VignetteAmount>
         <crs:ShadowTint>0</crs:ShadowTint>
         <crs:RedHue>0</crs:RedHue>
         <crs:RedSaturation>+11</crs:RedSaturation>
         <crs:GreenHue>0</crs:GreenHue>
         <crs:GreenSaturation>0</crs:GreenSaturation>
         <crs:BlueHue>+12</crs:BlueHue>
         <crs:BlueSaturation>+2</crs:BlueSaturation>
         <crs:FillLight>0</crs:FillLight>
         <crs:Vibrance>-6</crs:Vibrance>
         <crs:HighlightRecovery>0</crs:HighlightRecovery>
         <crs:Clarity>0</crs:Clarity>
         <crs:Defringe>0</crs:Defringe>
         <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
         <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
         <crs:HueAdjustmentYellow>+1</crs:HueAdjustmentYellow>
         <crs:HueAdjustmentGreen>+5</crs:HueAdjustmentGreen>
         <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
         <crs:HueAdjustmentBlue>-9</crs:HueAdjustmentBlue>
         <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
         <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
         <crs:SaturationAdjustmentRed>-2</crs:SaturationAdjustmentRed>
         <crs:SaturationAdjustmentOrange>+14</crs:SaturationAdjustmentOrange>
         <crs:SaturationAdjustmentYellow>+25</crs:SaturationAdjustmentYellow>
         <crs:SaturationAdjustmentGreen>+26</crs:SaturationAdjustmentGreen>
         <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
         <crs:SaturationAdjustmentBlue>+32</crs:SaturationAdjustmentBlue>
         <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
         <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
         <crs:LuminanceAdjustmentRed>+40</crs:LuminanceAdjustmentRed>
         <crs:LuminanceAdjustmentOrange>+13</crs:LuminanceAdjustmentOrange>
         <crs:LuminanceAdjustmentYellow>+3</crs:LuminanceAdjustmentYellow>
         <crs:LuminanceAdjustmentGreen>+15</crs:LuminanceAdjustmentGreen>
         <crs:LuminanceAdjustmentAqua>+3</crs:LuminanceAdjustmentAqua>
         <crs:LuminanceAdjustmentBlue>+4</crs:LuminanceAdjustmentBlue>
         <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
         <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
         <crs:SplitToningShadowHue>231</crs:SplitToningShadowHue>
         <crs:SplitToningShadowSaturation>32</crs:SplitToningShadowSaturation>
         <crs:SplitToningHighlightHue>45</crs:SplitToningHighlightHue>
         <crs:SplitToningHighlightSaturation>33</crs:SplitToningHighlightSaturation>
         <crs:SplitToningBalance>+74</crs:SplitToningBalance>
         <crs:ParametricShadows>-39</crs:ParametricShadows>
         <crs:ParametricDarks>-7</crs:ParametricDarks>
         <crs:ParametricLights>-15</crs:ParametricLights>
         <crs:ParametricHighlights>+14</crs:ParametricHighlights>
         <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
         <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
         <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
         <crs:SharpenRadius>+1.0</crs:SharpenRadius>
         <crs:SharpenDetail>25</crs:SharpenDetail>
         <crs:SharpenEdgeMasking>0</crs:SharpenEdgeMasking>
         <crs:PostCropVignetteAmount>-24</crs:PostCropVignetteAmount>
         <crs:PostCropVignetteMidpoint>50</crs:PostCropVignetteMidpoint>
         <crs:PostCropVignetteFeather>97</crs:PostCropVignetteFeather>
         <crs:PostCropVignetteRoundness>0</crs:PostCropVignetteRoundness>
         <crs:PostCropVignetteStyle>1</crs:PostCropVignetteStyle>
         <crs:PostCropVignetteHighlightContrast>0</crs:PostCropVignetteHighlightContrast>
         <crs:GrainAmount>0</crs:GrainAmount>
         <crs:ColorNoiseReductionDetail>50</crs:ColorNoiseReductionDetail>
         <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
         <crs:ToneCurveName>Medium Contrast</crs:ToneCurveName>
         <crs:CameraProfile>Adobe Standard</crs:CameraProfile>
         <crs:CameraProfileDigest>51B4314CF8312BA027EF3FC60481FB35</crs:CameraProfileDigest>
         <crs:HasSettings>True</crs:HasSettings>
To fix the problem you're gonna need to reset your camera raw defaults:
And then be careful when saving new camera raw defaults with the menu item just above, that your image has the camera raw defaults applied to it, except whatever small change you want to be the new default.

White Balance Selector Tool operation

The WB selector tool still appears as though it only selects one pixel in the the "Pick a Target Neutral" array display window, the one with the x over it (regardles of whether you scale the matrix to 16x16 or 5x5 with the scale slider. It does not appear to allow averaging of adjacent pixels to reduce the effect of random noisy pixels messing up the wb. This has already been brought up in previous threads and the LR team apparently dismisses the concern. Reminder to Adobe Labs: we don't all shoot with relatively noiseless Nikon D3/ D700s. Our cameras do produce significant color noise even at relatively low ISOs. So when we attempt to find a neutral patch or pick a spot on a neutral whibal card with the color picker tool, we see a random array of various shades of gray, some a little more purple, some a little more green in the tool's selection window. Depending on which pixel we place the X on, we get a different white balance. EVEN THOUGH WE ARE HOVERING OVER WHAT IS SUPPOSED TO BE AN EVENLY LIT NEUTRAL BALANCE CARD! Could you guys please talk with your Photoshop colleagues and figure out how to give us a 5x5 or NxN pixel averaging white balance picker. Or maybe you confirm that I am wrong and in fact this tool already DOES average all the pixels I see in the "Pick a Target Neutral" pixel array display? This would be far more useful an option than the ability to put a decorative flourish at the bottom of a menu panel! Thanks.

In addition to the point being made above in regards to a 3x3 or 5x5 pixel eye dropper for the selection of your color balance(color temperature), it would be great to have an eye dropper to select & set your black, white & mid grey(18%) point inside of lightroom to not only neutralize any color cast but also to set your tonal values with a x-rite color checker or similar reference.

White Balance tool and Camera Calibration Profiles

Downloaded Lightroom v4 Beta 1 for mac but the installer package failed to launch. (com.apple.installer.pagecontroller error -1.) So I've only watched the adobe tv presentations todate.
Anyway just wanted to give some feedback as a pro photographer about use of Lightroom and improvments I would like to see in the next version.
I am a commercial photographer who needs colour accuracy in photographing fashion/garment images - most of my work is reproduced on a printing press for catalogues and brochures. On average a shoot will yeild about 500 images for a client, so workflow is important as they normally want them all!
As a previous user of Capture One Pro v6 and now lightroom v3.6 - the biggest issue I have with Lightroom is the dominace of red tint when setting the white balance from a gray card reference image, shot at the same time as the images to be processed. I'm not adding anything to the images other than doing a white balance, a tweak on exposure and camera neutral setting on profiles.
To obtain a white balance setting I use the combination of an Xrite white balance card and the Q-Card and the old fasioned Kodak Gray cards all mounted on the same surface. I've used spot and ambient light readings on the gray cards to measure exposure and I've used the Adobe DNG Profiler and the Xrite colour checker profiler with the large colour checker card as a reference, (I've made profiles for sunny days, cloudy days, dual illuminant etc etc) and I'm viewing my images on a colour calibrated apple monitor.
Not withstanding all of the above the best results I get out of Lightroom are using the camera profile neutral setting! Everthing else is just too red!! even though the images do look more punchy; for accuracy of actual colour I choose the camera neutral profile.
Well when I say best results, those for colour critical garment photography and skin tones, these results are similar to those obtained from capture one pro v6.
So for the Lightroom v4 I would like to see.
1. White balance RGB values in numbers rather than percentages.
2. Add and delete a colour readouts points with a dropper tool on an image to enable more acurate colour balancing particularly in shadow areas - (already available on capture one pro and adobe photoshop)
3. Curves adjustments in all RGB channels (think you've done this)
4. Output to CMYK profiles.
5. Individual levels channel adjustment for RGB
6. Ability re-organize my tools palette (add and remove) is per Capture One and Photoshop
Regards

The legacy ACR X.x profiles are no more produced nor included for newer cameras (AFAIK, since ACR 5.1/LR 2.1). The Adobe Standard is the new default starting point for these.
While I am at it....are the Canon camera profiles I downloaded for the 1Ds MKII the same as for the 5D MKII or do I have to download different one...I suspect they are the same or Lightroom wouldn't offer them to me...is that correct?
The profiles are different for each camera model, even if they share the same name in the Calibration panel. If you can see them when developing 5DII files, it means the camera-specific profiles are installed for your particular camera model (otherwise, you wouldn't see them).

White Balance color temperature for custom temperature shots

Hello,
I would like to understand why LR and Photoshop too are always show wrong color temperature "As Shot"?
Let say I shoot with 6000K, set manually (Canon 40D, RAW)
Canon itself says it's 6000K in the slide info, fine.
Both Adobe apps says it's 5750K!
What's going on there?
Second question - I know the light was EXACTLY 6000K, but the slide has some green in it. Picking white balance in LR gives me 5900K (which is close to the truth) and +31 Tint, which makes slide neutral.
Of course I can correct Tint manually before the shot by WB Shift in Camera, so the question is: what is the best way - to find more or less appropriate WB shift in the camera, or use WB correction in LR after all?
Thanks
UPD. My suggestion is - Adobe doesn't read custom temperature from RAW file, it's just guessing! Is that right?

The white balance value you see in Lightroom is profile specific. It reads your custom white balance and translates it so that neutrals stay neutral, which is exactly what you want. If it wouldn't do this, your neutrals would shift in color.
The best way to get a correct white balance is to shoot a white balance (grey) card or use one of those filters on your camera to measure it. You can either set it in camera from the grey card or do it with the dropper in Lightroom and sync over the series. The effect will be the same.
P.S. unless you shoot a white balance card, you do not know that the color temp of your light is exactly 6000K. That is quite impossible to know. It might be approximately that under certain standardized conditions but you cannot be sure, no matter what you're told by the manufacturer.

Can Bridge report in-camera settings for White Balance?

No matter what settings I choose in Bridge Preferences, I cannot get it to tell me what was the White Balance (WB) setting of the camera when raw images were shot.
This seems an odd omission because Camera Raw is passed this information and displays images correctly, although it doesn't report what WB value it was given, only that what you are viewing, prior to any editing, is the default "As Shot".
I'm referring to raw files shot on my Canon 300D, Nikon D700 and Canon 5D Mark II.
Currently I'm using PsCS6 (13.0.1.2 x64), Bridge CS6 (5.0.2.4 x64) and ACR 8.1 on a Windows 7 x64 8GB system, but the same omission existed on the same Windows system with ACR 7.x in CS6 and all releases of PsCS5, Bridge CS5 and ACR 6.6 and 6.7.
On the opening dialog of Bridge Preferences, at the bottom you can choose whether or not you wish to 'Hide Empty Fields'. Selecting or unselecting this option does not have any effect upon Bridge's inability to report WB when, from within Bridge, you select File Info from the File menu or by hitting Ctrl + I.
The only locations in Bridge Preferences I can find that need selection (and which I have selected) for Bridge to supply WB information upon invoking File Info are here:
Preferences\Metadata\Camera Data (Exif)\White Balance; and
Preferences\Metadata\Camera Raw\White Balance
I have also selected Preferences\Metadata\File Properties\Supports XMP, and yet Bridge fails to give the in-camera WB in the Camera Data tab of File Info.
I have been able to locate references to WB in the following tabs of File Info:
File Info\Advanced, where there appears, under the sub-tab 'Exif Properties (http://ns.adobe.com/exif/1.0)', an entry such as 'exif:White Balance:1'; and
File Info\Raw Data an entry such as '<exif:White Balance >1< /exif:White Balance>'.
However, these are just code numbers, not names like 'Cloudy' or 'Shade', and they are not only inconsistent (both showing the code 1 for an unedited image I know was shot with Auto WB and another unedited image I know was shot with Flash WB) but also it would appear that the codes may refer to the WB as modified by ACR - because an image I know had its in-camera WB of Auto altered in ACR shows a code of 'Custom' rather than 0, 1 or some other number.
So what am I missing? Does anyone know how to make Bridge Preferences display the in-camera setting for WB, and if so, under which tab of File Info do you look for the answer once you have set up Preferences properly?
Message was edited by: Andrew_Hart
Just corrected my current Photoshop version

I'm afraid that you just haven't addressed the question that I asked in my original post.
I still like to think I have but if you for whatever reason need this info showing in the metadata you probably be better of trying to alter it your self or find a way to address Paul personally (maybe via a private message).
I have not heard from him for a long time and a small google search provided me with this forum post, hope it helps you, maybe you can also persuaded Paul to come back, he is very missed!
http://www.ps-scripts.com/bb/viewtopic.php?f=2&t=5508

Help with RAW files and custom white balance.

ive long had this issue with RAW shooting and adobe photoshop and lightroom, my main subject is a saltwater reef aquarium that is lit by artificial lighting, i shoot canon and use the custom white balance setting to get everything looking proper and it works good.. to an extent.. if i shoot jpg the photos all turn out as shot, if i shoot RAW the white balance in adobe programs is totally messed up and you cant fix it.. if i use DPP by canon, its perfect and looks just as shot or just a a jpg would look.. my question is how can i get adobe lilightroom to render my RAW files correctly.
below are all 3 images, first one was converted and exported to jpg in canon DPP without any adjustments and is what the photo should look like, second has been exported from photoshop, and 3rd i added a link to the actual RAW file. why cant my lightroom interpret these properly?
heres a link to the actual RAW file
https://www.dropbox.com/s/5a39ctllwgrem7a/_MG_8971.CR2
this was a raw converted in canon dpp, and its what the aquarium looks like, and is what the photo should look like. just to note, any other editing or viewing program besides adobe products all render the image correctly.
this is what photoshop and lightroom do to my Raw files, theres no way to adjust anything to get even remotely close to correct..

The white-balance Temperature of this image as computed by the camera is way beyond the 50,000K upper limit as you can see when you open the file in LR or ACR, so Adobe cannot reach the As Shot WB temperature number and stops at 50,000K which is still too blue -- although EXIFtool says: Color Temp As Shot : 10900, so maybe Adobe's wildly high 50,000K number is based on a faulty camera profile that exaggerates blues:
However, using the Camera Standard makes things not nearly so garish blue, and it is possible to use Photoshop to neutralize things even more:
However, as you say, other raw converters do ok with this image despite the high WB temperature, so I think the Canon T3/1100D profile needs some work, but probably won't get it since it is not a high-end camera.
For example, here is the default conversion from LibRaw that is part of RawDigger, and in my opinion is an improvement on the camera rendering though perhaps lacks a bit of saturation:
As another example, here is RawTherapee's conversion, after I neutralized the auto-tone and color values it applies by default, and appears to be a bit too saturated but that could be easily adjusted:
I would agree that Adobe is doing something wrong with this camera in this lighting. A clue is the bright green color of the top-central coral which seems to be yellow in the non-Adobe renderings.

How can I turn off Automatic White Balance/Correction?

Hi,
I shoot color Infra-Red images. White Balance is handled in Camera - and then in Photoshop. As a new user to Lightroom 2 - everytime I view/click on an image in the Library - the color/balance of the image changes to a deep red, and I lose all of the vivid colors that I had from the original image. The files are Nikon NEF RAW - and I am looking for a way to turn this automatic change in colors off. Can anyone help?
Thanks and have a great weekend !!!
Dave

Hal,
I have a Nikon D-70 that has the Lifepixel infra-red conversion. Take a look at their website and you can see the great color infra-red pictures that you can take with this converted camera. So there is my problem - I can set the camera at a PRE White-Balance and shoot Cyan/Blue/Green photos - and then import them into Lightroom. I see the photos in the Library - but as I click on them to view them, they change color to Red. Now if I set up the camera to take White Balance as Auto - or pretty much anything else other than the PRE (for which I can adjust), I will also get a Red photo. Red is OK if you want to convert to B+W - but if you want to retain all of the colors, I need to keep the color that the camera shot - without Lightroom changing them. I looked at the history - and only have an import/date. Other than clicking on it to view - no changes have been applied by me - yet. I will try to shoot them as jpg's - the ones I am working with right now were shot in the summer. We have -20 Deg. C. here right now - so Infra Red camera is in bag - have no green leaves to shoot. Looking through preferences and settings to see if I can find a "turn-off"....... Actually - let me load the photos with Bridge and see what they look like there..........
Dave

Open the same raw file in PS5 with two different White Balance settings

I'm trying to open the same Raw File in PS5 with two different White Balance settings. One setting "as shot" the other in "daylight", then blend them. The tutorial I'm watching says to "stack" the images. The tutorial shows one White Balance setting as the "Background" layer and the other setting as "Layer 1". I don't know how to do this and the tutorial is not specific. Can anyone either point me to a step by step instruction or offer some assistance?

Also look at the "Snapshots" feature of Camera Raw itself. It allows you non-destructively to keep multiple sets of settings for a single raw file.
Learning about it far exceeds the scope of what can be done in this particular forum. I would recommend this book as essential reading:
http://www.amazon.com/Real-World-Camera-Adobe-Photoshop/dp/0321713095/ref=sr_1_1?ie=UTF8&q id=1313502199&sr=8-1
Additionally, there's a dedicated Adobe Camera Raw forum:
http://forums.adobe.com/community/cameraraw
Wo Tai Lao Le
我太老了

White balance in photoshop cc

Similar Messages

Maybe you are looking for