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?

Similar Messages

Retaining custom White Balance on importing Raw IR files

How can I stop LR from changing my custom White Balance on importing RAW Infra Red files_

LR does interpret camera-embedded WB numbers but it is limited to 2000K on the red end. Is your custom WB below 2000K?
The way around LR not being able to go red enough for IR is to make a custom camera profile with the DNG Profile Editor that includes a negative WB calibration shift, which can further subtract from the normal limit of 2000K. That still won’t help translate a camera number to a LR number, I don’t think, but it would help you apply a LR-computed number to your IR images, normally by eyedroppering your Custom WB raw in LR with the IR profile place.
Tutorial 4 on page 8 of the DNG Profile Editor documentation describes what to do for IR photos:
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/cs6/ DNGProfile_EditorDocumentation.pdf
The DNG Profile Editor itself is available in the Photoshop Resources list:
http://www.adobe.com/products/photoshop/extend.displayTab2.html#resources

LR resets custom white balance on import

Hey guys,
So I photograph my aquarium under blue lights as it brings out the intense colour of the corals more. I set a custom white balance with a card and everything on the camera screen looks fantastic. Once imported, LR resets the white balance and everything shows up as a big blue mass.
Hope someone can help and tell me what I'm doing wrong. Lightroom version 5.6
Example of the same picture on the camera and from lightroom

With underwater photos in Lightroom, the trick is to generate a custom camera profile. Lightroom has an upper limit to the white balance and will cut it off if the camera reports a higher number. There are instructions over here: http://wwwimages.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/cs6/DNGProfile_Edi torDocumentation.pdf (tutorial 4 is what you want but go right on the slider instead of left) on how to do this. You can also take a look at Lightroom: White balance adjustments for underwater photography at Seppo Enervi's instructions.

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

White balance doesn't match CR2 EXIF colour temperature after import?

Why does Lightroom make it's own choice of white balance for "as shot"?
My CR2s from both a 40D and previous 350D all exhibit a shift in colour temperature compared to the EXIF data. It's not even consistent and a sequence of shots can visibly differ.
I know that camera auto white balance has its issues, but it does look like the camera makes a better initial guess than LR....
Thanks,
Barrie

The numbers are dependent on the mathematical model used to model the distribution of wavelengths in the lightsource. The details are rather heady, but indeed, the black body temperature is not as well defined as you might think. This is because a lightsource is seldom an actual black body radiator (not even the sun is due to atmospheric absorption, diffuse scattering on dust particles, and Raleigh scattering on the air molecules). If it were you would not need the "tint" number to describe it. There are quite a few different models for this in use and so it is not strange to see different numbers for the same conditions. In ACR/lightroom they are even dependent on the camera profile if I understand this correctly. Bottom line is that what is neutral in the camera system is neutral in the ACR/Lightroom number system. That's all you need to know.

JPEG and White Balance

When Aperture imports JPEGs it offers the same white balance options as it does for RAW files.
My understandiing from using Lightroom which does not use temperature in it's white balance Develop module for JPEGs, is that there is no data associated with a JPEG that tells the program where to start with white balance.
I'm curious as to what assumptions Aperture makes with regard to white balance when importing JPEGs and what goes on in the background as you change the temperature with a JPEG.
Thank you.

Aperture assigns a temperature of 5000k to all jpg and tif files.
I don't know what goes on in the background but the temperature changes are useful, if not correct.
Cheers,
Terry

Batch White Balance using a reference pixel?

Hi,
I have shot a time lapse image sequence that includes change from day to night & vice versa. The automatic white balance produces unsatisfying results.
Since it's always the same scene, what I would like to do is this: Select one pixel in one of the images and have Lightroom (3.3) use this pixel on each of the images as a reference for white balancing them.
Is this possible?
A solution for Camera Raw or Photoshop (CS5) would also be okay.
Thanks a lot!
Mike

Hi clvrmnky,
hi BDLImagery,
thanks for your replies.
function(){return A.apply(null,[this].concat($A(arguments)))}
The dropper will use an average from that selection to choose a neurtal, shifting all colours to match that new neutral. I suspect this is not what you want.
I do have some snow in foreground which imho makes a nice reference for white balancing since I don't want the snow to be blue, pink or whatever I've got at the moment. Same goes for the clouds. So my idea is to use each pic's snow at the same pixel position for white balancing.
function(){return A.apply(null,[this].concat($A(arguments)))}
Only way I can think of is to create an Action in Photoshop, tie this action with the Lightroom export function and check the "add to this catalog" in the Export window to import the modified photo back in the catalog.
Thought of something like that, too, but the problem is that applying a white balance after import (which this would be) would already work on corrupted data by the previous in-app (camera raw or lightroom) white balance. I tried it on a pic that comes out of the default white balance as completely blue, and you cant rescue that after import to photoshop since by then the original info is lost.
I think I'll now go something like this:
Select all ~5000 images in camera raw, perform white balance on the first one & propagate to the others, then browse forwards to the first one that does not work with these settings, select from that one to the end & do white-balace on those & repeat until done. And to avoid sharp cut-overs do some more or less smooth transitions on the surrounding images.
Kind regards
Mike

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.

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.

Canon 5D MK II white balance set as K does not import correctly

With a 5D II and the Kelvin white balance set in the camera the WB does not import correctly for RAW files and LR 2.4. For example when set to a specified white balance as a Kelvin setting, for example 5200, and then import the raw files with "As Shot" specified or subsequently WB to "As Shot" in Develop module the white balance is set to 4850 +1 (in the example of 5200). The pre set WB options provided inthe camera do work correctly.
Does anyone know if there is a way to set this up to work correctly? Has anyone else experienced this issue?
Thank you.

Does anyone know if there is a way to set this up to work correctly? Has anyone else experienced this issue?
Lightroom does work correctly. The numbers are different, but the appearance ot the colour temperature matches. The way I understand it, cameras don't actually store Kelvin numbers, but store colour space co-ordinates instead. LR and your Canon are interpreting the RAW values into different colour spaces, so the kelvin values and tint numbers will differ.
Hal

Since update to 3.5 issues with white balance

since update to Aperture 3.5 tonight the white balance in all of my pictures is completely wrong (way too cool with a greenish tint).
After setting the white balance with the eyedropper it reads on a Whibal grey card
R: 117
G: 188
B: 156
Any suggestions? Thanks a lot !

I cannot replicate this issue. Upon import of new images (RAW) I tested the White Correction using the eye dropper. No issue at all, despite reports here to the contrary.
In the previous round of this issue, it seems to have only impacted people who did not directly download new photos into Aperture, but rather were using some third party software to first do some processing of them.
The previous issue required some sort of fix not only from Apple, but also an update of the aforementioned third party software (Nik apps in that case.)
Ernie

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

Bug Fix for White Balance Issue (When ?)

Dear Apple:
When can users expect a patch for the bug that "crept" into Aperture late in the development cycle that seriously effects the white balance tool?
This bug is obviously a major concern and issue for most professional-level photographers; and, quite frankly, prevents Aperture from being used in a professional capacity with regard to RAW decoding.
Cheers

Excuse me, John:
But, quite frankly I don't think you are in any position to tell the users of this form how they should feel. Most users, who happen to be high-end prosumers or professionals such as myself, have paid a great deal of money on a piece of software that was supposed to live up to certain, basic expectations. Unfortunately, that software did not. As such it cannot be used in a professional environment.
Subsequently, an update was provided to address all the concerns that users expressed. Unfortunately, that update created a major issue with regard to the white balance of RAW images. Yet again, this expensive piece of software is nearly useless in a professional environment.
Let me ask you this: "if you were a gardner and paid several hundred dollars for a lawn mower, only to discover that it cut your clients' grass unevenly, would you continue to use it? Would you continue to be patient after taking it into the repair shop only to have it still screw up your lawns? Would you not be on the phone with the repair shop constantly until it was fixed?"
Unfortunately, Aperture is a good idea that has a flawed implementation and that NEEDS to be addressed! So, I will continue to ask Joe and Steve and the others at Apple when will this piece of software actually live up to the expectations set forth by the company that produced it!

White Balance jpg Importing Issue

Similar Messages

Maybe you are looking for