Lightroom 4: Massive BUG with White Balance / Quick Develop. Totally Unreliable!

I just recently updated from LR3 and just now found a massive bug concerning the white balance adjustments in the quick develop module.
After a studio shooting and especially after weddings I use the "make warmer" adjustment in the quick develop panel to give all (a few thousand NEFs) a nicer look all at once.
The great thing about this is - like all quick developments - that it increases the color temperature relative to each image's starting white balance.
Yesterday I wanted to edit my first wedding in LR4 and like in LR3 applied one click "make warmer" to all images at once (previously WB was "as shot").
While I browsed through the images to rate them I noticed some of them were very "pinkish".
After closer inspection it came out that a lot of images (50%-60%) had the following custom WB set: 5316, Tint: +10.
It is always this exact combination no matter what the "as shot" WB was.
That setting of course applies way too much magenta to a lot of images.
After resetting the WB of single images to "as shot" and selecting "make warmer" once again the images look fine and get appropriate WB values.
But every time I select more than one image to apply "make warmer" a lot of them get the strange value of 5316 and +10.
Sometimes it's even just the first few images of the selection that get correct values and all the following ones get the off value. It appears to be totally random.
I tried completely resetting all images prior to "make warmer", setting them to different camera profiles first and even switched them to Process 2010 again. But absolutely no luck!  :-(
The "make warmer" tool gives me totally unusable results.
I find it strange, that I couldn't find anything about that on the net.
PLEASE fix this ASAP.
To apply WB to thousands of images individually is a real pain.
I would be glad to support you fixing the issue.
My setup:
Nikon D700
Nikon D300s
(Both cameras affected, I only shoot NEF)
Win7 x64
LR4.1 as well as LR4.2 RC

@ssprengel
I get your point but that is exactly my problem.
Not only is there no pattern but also once I reset a file that got 5316+10 to "as shot" and select "make warmer" for it again it does get the correct value! As long as I select it as a single file without others.
So just to simplify my findings and explain what I have been doing all night:
- SELECT 5 files in Library View (all freshly imported, no settings altered, WB "as shot")
File 1: 5700 / -8
File 2: 5500 / -8
File 3: 5550 / -8
File 4: 5450 / -6
File 5: 5500 / -7
- CLICK "make warmer" once
Result:
File 1: 6089 / -8
File 2: 5867 / -8
File 3: 5316 / +10
File 4: 5316 / +10
File 5: 5316 / +10
1 and 2 are okay!
- SELECT 3-5
- RESET THEM
Result:
File 3: 5550 / -8
File 4: 5450 / -6
File 5: 5500 / -7
- CLICK "make warmer" again
Result:
File 3: 5316 / +10
File 4: 5812 / -6
File 5: 5867 / -7
File 4 and 5 are okay!
- SELECT File 3 again
- RESET IT
- CLICK "make warmer"
Result:
File 3: 5923 / -8
now File 3 is okay, too.
It is completely random!
But that is no way to work, of course.
I have two weddings from last week and am going nuts already.

Similar Messages

  • I downloaded Lightroom 5 but tab with White Balance Dropper have disappeared?

    White Balance dropper tab dissapearence in Lightroom 5.3

    You need to restore the Basic panel:
    http://www.lightroomforums.net/showthread.php?19775-Missing-Panels-Modules

  • The panel with White Balance, contrast, exposure, whites, blacks, etc. has disappeared from my Develop screen

    The panel with White Balance, Exposure, Contrast, Tone, Whites, Blacks, etc has disappeared from my Develop screen.  The control panel on the right side now starts with Tone Curve and I can't find a way to revert back to the screen with the other adjustments. I need to know how to correct this problem.
    This is what I'm working with now:

    Right click 'Tone Curve' (the title/words) and enable 'Basic'.
    Do you see it?

  • Lightroom 5.3 bug with export images

    Hi,
    I can't export single images in Lightroom anymore. When I choose an image including the watermark the system exports all the latest imported images, but not a single one. Can anyone help me with that?
    -jo

    in your lr5.2, click help>updates...
    bug fixes:
    Issues when upgrading catalog from previous versions of Lightroom.
    Incorrect photos are displayed after switching away from a Publish Collection.
    Catalog optimization did not finish, and was not optimizing the catalog
    Feather of clone spots is set to 0 after upgrading catalog to Lightroom 5.
    Auto White Balance settings are not saved to Snapshots.
    Sony 18-55mm lens is detected as the Hasselblad 18-55mm lens for lens correction.
    Increased Update Spot Removal history steps when in Before and After view.
    Slideshows start playing automatically even when the Manual Slideshow option is enabled.
    Video playback stops when dragging on the scrubber.
    Errors when publishing photos to Flickr through the Publish Service.
    Option + drag on Edit Pin behavior is functioning incorrectly.
    Black border appears around the exported slideshow video.
    Catalog containing images processed with PV2003 were adding a post-crop vignette when catalog upgraded to Lightroom 5.
    Pressing the “Reset” button while holding down the Shift key caused Lightroom to exit abruptly.
    Output Sharpening and Noise Reduction were not applied to exported images that were resized to less than 1/3 of the original image size.
    The Esc key did not exit the slideshow after right clicking screen with mouse during slideshow playing.
    Import dialog remained blank for folders that contain PNG files with XMP sidecars.
    Metadata panel displayed incorrect information after modifying published photo.  Please note that this only occurred when metadata was changed after the photo was published.

  • Help requested with White Balance

    This may come as a surprise to many, but here I am requesting your help, instead of giving it.
    I have filled out a feature request with the following content, already some time ago:
    Would it not be nice to be able to extract the WB settings in K  from the metadata and be able in post to change it to what you should have done during the shoot.
    Say your WB is set to 5600 K, you can extract that from the metadata and with the White Balance effect you can enter a desired setting of say 6100 K. During the shoot you can do that with the Canon XF series, but if you have forgotten to use a warm card instead of the white balance card, this would be a great effect to have. Or in the situation where you simply want a shot to be slightly cooler or warmer, this would be a great feature.
    Interface similar to the scale slider and fully keyframeable. The program monitor should reflect changes in color temperature immediately. Simple, easy to understand, like using a set of Warm Cards after the shoot.
    Retrieval of the color temperatures should not be difficult. It is contained in the metadata:
    It works both with AWB and manual for the XF series. If the camera does not record these data, the effect should be greyed out.
    I request your help to get this feature implemented, since it is pretty simple to implement, is a great help to have when doing multicam work, to fine tune different cameras or to change the atmosphere of a shot. It is far easier than the color correction effects we already have.
    If you agree with me, please fill out a similar feature request. The more requests made, the greater the chance of it being implemented.
    See Feature Request Form

    Harm, I've seen instances of multi-cam shoot cameras that were identical models, using a clone of the settings which still resulted in differences in color.  I've seen this blamed on the chips and the chip manufacturing process.  I've also seen multicam footage from analog cameras that were supposedly balanced before shooting that resulted in shifts.  And then, you have a situation where the atmospherics can alter the color, such as when one camera is close to the action, and the distant camera is shooting through fog or haze that has light shooting through it.
    So again, while you can get in the ballpark with certain regimes, when it comes time to finish, you have to trust your eyes.
    So, for my situation, it's not something that rises to the level of something I'd use enough to warrant a feature request.
    My biggest issue today is that I'd love to see Pr offering bottom-up rendering, the way Avid MC offers it with its Render All option vs. Smart Rendering, which is top down.  I don't like that I have to re-render entire sequences just because I made a little change to an upper layer clip.  That, to me, warrants a concerted campaign or pitchfork mob.
    But, I'll make a pact with you.  If you'll request bottom up rendering, I'll request WB metadata support, OK?

  • Real Problems With White Balance Tool

    I attempted to white balance an image I took using the White Balance eyedropper tool, and selecing an area on a Grey Balance Target. Well, Aperture is doing a horrible job of white balancing the image. With Aperture, I exported the image to Photoshop and white balanced it using levels.
    You can see the side by side images here along with the corresponding RGB values. The image on the left, is the one that Aperture "thinks" is white balanced. Since there doesn't seem to be a way to check RGB values within Aperture I can't say what they really are, other than to use OS X's Digital Color Meter, which shows exactly what Photoshop is telling me...the image has a definite blue cast to it.
    http://www.johnburdick.us/WhiteBalance.jpg
    I don't know if I'm doing something wrong, or if Aperture's white balance function is not working as advertised..
    Any suggestions? Has anyone else had these issues?
    PowerMac G5 Dual 2.3 4.5Gb RAM   Mac OS X (10.4.2)  
    PowerMac G5 Dual 2.3   Mac OS X (10.4.2)  

    Apple are being deliberately deceptive on this issue.
    I have been to a couple of demo's at their store and watched the demonstrator use the same wedding photo each time to highlight the power of the white balance eye-dropper. I think this is the only photo on the face of the earth to give a half-way decent result from the eye-dropper (and even then it's still a little blue).
    When I cornered the demonstrator on this specific issue he tried to use another image (one of the Tibet portraits) and the results were horrible and he was forced to concede that this tool was lousy.
    I simply don't believe the software developers weren't aware of the shortcomings of this and yet they still decided to release and insult their customers with it.
    But this is a minor issue compared with the overall quality of the images coming out of the RAW adjustments.
    I can't understand why photographers are still fighting to make this application work. Sure, as a image selection/management tool it's very nice but beyond that it's garbage.
    I've returned my copy to the Apple Store where I purchased it and received a full refund thankfully.

  • Issues with White Balance and other camera setting...

    I have found a glitch with the camera on the Lumia 800: When you try to change a different white balance setting- (try it with incandescent so you can see the difference) as well as changing the scene (ie to portrait mode) it will flip back to auto white balance, although it will say that it is still incandescent.  If you change the scene first and then the white balance and save those settings, it will take one picture like that and then revert back to auto white balance again for the next shot, but again it will tell you that it is still incandescent. (You can clearly see the white balance difference between the 2 shots, even though the camera settings say they should be the same). The whole point of saving settings is so that you can take multple shots with the same settings.  I have spent hours on the phone to Nokia trying to explain this to them and they have assured me that it will be fixed in the next update.  I took the phone back to the Orange shop and we tried 3 different handsets and they all had the same problem.
    I also have the same problem with video autofocus that  lots of people have mentioned.  Has anyone found a solution yet?  The main reason I got this phone (only last week) was for the camera so I am diappointed.  I am a photographer so I am really fussy about cameras!  They have said in the Orange shop that I can change the Lumia for another phone, such as a Galaxy S2, which is also an awesome phone.  The thing is, I really love the Lumia otherwise.  I really like the fact that I don't have an iPhone anymore, for a start!!
     Does anyone think the network you are on makes a difference? It's just that several people have suggested that there could be a conflict with the Orange software and the Nokia/Windows software.  Does anyone else have this problem who is not with Orange?

    Thanks for all of your valuable suggestions.
    The problem was compounded when there were drastic shifts in the levels of ambient light also occuring at the same time.
    Happy Holidays to everyone.
    Bruce

  • 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

  • Select area with white balance picker

    Here's an improvement that would make it much easier to make accurate white balance picks:
    A white balance picker that can sample an area of pixels.
    This can be done in two ways:
    1. Perhaps the simplest and most logical: Make the white balance into an area selector, like the mask tool in Photoshop. The pixels in the square are averaged and used to set the white balance. You could keep the one-click functionality as is.
    2. Give the white balance tool an adjustable sample area. 1x1, 3x3, 9x9 for instance.
    I've been trying to investigate if it is possible to get averaged WB values by picking from a very zoomed-out view of the image. It seems to work, but I'm not 100% sure. Anyone who can fill me in on this?

    I see what you mean (I just tried it) - pretty clear whats going on there...
    The way it is seems pretty good to me - as long as you are willing to use >1:1 zoom ratio for fine control, no?
    i.e. its easy to pick exactly which pixel you want. Are there cases where you would want a pixel in-between? or would it just be a convenience (to use an averaged area) so you wouldn't have to choose amongst candidate pixels?
    Just curious mostly...
    Rob

  • LIGHTROOM CC 2015 Bug with Intuos

    LIGHTROOM CC 2015
    Mac Pro mi-2010 and Macbook Pro mi-2010 - Yosemite 10.3.3
    When you put an overlay, it is possible to change the settings with apple mouse or trackpad, using command key. It’s impossible to change this with Wacom Intuos 4 or Intros Pro (driver 6.3.11-3). all was OK in Lightroom 5.7.1
    Other bug : Pentax 20-40 exif don’t be displayed even when the correct profil is selected.
    Please, share this with developers. Thanks

    Well what do you know ... this might just be a combination of buggy coding on both Adobe's and Wacom's parts.
    One of the problem areas in LR CC or 6.0.1 is as said curves adjustments ... erratic behaviour and unresponsive pen action from using the Pro M tablet made me roll back various drivers, each time clearing the preferences etc. Until I found out that using the latest 6.3.11-3 driver and turning Touch input ON it actually is as instant and smooth action as you'd wish for, if you pick an adjustment point and then two-finger-click-drag.
    Furthermore the general laggy and unresponsive feeling of sliders, and in particular using scrubby sliders, is gone if you choose to use touch input. Place the cursor over the desired slider or value and two-finger-click-drag or respectively three-finger-drag.
    Even scrolling in grid view using touch input works as well! We just can't use the pens for now in Adobe LR CC.
    Please note that in general I've been very satisfied with Wacom tablets and their performance for more than seven years. This is somewhat of a hickup that has been intruduced since OS X Yosemite in combination with newer Adobe applications. None the less it is utterly important to solve these bugs as it makes work frustrating.
    Best,
    Henrik

  • Have taken photos outdoors with white balance set to tungsten by mistake.

    is there a simple solution in pse4 to correct my blue pics

    If above suggestions do not work, try the following
    Open picture file
    Go to Enhance>Adjust color>Levels - not a levels adjustment layer
    Access the white eye dropper and click on something that should be white.
    One can also set the black and gray points

  • Lightroom+RAW+IR+disable auto white balance

    Hi all,
    My question is simple:
    What is the thing (function) who change my raw automaticaly and who to disable it.
    Look, my raw in windows
    http://i569.photobucket.com/albums/ss140/ankhsunamoon/lightroom%20ir/raw_zpsk5empcsa.jpg
    I import this raw lightroom and he's for a few second like that
    http://i569.photobucket.com/albums/ss140/ankhsunamoon/lightroom%20ir/normal%20raw_zps7gktn mx9.jpg
    and after this few second a become like that
    http://i569.photobucket.com/albums/ss140/ankhsunamoon/lightroom%20ir/after%20import%20in%2 0lightroom_zpsjdu6amq5.jpg
    And I don't know why ...
    Thank's for reading I waiting for your answers, regards.

    The IR Treatment is something that is processed in the camera. It is a camera setting that Lightroom doesn't read. That's because the setting is one of those individual settings that is not in a standard location. The reason you can see the effect in the camera and in Lightroom for a few seconds is that you are seeing the embedded JPEG preview. But then Lightroom builds its own preview from the raw image data, ignoring almost all of those in-camera settings. If you want the IR Treatment to show immediately in Lightroom without any adjustments, then you need to shoot that image in JPEG mode. That way, all of the camera adjustments will get "baked" into the image file. Lightroom will not be required to interpret anything.

  • Can you remove the camera white balance setting in Aperture

    I have a Canon 7D and use Aperture for processing and storing my images.
    With the Canon I shoot both video and still and frequently adjust the white balance in the camera.  I make a frequent mistake in leaving the wrong white balance setting on - eg when taking video indoors in the evening  I set the white balance to indoors (the Canon seems poor at white balance decision making on video) and then I forget I'm not using auto white balance and switch to taking a photo with flash.  The result is a horrible blue photo - which if I don't spot the problem at the time seems very hard to correct afterwards.
    I use the Aperture white balance adjustments frequently but unless there is a patch or white or grey I an use the dropper on, I find this particular situation seems to be right off the scale of what I can fix in Aperture.  I end up with sliders at the extremes of the scales and no intuitive sense of what numbers to type in manually to try and get realistic colour - so I often end up discarding these photos even if the shot itself is something I'd like to use.
    So my question is given I'm importing RAW, is there a way to show the phoo without the (wrong) white balance setting I applied in the camera, to let me choose white balance from scratch?
    Or if not, do you have any advice about how to adjust from this very bluey unrealistic colour of image?

    Kirkby - thanks for the quick reply.
    Didn't know you could drag inside a value field - that's helpful.
    But being able to get different numbers on the slider isn't the root of my problem.
    In a specific example I have two photos - one taken with white balance set to flash and the photo was with flash, where after a bit of tweaking to get the colour I want the temp slider is at 5000K (and tint 0).  The second photo has my shooting error with interior lighting white balance but taken with flash.  The two shots were taken from almost the same point of the same view (but different people in frame).  The shot with the white balance error comes off camera horribly blue coloured. I can fiddle with the two sliders - I take temperature to 20000K and tint to 40 to do the best with it I can, and with those settings one of the two faces is approaching flesh colour but the wall behind the subjects (which is a light blue in reality) is now appearing light yellow in places.  I just can't get a good looking colour effect no matter ow extreme the slider settings.
    I may have phrased my question badly - as I totally agree you can't show a raw without a colour setting - so maybe I'm better asking to be able to use a different colour setting on the raw data rather than having to start with adjustments on top of my white balance mistake.
    Given the two shots were in the same place against the same background and the same lighting (both with flash) it seems to me I ought to be able to get a similar colour effect on both and I just can't.  To illustrate here are the two photos (the one on the left was shot with flash wb and in Aperture I'm viewing it with 5000K and 0 tint, the one on the right was shot with indoor wb and in Aperture I'm viewing it with 20000K and 40 tint and it looks terrible!)
    https://www.box.com/shared/qle3t6ovyhrd1egez3vc

  • Aperture 2  and White Balance Tint

    Hello
    Has anyone else noticed the huge colour shift when making a White Balance Tint adjustment with AP2 on a new image?
    When I make an incremental (1 point) Tint adjustment for the first time on a new image the colour changes dramatically (similar to making a 20 point tint adjustment in one go). Hitting the Reset button and then making further incremental WB adjustments eliminates the problem - and everything is back to normal.
    This is happening on both my Nikon D3 and Canon 1DmkIII images, so, I don't think it's a camera specific problem.
    Anyone else?

    I am having the same issue. Clicking in the value box for Temp or Tint causes a big shift. Using the Temp slider causes the image to go green quite a bit. The eye dropper is not much better. It routinely goes warm by a few thousand degrees or gets a green tint.
    I called Apple and walked the tech through the issue and he was able to duplicate it and confirmed it is a bug. It is driving me crazy as I am spending way to much time fussing with white balance.

  • Wrong white balance in NEF files (Nikon D70 RAW)

    Hi
    I have a problem with NEF files: I shoot them with white balance set to Cloudy (6500K), however, in lightroom the white balance is shown as 5450K.
    There is a color shift because of this:
    When I leave the white balance at "As shoot" the image appears OK, however, changing white balance to "cloudy" which is supposed to do nothing, makes the image warmer, obviously because Lightroom believes that the image is shot at 5450K and converts it to 6500K, e.g. makes it warmer, while the image is already 6500K. Changing the setting to, say, "shadow", makes it even warmer.
    Of course I may try to correct the WB "blindly", disregarding the temperature value, but that's annoying.
    The camera is Nikon D70, unpatched.
    Did anyone have the same symphtom?
    Is there any fix or a workaround?
    Thank you,
    Gennady

    When the camera was set to "Cloudy" (6500K) then switching to "daylight" (5200K) makes the picture cooler, switching to "Shadow" (7500K) makes the picture warmer. This is how the camera behaves and this is how Nikon's NEF convertor behaves. Obviously, when the camera was set to "Cloudy", then switching between "As shot" and "Cloudy" should make no change, because "As shot" means "Cloudy", because the camera was set to "Cloudy".
    Now, for some reason, Lightroom believes that the picture was shot with a manual settings of 5450K. I don't know why it believes so.
    And thus, switching from "As shot" to "Cloudy" makes the picture warmer (although it should leave it unchanged), and switching to "Shadow" makes it even more warmer, far warmer that it should be at "cloudy" setting.
    What I expect is that switching from "As shot" to "Cloudy" in the Lightroom would give the same colors as switching from "As shot" to "Cloudy" in Nikon's NEF convertor. And apparently it does not work this way.

Maybe you are looking for