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.

Similar Messages

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.

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.

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.

Nikon D700 RAW import shows only dotted boxes, not thumbnails

I am unable to see thumbnails of the RAW images on the memory card of my Nikon D700 when I import images into Aperture.
What I see during an import is a series of frames with a dashed or dotted border that represent the correct number of images on the card. I can select these boxes, but the selection is not indicated with any kind of highlighting, just with a number displayed on the import button. I can, however, import my selection, and once the images are imported, I can see thumbnails in the library.
If I shoot JPG images this is not a problem, only with the Nikon NEF files. I am using the Lossless Compressed format plus a normal quality jpg.
My look at other threads shows some people with D200s have been able to solve this, and they have mentioned fiddling with a USB setting on their camera. However, the D700 has no such setting.
Since Apple now supports the D700 in RAW mode, how can I get the thumbnails of the images in the camera's card to show up on screen during an import? It is a hassle not to be able to see which images I'm importing while I'm importing them.
Thanks!

Ibartram,
I am having the EXACT same problem as you. I have the new Olympus E520— which like the D700, was not suported by Aperutre until the recent upgrade. Like you I was happy to finally have my new camera supported by Aperture and like you, I cannot see thumbnails of my RAW images on my memory card when using the import function in Aperture.
As you have said: Everything is fine AFTER I import, but prior to import, when reading off my card, only empty dotted boxes.
Also, I cannot see the images in the finder either. Are you having this problem as well?
Do you connect your camera directly to Aperture or do you use a card reader? I use a card reader.
Please let me know if you find a solution to this problem. Or if there is any other information I can give you. It's not just a Nikon problem or a D700 problem. After reading your post my guess is that it's a problem with newer, previously unsupported cameras.
It's no good not being able to see which images I'm importing until after they're imported.

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?

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?

Canon 6D importing at custom white balance

I'm using Lightroom 5 and edit images from several different cameras including a Canon 60D, Canon 6D and 4 different Nikons.
All of the images import as expected with the exception of my Canon 6D which automatically import at a custom white balance of 4450. Changing the images to "as shot" does the trick to fix it, but this is an annoying and unnecessary step.
I'm totally stumped as it only happens on this camera, but I've given my cards to other lightroom users and they're not experiencing the same issue on their machines. I *think* I have restored all of the default presets and I've double checked my import presets with nothing looking funky.
Any thoughts of something I may have missed?

It sounds like you have custom camera-raw defaults to include a specific custom WB not As Shot.
There are a couple ways to fix this:
1) Reset to Adobe defaults
2) Update your custom default to include As Shot WB.
Both of these options are available by pressing the Alt key in Develop which will set the Reset button to Set Default… and then choose one of the two options.
If you want to update your defaults with the correct WB, import a completely new picture from the 6D which should have settings of whatever LR normally imports as which a specific WB, set the WB to As Shot, then use (alt) Set Default… / Update to Current Settings to change the Default WB to As Shot.

Nikon D700 color issue

Hellow,
I am shooting with a Nikon D700, and my problem with aperture 3 is that when I upload the pictures Aperture will oversaturate or over boost the colors (specialy green). I've already set the Hue boost to 0 but that doesn't work. I am shooting in RAW (NEF), can someone help me? I am realy frustrated about it
I think it would be a problem with Camera RAW from aperture...

This is just too good to miss so i must put my pennyworth in and stir with wooden spoon.
A raw file is not an international standard as are jpeg's. A Standard is needed.
Camera sensors do not record colour. May be a bit of a surprise to some folkes!
Colour is totally subjective. Just like spelling. Therefore the definition better is with the person or people who think it is, for whatever reasons they think it, especially when it comes to photography. Some people say jpegs are best and i am sure they are for them, i say raw is better, do you disagree?
White Balance can not be set by numbers, between differing raw formats when all the companies involved are trying to discredit and rubbish the opposition and cannot even agree a standard format for their own products. How can we expect competitors to share information and why should they? They probably think they share too much already. Even if they did there would be widespread disagreement about what is better. Where can i get a white balance meter so i get it correct? Oh i'm forgetful, my camera has one built in but now i know it's not accurate what am i to do. It has not been an issue in the past so maybe something is going my way for a change.
Red has always been a difficult colour to reproduce and ever since colour photography was invented, it even gave problems in Orthochromatic photography. Blue in Panchromatic so no surprise when we want full colour.
How many people use a dark room these days? You really should. The ambient light will have a greater effect on your WB setting than you may imagine, maybe even more than the difference in the numbers talked about here. My screen at the moment looks white, as i put the tungsten light up the screen turns blue and then yellow as i ramp it down and if i leave it on or off it soon looks white again. By the way what colour or colours are the walls of your room.
Go in to the Shooting Menu of the D700 then White Balance, press right toggle twice and toggle again to change the WB. Toggle up or down to change the colour without affecting the White Balance.
If this does not resolve the issue go back to good old B&W that will and a good one knocks the spots off colour.
By the way you can have any colour of white except black and neither are colours and there is no difference between the two without the odd photon.
An old screen may be passed its useful life. There may be some gain in checking the screen profile it may need calibrating. You can do this several times and save each one, and if you are getting it correct there should be no difference between each one. This will not solve anything but you then know you are seeing the colours of the screen as intended, as these change over time. Allan

LR4 White Balance Numbers Differ w/ Nikon D4 and D3s

I've noticed that LR interprets the white balance settings differently for my raw .nef files coming from my Nikon D3s and D4 bodies; even when a specific kelvin temp is chosen in camera.
Here's a few examples:
D4 flash WB, LR shows as 6150, +2
D3s flash WB, LR shows as 6400, +9
D4 WB set to 5k, LR reads as 4750, +1
D3s WB set to 5k, LR reads as 4900, +10
Any thoughts on why this is happening, and what (if anything) I should do to get xxxx kelvin temp in camera to import as xxxx kelvin temp in LR?

Eric Chan, senior designer of LR/ACR wrote:
Quote:
The white balance readout in terms of temperature & tint depends on the camera profile (more specifically, the translation between so-called "camera neutral" values and temperature/tint values). Different raw converters use different profiles. This results in different readouts, even if image appearance is the same.
The process of reporting white balance values is non-standardized.
http://www.luminous-landscape.com/fo...2#msg411522%29
Raw converters, whether in the camera or in a computer, do not deal with color temperatures, they deal with multipliers applied to the red and blue channels. But because representing a WB as a pair of multiplier values would be mystifying for most users, the GUI translates those numbers into the corresponding color temperature that the WB will neutralize, a concept more familiar to most photograhers. When "As Shot" is set in the converter it reads from the image file metadata the mutipliers listed there and applies them. However, the WB multipliers are applied after the camera profile and since different converters use different profiles with differing renderings of the basic color values, the post-WB image values are different, even though the same multipliers are used, and the corresponding Kelvin temperature is different.
Now, what happens when you dial a temperature into your camera? The firmware calculates what multipliers will be needed in combination with the Nikon profile in order to neutralize light of that color. Then it records the multipliers in the metadata and, if outputting a jpg, applies them. But if you output a Raw, LR reads the multipliers and does the reverse calculation, "What temperature will be neutralized if these multipliers are used with an Adobe profile?" and does not come back to the same temperature that you set in the camera.
Different cameras = different profiles = different temperatures.

White balance issues after ProKit Update 5.1

After the new ProKit 5.1 update I get a new reprocess block. When I reprocess the image the white balance gets messed up. The Tint sliders go to 50. The white balance presets are all off too. Is anyone else having issue?

This is frustrating me too. Some things I've discovered:
Reprocessing photos tagged with the 1.0 to 1.1 which required reprocessing caused most of the issues. The auto-converted photos would go from 5200K temp, -1 tint or similar to having a wierd tint. However, using a tint around 90 (off the range the tint slider can be adjusted to. Similarly, using the dropper to select a whitepoint results in these out of range tints. However, the tint looked OK, it's just out of the range you can slide it to.
I tried the deletion of the Raw decode plist and that didn't fix things.
Also of note, I have a selection of images with each of my camera's whitepoint settings (a Canon 30d as it happens). If I reprocess each, select the whitepoint brick to enable it and press reset, I get back the whitepoint which was interpretted from the RAW (and hence the cameras whitepoint setting). These also leap from say ~5200K daylight -1 tint (if I recall correctly) to having offscale tints. This suggests there's a new range at play for RAW 3?
Incredibly frustrating. If anyone has any reasonable fixes, I'd love to hear about them, or preferably could we have an update from Apple which resolves the issue.
I understand that reprocessing can cause small shifts, but my photos which have not been heavily adjusted look totally wrong when reprocessed. For now I will not be reprocessing anything until there's a fix.
Also of note, it looks like way back I locked my default raw processor to 1.0 or 1.1. That may have caused issues. I have since reset the camera defaults to the reset RAW processing defaults for 3. I'll try importing some stuff from camera tonight and see what it does.

White Balance Issues

Hello,
I have noticed this for a couple of weeks now. The display on my 2012 MacBook Pro (non-retina) will switch white balance for a second and then flip back to the normal colors. When it does this you can notice a distinct blue-ish tint to the colors on the screen. The first few times it occurred it lasted for only a second and then would be normal. But today it has occurred twice now; the first lasted for a few minutes and the second hasn't switched back. The current OS of my macbook is Yosemite.
I tried going into the display options under system preferences but all the options still have the blue-ish tint to them. Any one else have this problem? I spilled coffee on my mac last week but this was a thing before that happened. I'm really hoping that it's not a sign of the screen dying.
Thanks for any help.
Travis

This is frustrating me too. Some things I've discovered:
Reprocessing photos tagged with the 1.0 to 1.1 which required reprocessing caused most of the issues. The auto-converted photos would go from 5200K temp, -1 tint or similar to having a wierd tint. However, using a tint around 90 (off the range the tint slider can be adjusted to. Similarly, using the dropper to select a whitepoint results in these out of range tints. However, the tint looked OK, it's just out of the range you can slide it to.
I tried the deletion of the Raw decode plist and that didn't fix things.
Also of note, I have a selection of images with each of my camera's whitepoint settings (a Canon 30d as it happens). If I reprocess each, select the whitepoint brick to enable it and press reset, I get back the whitepoint which was interpretted from the RAW (and hence the cameras whitepoint setting). These also leap from say ~5200K daylight -1 tint (if I recall correctly) to having offscale tints. This suggests there's a new range at play for RAW 3?
Incredibly frustrating. If anyone has any reasonable fixes, I'd love to hear about them, or preferably could we have an update from Apple which resolves the issue.
I understand that reprocessing can cause small shifts, but my photos which have not been heavily adjusted look totally wrong when reprocessed. For now I will not be reprocessing anything until there's a fix.
Also of note, it looks like way back I locked my default raw processor to 1.0 or 1.1. That may have caused issues. I have since reset the camera defaults to the reset RAW processing defaults for 3. I'll try importing some stuff from camera tonight and see what it does.

Nikon D2X - DNG vs NEF White Balance Mismatch

Folks, I was hoping someone might be able to help me with a frustrating White Balance issue. Specifically, I have found that my photos often have very different White Balance values -- for both Color Temperature as well as Tint -- when comparing the original NEF and a DNG created by Adobe DNG Converter. (And the images' appearance is reflected by the difference.) If I proceed to correct the White Balance values in the DNG, so that they exactly match the NEF, the images are identical.
You might ask, "Why do you want to convert your images to DNG?" The key reason is that DNG provides lossless compression, which makes a HUGE difference on storage requirements. (Unfortunately, Nikon's RAW compression is lossy, and I cannot afford any image quality degradation -- no matter how slight.)
As far as pertinent info: Camera: Nikon D2X. Platform: Mac OS X 10.4.8, with all updates installed (including the Camera RAW update released a month or so ago). Hardware: MacBook Pro 17" 2.16 (CoreDuo) and PowerMac G5 2.7. Software: Lightroom 1.0 and Adobe DNG Converter 3.7. (DNG Converter 3.6 provides same results.)
In terms of the NEFs, they are uncompressed. (I also took a couple of test shots with compressed NEF, but the results are the same.) In terms of color settings on my camera: Color Mode II, Color Space AdobeRGB. (I know these things theoretically have no impact on RAW files, but I thought I should mention it anyway.)
When searching the Adobe forums, the only directly-comparable issue I found was related to Sony's Alpha camera, using a much older version of the DNG Converter. However, this issue was corrected in later versions. URL of message thread: http://www.adobeforums.com/cgi-bin/webx/.3bbf7680/7
Has anyone else encountered an issue like this? And please tell me that what I am experiencing is not a "feature" of either Lightroom and/or DNG? :-P

Even the professionals are divided on this one, which is why I provided the link I did. It actually supports your statement.
However, my _only_ point was that converting your lossy compressed NEF format photos to DNG will not recover those bits. They are gone forever as a result of the in-camera processing.
Different post-production workflow issues are a completely different thing, and a good reason to switch to DNG (along with the arguments for long-term archival storage).
You did state that your key reason for going to DNG was to take advantage of lossless compression. Ok, but you are taking a lossy compressed original (probably, but this depends on your camera) and converting it to a new format. Regardless of whether that new format is losslessly compressed or not, the original is missing that information. Again, converting to DNG will not recover those bits.
Unless, of course, you have a camera that offers lossless NEFs, in which case conversion and compression might save you quite a bit, as long as you did not save the original NEF inside the DNG.
If you, like me, are stuck with a Nikon that only makes compressed NEFs, then you are stuck accepting lossy compressed NEFs -- NEFs that are quantized in-camera.

Nikon D700 White balance importing issues

Similar Messages

Maybe you are looking for