New to RAW, White balance question

I've been using Lightroom for years, but with my camera outputting JPG images only. I've now started working with RAW (NEF) files from my D90 recently, and am having newbie's difficulties.
LR 2.6, Mac OSX 10.5.8, iMac 24" 2.8GHz
The problem that brings me here is that I just did a shoot without setting a white balance. Shot JPG & NEF, and I see that Lightroom is extrapolating the AWB values the camera came up with onto the NEF files "As Shot". For a series of similar images I have found a white balance that seems to work. I set that on my chosen image, shift-select the rest, and attempt to SYNC white balance to the other images.
It doesn't take. WB's remain "As Shot" for the other images, and all over the place, following the camera. Expanding the items synced to include "Treatment (Color)" doesn't help.
How can I "Sync" white balance with NEF files, please?
Many thanks in advance.

So Lightroom is essentially applying an "Auto WB" on its own when displaying images "As Shot"?
ON EDIT: I ask this because every image has a different, individual "As Shot" WB when first seen in Lightroom.
Hardly seems "As Shot" if LR is going in and altering the WB right off the bat.
MethodPhoto wrote:
The white balance information that Nikon knows about is not information that Lightroom uses.
Camera Raw and Lightroom use Adobe's method of profiling the camera which is different from Nikon's. So you won't get an exact match, however Adobe provide a set of profiles which are intended to match as closely as possible the Camera looks - these are in Develop > Camera Calibration
If you find there are a certain set of adjustments that you repeatedly make then save them as a Preset and you can apply them to a batch of images or on import. (These can include White Balance settings and Calibrations and Profiles).

Similar Messages

  • Tethered and White Balance question

    I am using the latest Aperture and also the latest Aperture Hot Folder to shoot tethered using my Canon5d to my powerbook g4 1.67ghz. The issue is shooting images with the same white balance applied as I shoot. Is there an obvious way to do this that I am missing? Or does anyone have an idea how to do this using Applescript? My main app to shoot is CaptureOne and white balance is quite easy to do using this app. I am trying to integrate Aperture into my shooting workflow not just my post workflow. Any ideas would be appreciated.
    - Rudy

    i don't know what your canon is like, but the D200 also has the ability to 'read' a white balance setting (probably from the same sort of calibration card that you're talking about... i've never tried one, but often want one). this calibrates the in-camera white balance setting based on the light you're shooting with. this again would hopefully get you close to correct without software post production (this is a theme for me: shoot correctly and then spend less time correcting).
    and you've still got the ability to tweak if its not perfect and then lift/stamp those tweaks everywhere else. i like the fact that CapOne had thought of that for tethered shooting, but i also don't like to stretch and pull my image data any further away from the raw data than necessary.
    keep us posted on how you finalize the workflow
    scott
    PowerMac G5 2.5GHz   Mac OS X (10.4.8)   MacBook Pro 2.0GHz

  • Camera Raw white balance presets

    When I open an image (either RAW or JPEG), I only have 3 option for white balance presets. "As Shot" "Auto" or "Custom". Does anyone know how I can get the other presets?? I am using CS3 w/ Camera Raw 4.2. I have reset my Camera Raw defaults with no luck.
    Thank you for your help.

    Brent: Are you absolutely, 100%, sure you are opening a raw file?
    JPEG and TIFFs so not have these extra presets because they don't make sense since the starting point for a JPEG/TIFF is unknown.

  • White Balance Questions

    Is there a way that I can shoot a pic of a gray card at the beginning of a photo session and then magically apply that neutral gray to an entire project automatically? Or, do I have to go through and adjust the white balance on each and every picture in the project? If the answer is the latter, how do I pull the neutral gray from the pic of the card and apply it to the real pictures in my project, on a pic-by-pic basis? I've been playing with this and I just can't figure it out intuitively, nor do I find it addressed in the aperture manual.
    One more question ... If I don't take a pic of a gray card and instead use the eye dropper tool to find a neutral gray within the picture, what numeric levels am I aiming to find for the four different colors that appear? For the life of me, I don't know why that simply question is not addressed in the manual!
    I appreciate any insight you can give.

    I use a gray scale instead of a gray card, and I click white instead of middle gray. However, I just tested on middle gray, and the difference is less that 70 degrees Kelvin.
    So, if you use the eyedropper in the white balance brick, you can then use Lift and Stamp to apply it to the rest of the images in your project.
    See Applying Adjustments to a Group of Images page 438 of the user manual.
    DLS
    PS welcome to the forum
    Message was edited by: MacDLS

  • Lightroom Changes RAW White Balance Upon Import?

    Hi All,
    I'm new to Lightroom so bear with me. My problem lies in the import process: each time I import, a yellow tint (tungsten WB) is added to each photo, as if the white balance is being changed. I know that thumbnails are created in camera, but the photos look fine when Lightroom is "loading" them on the library screen, it is only when the "loading" message goes away that they look too yellow. I don't want to apply an import preset because I fear that each photo's problem is unique. When I use quicklook in finder, the images look fine. When I export as a jpeg from LR, the problem persists. Here's what I'm using:
    Camera: Canon T2i (Color Space: sRGB)
    Lightroom: Version 4.0
    Computer: Macbook Pro, Snow Leopard
    I've read that this could be caused by a corrupt color profile, but I'm not sure how to change this on a Mac and if it's appropriate to apply sRGB as a monitor profile.
    Any help is appreciated!!

    The initial preview is the camera generated JPEG (should match the LCD). Then LR builds it’s own high quality previews based on it’s engine. Hence the difference. Ignore the original OR if you really like it, try making a preset for importing the images that honor that rendering. Bottom line, the initial previews are not any reality to what LR is going to initially produce based on all those sliders.

  • Changing RAW White Balance

    I just bought a Canon S95 and am playing around with shooting in RAW.
    I know when you shoot that the camera writes the selected white balance mode or white balance setting into the file, and then iPhoto sees that when it is imported. What I am wondering is if there is any way to change that setting to another preset. For example in Canon's Digital Photo Professional software you can select any White Balance preset or use the one the camera wrote to the .cr2 file. Can you do that in iPhoto, or can you just adjust it using the Temperature and Tint sliders in the edit pane? Thanks.

    You just change the slide for temperature.
    I tested it not that long ago taking a few photos with different in camera WB settings because I wanted to see if iPhoto actually imports them and adjusts the slider to that position or if the slider is always in the middle regardless of the WB setting. I confirmed that when imported, the slider will be set/moved to whatever the RAW file says the camera was set for or will set it to the extreme if your camera goes further (e.g. if you camera can be set for 14k, then the slider will max out at 10k in iPhoto.
    You might try taking a photo with each of the standard presets on your camera then simply note what setting on the slider it is when imported to iPhoto for future reference.
    Cheers,
    Patrick

  • White Balance question

    I have taken a few zillion pictures of various minor hockey games. I have not been wise enough to use a WB card, so most of the pictures are various shades of yellow due to bad lighting in the arena. EVERY picture however requires me to use the dropper to find a gray target and set the white balance that way. No big deal. But do I really have to do it for every picture? Why wouldn't the TEMP and TINT be the same for a whole game?
    Paul

    Because the arenas are usually lit by high-bay lights, possibly a mixture of metal-halide and sodium. Each light has a different color, and they flicker at 120Hz. If you are shooting at shutter speeds faster than about 1/30th, you are catching pieces of cycles from individual lamps meaning the color and lighting are always changing.
    The solution to this is lighting the arena yourself with big strobes. Sadly, getting them to install electronically-ballasted lamps into the arenas is not going to be so easy.

  • Basic white balance questions

    1.) What do you do if you are working on an image that has absolutely no white in it or neutral colors? Maybe the white detail is all washed out, maybe the image is made up of blues, reds and yellows. How do you use the white balance tool in this case?
    2.) If you have the option of choosing both a white color or grey color to use the white balance tool on, is there a general rule of thumb for using one over the other? Or do you just try both to see which looks better? Does clicking on white result in a better white balanced image generallly than when clicking on grey?
    Thanks.

    Jeff Schewe wrote:
    Most of the time I don't bother with the White Balance tool and simply adjust the image to taste. But if you do need an "accurate" WB, then it's better to use a non-specular non-blownout white. Grey is too far down the tone scale and can be a bit less accurate.
    A non-specular non-blownout white would be best. Unfortunately, such a target is not readily available. The "white" patch of the Colorchecker has a reflectance of about 90% (optical density = 0.05) and is not spectrally neutral, so it is recommended to use the second brightest patch for white balancing with the color checker. It is apparently difficult to make a spectrally neutral white paint. The second brightest patch has an OD of 0.23 (~60% reflectance) and is reasonable spectrally neutral. The darker neutral patches will result in a higher signal:noise in the image, but can work relatively well if your sensor has good noise characteristics, and a darker gray neutral area of an image can be used if a lighter neutral area is not available.
    Babel Color used to provide a spectrally neutral white target, but it is no longer being offered. Their web-site FAQ gives useful information on the section on the of a white balancing target. Besides not being spectrally neutral in many cases, the Kodak 18% target is too dark, but can give acceptable results as many photographers have found. The WhiBal target has a reflectance of 50% (OD = 0.32, L* = 75) and is a reasonable choice for white balancing.
    http://www.babelcolor.com/main_level/faq.htm#FAQ-white_balance_target

  • Apeture/White Balance question

    When I want to use the dropper in the White Balance adjustment, I'm supposed to choose neutral gray. What do you choose if there is no neutral gray in the shot? What numerical values should I be targeting that appear in the Loupe? Thanks.
    Jerry

    Any color where the amount of 'red', 'green', and 'blue' are all equal will work -- including "white".
    But you're not searching for color values where the R, G, & B values are equal... rather you're searching for colors you know are supposed to be equal -- yet are not. The white-balance will then adjust them based on how out-of-balance your selected color is to correct the color to be in-balance (and everything else in the image will be adjusted relative to that selected point.)
    This just gets you a starting point -- you might need (or want) to tweak it off that starting point just a little. e.g. At a wedding with candles the images probably should appear just a touch to the warmer side -- a true & "perfect" balance that fails to represent that candles would have put a slight warm cast on the room would make the pictures appear "cold".
    At the very least, make sure the color adjustment appears consistent from image to image.

  • Canon 1dsM3 sRAW / RAW white balance differences.

    I am glad that Lightroom 2 is one of the few photo manipulation products that supports the Canon 1ds mark III sRaw format. Curiously when an identical photo taken in RAW and again in sRaw, Lightroom displays them strikingly differently.
    The 1dsm3 has the ability to take one photo, and write a RAW file to one memory card, and an sRaw image to a second card. An example image taken in this way can be found here:
    http://www.melaque.com/photos/test-images/jjw12363-sraw.CR2
    http://www.melaque.com/photos/test-images/jjw12363.CR2
    As both of these images were taken at the same time (only one exposure), one would think that they would display rather similarly in Lightroom 2. However in reality, one shows up quite warmer than the other.
    When displayed with Canon's DPP the photos look identical, that is one is not warmer in tone than the other. Apple's Aperture product displays....well, nothing, as they do not support sRAW.
    I would imagine that it would be a small matter to adjust the raw engine to correct this problem.

    Accessing the files return Not Found:
    Not Found
    http://www.melaque.com/photos/test-images/jjw12363-sraw.CR2
    The requested URL was not found on this server.

  • 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

  • Lens Profile Tool Addition – White Balance Offset Correction

    I have noticed that my Canon 17-40mm and 70-200mm F4 IS lenses have virtually identical color temperature and can use the same white balance setting. My Sigma 50mm F2.8 Macro lens is another story, requiring almost 200K and +15 change to White Balance sliders. I am sure there are cases where Canon’s lenses will differ more widely and exhibit a similar degree of white balance differences, not to mention use of UV or 1B protection filters. An 85mm F1.2 lens using “rare earth” low dispersion glass, will have a warmer color temperature than a lens using more common glass elements.
    I use the X-Rite ColorChecker Passport to create custom profiles for each of my camera bodies. I typically make separate correction presets for Daylight, Cloudy, and Tungsten (2700K). This requires changing the LR White Balance sliders to obtain “neutral gray in the ColorChecker image files shot in each of above described lighting conditions. It does not appear necessary to create a separate ColorChecker camera profile for each lens, just correction to the LR white balance slider settings.
    I did some measurements of change in camera profile for Sunny Daylight (~5,500K), Cloudy (8,000K+), and Tungsten (~2,900K) lighting. There was no measurable change in rendering of the ColorChecker Passport images for the extreme Sunny to Cloudy conditions, and only very slight changewhen comparing the Tungsten profile. This was done by loading a ColorChecker Passport image file and applying alternate profiles:
    EXAMPLE:
    Open a DaylightColorChecker Passport image file in LR, apply Cloudy Camera Profile, and adjust White Balance for the gray scale patches using the Eyedropper Tool. Then look at the 'Before' and 'After' images....you will see NO visual change to any of the color patches. I saw only a very slight change when doing this with the Daylight to Tungsten (artificial light source) comparison.
    The relatively small change in color balance between lenses (~500K max.) should have no measurable or visible affect to the ColorChecker Passport created "Camera Profile." The ColorChecker Passport or any other "Camera Profile" creation tool is first and foremost correcting for differences in the camera's image sensor color rendering.
    SUGGESTION:
    Since this white balance difference is a factor of the lens, it would be very convenient to add another tool in Lightroom's and Camera Raw Lens Profile panel for “White Balance Offset.” This allows setup of LR defaults for one specific lens type, such as your most used lens. Then you use the new ‘Lens Profile’ located ‘White Balance Offset’ correction tool to adjust white balance for all of your other lenses. In addition, Adobe or camera manufacturers could also provide the 'White Balance Offset Correction' as a function of the lens spectral response deviation from linear. This would provide a "uniform method" of calculating and adding the White Balance correction to the 'Lens Profile.' Since this is a factor of the lens only, the “lens offset correction” can be used with ANY lens/camera body pairing, The current LR and Camera Raw White Balance settings are then only used for “Global” correction of lighting conditions, and NOT for lens differences.
    This is a linear mathematical function,which should be extremely easy for Adobe to add the ‘White Balance Offset’ correction feature to LR’s and Camera Raw's Lens Profile GUI. Just like many other tools in LR that some don't use, you can choose to use it or not!

    Interesting suggestion. Thanks. -Simon

  • White balance in kelvins

    Can anyone please explain the difference between adobe camera raw white balance settings (temperature and tint) and white balance in the camera which is measured in kelvins.
    let's say i like 5350 for temperature, and  -8 for tint white balance settings. how much would that be in kelvins on my camera?
    thank you

    Temperature = degrees Kelvin. That's the blue/yellow axis that refers to black body radiation as it heats up ( http://en.wikipedia.org/wiki/Black-body_radiation ).
    Tint is just the other axis at 90 degrees to that. The tint axis is green/magenta.
    You adjust (fine-tune) along the same two axes in the D800, by moving the point vertically or horizontally. But camera and ACR won't necessarily agree as they interpret things a little differently. In any case: If you shoot raw, there's no need to make fine adjustments to this in camera. Do it in ACR. The camera white balance setting does not affect the sensor data or the file itself. ACR just reads the camera setting to get a rough starting point.

  • Raw Update 2.3 + Nikon D90 = Wrong White Balance Temperature

    Hi folks. Wonder if someone has had a similar issue and/or has any insights.
    Here's the background:
    - Aperture 2.1.2 on OS 10.4.11
    - Downloaded/installed Raw Update 2.3
    - Imported ~800 NEFs from a D90
    - On ~15-20 NEFs, pictures show up blue (white balance at ~2500)
    - The affected NEFs are semi-randomly distributed among the ~800
    Here's why it's weird:
    - NEF displays correctly in Nikon View (the thumbnail and full picture)
    - NEF displays correctly in the Finder (the thumbnail)
    - NEF displays correctly in the preview and thumbnail *in Aperture* but only until the preview and thumbnail processing completes at which point they turn blue (this is why it's especially weird)
    - Peeking into the Aperture package, the NEF thumbnail shows up correctly but the preview and thumbnail files show up blue.
    If I delete the NEFs from Aperture, close down, and repeat I get the exact same problem on the exact same NEFs. This leads me to believe that there's something specific to the NEFs but it must also be linked to Aperture and more specifically, it's thumbnail/preview process since they show up fine in Nikon View, the finder and Aperture before the thumbnail/preview processing takes place.
    Obviously I can't downgrade to Raw Converter 2.1 or 2.2 since my files are from a D90, and I shoot in raw (not raw + jpeg) only so have been limping along with Nikon's software.
    Any ideas out there?
    Thanks!
    Message was edited by: rbhansen57

    Hi,
    I simply can't see the NEFs.
    OS X 10.5.5
    Aperture 2.1.2
    Nikon D90
    Import runs fine, and the thumbs are there, but when opening a NEF a big thumb (7x4.5cm on the 24" screen) is displayed in the middle for a second, and then it turns into a dark red message "Unsupported Image Format".
    It's general - no NEFs work for me.
    I import directly into Aperture - do you import via the Nikon Software?
    Previously I had an Olympus E400 - the RAWs worked fine in Aperture (directly imported).
    My strange observations are:
    With the Olympus E400 (10MB) the size of the JPG files were 6-7MB and the RAW files (called .ORF) were 21MB.
    With the Nikon D90 (12.3MB) the size of the JPGs are around 6.5MB (4288x2848 pixels), but the size of the NEFs are just around 11MB (I did expect over 21MB) and the pixels are 256x170 (although the picture says 4288x2848 on the camera itself).
    I'm new to this support site - do Apple supporters take time to read our questions and join these discussions?

  • White Balance Tint Limit When Processing Raw Files

    Hi guys, following some recent suggestions I've got hold of some Welding glass to use as an ND filter on my Fuji HS20. It arrived today and works a treat.
    I do however now have a new issue that this has caused.  I've set a custom white balance on the camera to counter act the tint from the glass. This now produces the correct colour on my jpg photo's however the RAW files have the wrong colour tint.
    When I open them in photoshop elements 11 I get the CAMERA RAW application. The white balance is set to 'AS SHOT' however the Tint is at +150. I'm guessing my problem is that the tint needs to be more than +150 and CAMERA RAW is limiting it.
    Does this mean I am now limited to using JPG's when I use this glass as an ND filter, or is there a way I can get rid of this limit to the tint on the white balance

    filippodallosso wrote:
    I have exactly the same problem. The reply is to your question is not what you were asking, isnt it?
    The point is that we CAN NOT adjust the white balance as suggested, because the sliders are already at their maximum value when we open the photo in camera raw. We'd need to further increase the tint value (as the photo looks green) but it is by default at 150, so we cannot increase it further.
    One way to overcome the limitation of the tint/temp sliders is to save an intermediate tiff or psd file. You can open it in ACR and apply the same maximal slider correction.
    For the same purpose, instead of saving an intermediate file, I opened the raw file in the editor. From there, I used the Editinacr script in Elements+ to reopen the layer in ACR (shift f3 and script selection). Same corrections and back as a new layer in the editor. I could repeat the process several times to get a very powerful correction without intermediate files.

Maybe you are looking for