Lightroom & Nikon D800e White Balance

I've set my white balance in the camera (D800e) to afixed temperature; 5500K.
When I bring the .NEF file into Lightroom 4.1, the "As Shot" white balance is called out as 5300K, with a +6 Tint.
I get this same reading with any of the six camera profiles listed in the LR Camera Callibration frame.
If LR is reading the metadata in the .NEF file, the numbers ought to match.
Why don't they?

So on import you want all your photos so have a 5500K 0 WB in LR like you did with your old camera?  Then all you have to do is set LR to have that as it’s default WB, or create a Develop preset with WB 5500K0 and use that as your import preset.  The only reason it matters what your camera is set to is that you are using the LR factory default of As Shot so LR interprets the camera’s gray-point values into a WB.  The only thing that is affected by your camera’s setting is the WB of the embedded JPG preview that the camera shows as you review your photos, or that you see when you import photos before LR re-renders things. 
If seeing this spectrum of colors on your camera’s display and on the Import grid is important, then so you need your camera’s custom WB to show up in LR as 5500K +0 then take a sequence of shots where you vary the WB slightly  in your camera maybe by 50K on each one, and keeping track of what you set it to for each one, and find the one that LR interprets most closely as 5500K +0.
I used to do what I think you’re saying you do, have my camera set to the same custom WB for everything and have the tungsten shots look very orange and my twilight shots look very blue and other outdoor shots vary between orange and blue, and then adjust my WB in LR to how I wanted it.  Since I always was needing to adjust my WB in LR, I decided to get a little help from my camera, and now I have it set to AWB so I have the added benefit of the camera’s intelligence in guessing what looks good.  I still synchronize my various photos in a particular lighting scenario to the same WB after deciding what looks best, but sometimes I find the camera does a better job of guessing than I did and I sync to a custom-WB that is equivalent to what it picked for its AWB of one of the shots instead of always having to play with the WB to figure out what I want.  Having my camera set to AWB doesn’t preclude me from having the same WB for all my photos in LR and seeing which ones are warmer or cooler than others, but not having my camera set to AWB removes the camera’s intelligence as a suggested WB.

Similar Messages

  • Nikon D700 White balance importing issues

    Hi Guys,
    I am using a nikon d700 with Lightroom 3.2 If I shoot tethered, the correct white balance appears and gets loaded in Lightroom, but if I import them after the shoot, from the card, it loads a completely different white balance value and I have to go back and correct them one by one. I am not using any profile, just leave it on the standard Adobe version because the Nikon profiles are significantly reducing the quality on raw file. Does someone have an idea what I am doing wrong to be able to load the correct white balance during importing?
    Thanks

    Are you shooting RAW? If so there is no WB embedded in a RAW file, you set the WB in LR. Setting "As Shot" and a calibration profile that matches the camera setting (if one exists) will usually closest to the wb embedded in a jpg produced by the camera processing.
    You may want to check out the FAQ, this one is pertinent.

  • Lightroom D100 custom white balance not read

    I have a D100 converted to IR use. I shoot with a custom white balance set off green grass. If I open an image in Raw Shooter or Capture I get the balance I expect. In Lightroom it opens as what looks like an unbalanced "pink" IR shot. Manually adjusting the white balance in LR I can't get my normal results - may be related to the fact that the red channel looks completely clipped at the high end which I don't see in RSP.
    The D100 is meant to be supported for reading white balances.
    Any suggestions ?
    Andrew
    ps: I thought I posted this a few days ago but after a couple of days with no response couldn't find it myself so if it is lurking somewhere, apologies !

    Suggestion for a workaround:
    It seems that you want to work with a specific WB value you know.
    Just create a preset with a fixed WB value which you apply by importing your IR shots. Then you don't even have to set it in the camera.
    Besides this with my D70 I get the WB valance values from the camera without probs. I have however no experience with the D100
    regards
    Chris

  • Lightroom 2 - Auto white balance - crash

    I'm having intermittent problems while applying auto white balance on some CR2 files in Lightroom 2 running on OS X 10.5.4. When choosing Auto from the list of white balance options, LR waits for a second or two, doesn't update the history panel and the spinning beachball appears. CPU rises to about 100% and there's no other way than to force quit.
    So far it happens with, say, one in 50 images (I've been working on approximately 100 images and with 2 this happened).
    When I restart I can easily recreate the problem by going through the same routine.
    The workaround is working on another image and then going back to the problematic one; then I can apply AWB without any problems.
    I can save a (lengthy) hang reporter log file.

    Thought I was doing pretty good with LR2, but unfortunately this problem has showed up on my Mac OS X 10.5.4 system. The stalls (i.e., beachball) are when developing CR2 images from a Canon 5D. I experience many occurrences of the problem when going through this folder of RAWs, perhaps 20-30% of the images. Today I thought I had found one that always fails, but turns out not to be the case, although it causes a failure over half the time it is accessed. Same symptoms as described in the above posts: Convert an image's white balance to auto, in either quick-develop or develop. Then when you access the image you get the spinning beachball forever, and have to force-quit. I've also stalled LR with this sequence: in QD, convert WB to auto, switch to develop module, undo the WB change in history by clicking the prior step... LR stalls. Basically I've seen all the same steps as described here, and more.
    Also, just for fun I tried everyone's favorite troubleshooting step, i.e., trashing preferences. It made absolutely no difference. The first time I simply clicked on the troublesome image, LR got stuck.
    Jao... interestingly, I never saw this problem in the beta in spite of developing many, many images in the beta. If it was known and not fixed, that's quite a concern.

  • Lightroom 4 and white balance tool

    In Lightroom 4 i use the whtie balance tool and find point that give as high as 99% reading and it would work to set it as the reference point. Today i did the same thing and got a message that said Lightroom could not obtain white balance from that spot and to try again. i've never seen this before. even if i used  a spot that was 100% reflective. It would just render colors off.
    Today i did the same thing and a message came on the screen that Lightroom couldn't obtain white balance from that spot and i should try again. i was only able to obtain white balance if i used a spot that reflected no more than approx. 90%.
    what has changed?
    thank you

    The White Balance Picker sample area  in LR4  can now be adjusted using the 'Scale' slider, so yes it has changed from LR3:
    http://feedback.photoshop.com/photoshop_family/topics/white_balance_eyedropper_tool_option
    The readings you see in the LR Histogram in no way reflect the actual raw data values. The White Balance picker needs a sample area that has no raw data clipping in any channel (i.e.All four R,G, B, G2 channels 99% or less). I suspect the 99% area you are sampling has raw data clipping in one or more channels. If interested you can download RawDigger to examine the image file to confirm:
    http://www.rawdigger.com/
    I suggest choosing a sample area that is well below 99%, such as 85% to 95%.

  • 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.

  • Nikon NEF White Balance encryption

    Hi,
    I've read quite a bit about the encryption of white balance information in NEF files. I'm in the market for a D50 but this seems to be a problem for me. I'v shot with a 350D and the CR2 files are fine. I got my hands on a D200 and I can only open them with Lighroom.
    Any D50 users out there using iPhoto? Does iPhoto decrypt the WB information or do you need to send the NEFs through Nikons software before imporing?
    I'd hate to get an overpriced Canaon simply because of an encryption problem...
    Thanks!
    Matt

    Hi Matt,
    I use the Nikon D70 and I just shot a bunch of
    pictures using Raw format (NEF). Yes, indeed the
    white balance in the adjustment panel started off in
    non-zero value.
    You're talking about iphoto here, right? If iphoto can open the files, so could preview, for example.
    I guess your analogy is correct that
    iPhoto is able to read the picture information from
    NEF. In fact, I think the quality of the adjusted NEF
    picture is much better than if you adjust a similar
    image shot in JPG. I'll go home and test this tonight.
    Yeah, I bet they are! That's a main reason I want a dslr. Sure there are some point and shooters that do some kind of RAW, but if I go 'advanced amateur' I'm gonna go all the way!
    btw, what's the rest of your photo-gear?
    Thanks for writing!
    Matt

  • Aperture - Nikon D2X White Balance

    Apologies for posting in this forum but couldn't find one dedicated to Aperture yet.
    Does anyone know if Aperture will actually decode the encrypted white balance information in Nikon NEF files from my D2X or will it make a 'best guess' for the balance based on the image contents ?
    aTdHvAaNnKcSe
    [email protected]

    It is my understanding that Nikon will continue to keep their NEF WB data proprietary. It will probably take a hacker (not Apple) to take care of this problem.

  • Nikon D800 Flash White Balance

    When RAW files (either NEF or DNG) taken with the setting Flash White Balance, they are imported into either Lightroom(4) or Photoshop(CS6) with a temperature of 6150K.  This does not coincide with the Nikon default of 5400K.  If the Nikon Software (View NX2) is used, the white balance shows that the Flash setting was used and the image appears identical when their 5400 default is applied.  In Lightroom, or in CS6, if the temperature number is changed to reflect the Nikon default number of 5400K, the color of the image dramatically changes.  If the temperature is left at 6150K, the image appears virtually identical to what Nikon calls 5400K. 
    The issue, a minor one, seems to be that the Adobe products are applying an incorrect Kelving Temperature number to the files.  It is disconcerting to see the wrong temperature displayed in the software, but the number can be ignored without any negative effects; and the number can be modified to produce a more pleasing balance.
    I am writing only because it took some experimentation and time to come to these conclusions.  I wasn't clear, at first whether the camera was at fault, or if the software was producing the issue.  It would be beneficial to have the issue addressed and corrected.
    Incidentally, all the other White Balance settings from the camera seem to translate accurately into the Adobe Software.

    Nikon's white balance numbers are confusing.  Nikon list Direct Sunlight as 5200 degrees and Flash as 5400 degrees - no values are listed for tint.  If you open an NEF file with Nikon Capture NX2 and select Direct Sunlight for the white balance it will list 5200 degrees with tint of 0 for the white balance, and if you select Flash it will list 5400 degrees and a tint of 0.  You can adjust these values with sliders, and if you adjust the Flash values to 5200 degrees with a tint of 0 you do not get the same colors in the image as you get with Direct Sunlight selected which has the identical temperature and tint values. 
    I don't find any agreement between Nikon's white balance values and what you get with Adobe RAW processing software.  I don't find the presets in Adobe Software (Daylight, Flash, etc) very useful because they don't appear correct for the camera's I have.  I shot images (NEF Files) with every preset available in the camera selected and saved the white balance values as presets in Adobe Camera RAW.  I also find the Camera profiles more useful than Adobe Standard. 

  • Is there anyway of overriding the d700 white balance fine tuning when importing to lightroom?

    I have imported a large number of my raw photos from my d700 into lightroom.  The white balance fine tuning setting was b4 creating a blue bias which I would like to remove.  When I copy directly from the camera to my iPad there is no bias and the photos look good however once I import into either lightroom or photoshop I must adjust each photo to remove the bias.  There must be a better way.

    My suggestion would be for you to adjust the white balance to your satisfaction along with any other adjustments that you think are consistently out of line with what you want. Then, create new defaults for that camera.

  • White Balance Tool Help

    Can someone please tell me how to set Lightroom so the White Balance tool stays active until I deselect it.

    Thanks Lee Jay, don't use it much myself. Even so, you can move the image around in Loupe with Pgup and Pgdn. It will sequence right throughtout he whole image from one point right back to the starting point while WB is active.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core, Pentax *ist D
    http://donricklin.blogspot.com/

  • White Balance jpg Importing Issue

    In Lightroom 1.2 I'm having a white balance issue after importing jpg's from my hard drive into LR. I noticed the issue after I did my jpg selection in Windows XP using the MS Picture Viewer to delete bad jpg's before I import the good jpg's into Lightroom. The white balance was way of balance using the LR "As Shot" WB as compared to MS Picture Viewer and Paint Shop Pro 9. A custom WB of -31 in LR equals the WB of jpg as viewed in the Picture Viewer and Paint Shop Pro 9. All 289 jpgs were affected. I also re-imported the jpg's into other new catalogs with the same results.
    I do not have any presets selected for importing. I don't think I made any setting changes, I checked the settings and did not see anything out of the ordinary. I also did a "repair" re-install of Lightroom just in case a module got corrupted. The jpg's were from a Canon 20D. In the past week I was doing a lot of RAW prior to this importing the jpg's. The jpg's were imported into a brand new catalog and the PC was booted up prior to the importing. I never had this problem before with jpg's. Lately I have been getting catalog errors, settings that reset themselves, crops that uncrop themselves and photos that won't remove after I remove them while doing development of Raw photos. I have Lightroom installed on my local "C" Drive and the LR Catalogs are on my local "E" Drive.
    thanks
    Vince

    >Is MS Picture Viewer a colour managed application? I don't know, but don't think so. Lightroom is however which might be the cause of your problems.
    Not in XP. In vista it is color managed. From the sound of it, the problem is a bad monitor profile but you might also have a corrupt Lightroom database. You need to recalibrate the monitor and NEVER use canned profiles from the monitor manufacturer. They are almost always corrupt. As a very last resort, you can use sRGB as the monitor profile (delete any profile found in the windows display properties) but only to hold you over until you can really calibrate it. The other problems with weird errors are pretty worrisome though. Do you also get them when you start a fresh catalog?

  • Bug report: Wrong As Shot White Balance for Nikon D50 NEF in Camera Raw 7, Lightroom 4

    For Nikon D50 cameras Adobe Creative Suite 6 does not read "As Shot" white balance data whether it's specified or not. It defaults to "Automatic". We have the problem only for Nikon D50 and only in Photoshop CS6, Adobe Camera Raw 7.3 and Photoshop Lightroom 4. (Not in CS5. Not for Nikon D5100 or D7000 or Canon S95) .
    There is a more detailed posting at photoshop.com.
    Lightroom 4.2 / ACR 7.2: WB "as shot" does not read the WB of Nikon D50 NEF, defaults to "automatic"
    http://phtshp.us/10utPuk
    phtshp.us/10utPuk

    Moving the discussion to PS Forums

  • Lightroom: Why does auto white balance no longer work after changing the camera calibration profile?

    I'm using NEF raw files from Nikon.
    Lets say for example I import a NEF file into Lightroom (v4) and click on 'auto' for white balance. The white balance in the image is  adjusted correctly (somewhat). However, if I then change the camera profile (in the camera calibration section) from 'adobe standard' to 'camera standard' then the white balance in the image becomes very wrong. I then have to set the white balance back to 'as shot' and correct it manually instead.
    Why would 'auto white balance' no longer work just because I change the profile from 'adobe standard' to 'camera standard'?
    Any ideas?

    Works as expected here...
    Which Lr version and what OS??

  • Does Lightroom read white balance settings in NEF files?

    I have noticed an interesting difference in white balance color temp using Lightroom vs. Capture NX: In a Nikon D70 RAW shot (with camera white balance set at Direct Sunlight, no fine-tuning) Lightroom shows the "as shot" color temp to be 4850K. Capture NX reads the as shot color temp to be 5200. If Lightroom is reading the NEF w.b. settings, why isn't it reading the K temp as 5200?

    Fred Felder:
    I still have not been able to find the original post (the links I tried to follow appear to be broken) by Thomas Knoll but I found another message which contains the relevant quote:
    Ramón G Castañeda, "D200 White Balance Issue" #13, 30 Aug 2006 3:52 am
    which says...
    >Thomas Knoll - 10:47am Sep 25, 05 PST (#1 of 101) Edited: 25-Sep-2005 at 12:57pm
    >This is the normal and expected result of Adobe Camera Raw and Nikon using different camera profiles and algorithms, and is not a bug.
    >Because of the different camera profiles being used, when matching white balance values Camera Raw can either match the white balance appearance (which colors are exactly neutral) or the white balance numbers (exact Kelvin/Tint numbers). In these cases, Camera Raw chose to match the appearance, not the numbers.
    >Even if the white balance matches, I don't expect an exact overall appearance match since Camera Raw and Nikon software use a different tone curve and rendering algorithms for non-neutral colors.

Maybe you are looking for

  • New to Lifecycle, Error while generating PDF using Output service

    Hi All, I am using LC 8.x for weblogic. I am using the code given in the documents to generate PDF given XDP and XML data, using Output Service. I am getting the following error, Exception in thread "Main Thread" com.adobe.idp.DocumentError: error un

  • Unable to send to BB via bluetooth......

    Hi, As a new BB user I'm trying to get to grips with how it works.............I've been trying to send pics,mps etc to my BB via bluetooth but keep hitting a brick wall.  I've read up on a few posts on what to do but I've tried everything suggested b

  • Cut and Paste between Events not working

    Using iPhoto11, I can drag and drop pictures between events, no problem...but Cut and Paste does not work. I select a photo and cut in event A, go to event B, I right click and get a PAST button, It even clicks but nothing happen, the Cut image never

  • How to define the Index on the column which is define in view (9i)

    hi all, I have one view which is based on to tables say 'customers' and 'vendors' view definition is like: create or replace view customer_vendor as select customer_name, 'Customer' type from customers union all select vendor_name, 'Vendor' type form

  • IPhoto doesn't recognize jpeg's

    I don't remember anything like this with previous versions. I have been using iPhoto for years, I have tens of thousands of images from a variety of sources (camera import and Photoshop) in multiple libraries. Today I found that iPhoto '09 (version 8