"as shot" white balance display

*Where* do I find the "as shot" white balance for a photo I've already developed? I have Googled and searched the menus for 30 minutes, nothing! (not to mention, to mention, I've tried to post here 3 times, and had my message erased almost every time.)

and I guess, just undo after changing to As Shot, or is there someway more elegant?
I don't completly understand that... Do you mean that you just want to quickly review what the WB in your camera was for the photo, but you want to retain the custom WB setting that you made during developmen? If that is the case, yes, undo afterwards seems to be the best thing to do. If I remember correctly, there is no place in the metadata panel where one can view the original WB information (I don't have LR at my disposal at present).
The same should be true for the flash info, but I am not 100% sure about that right now. Look for it in the metadata panel switched to "EXIF". If an information is not there, it is probably not available in LR elsewhere (except perhaps via a plugin).
Note: The WB values (temp, tint) of "As Shot" do not necessarily equal those displayed by the camera of by the camera maker's software. Actual WB values heavily depend on the raw processing and camera profiles used, and because Adobe/ACR uses different ones compared to the camera maker, there may be substantial differences. I think there was a thread somewhere here in the forum about that...

Similar Messages

  • 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

  • In Develop Mode, always Display As Shot White Balance

    When adjusting WB for RAW images in Develop Mode, it would be really useful to have the As Shot WB visible in RH Pane, along side the Custom WB or other adopted WB.

    and I guess, just undo after changing to As Shot, or is there someway more elegant?
    I don't completly understand that... Do you mean that you just want to quickly review what the WB in your camera was for the photo, but you want to retain the custom WB setting that you made during developmen? If that is the case, yes, undo afterwards seems to be the best thing to do. If I remember correctly, there is no place in the metadata panel where one can view the original WB information (I don't have LR at my disposal at present).
    The same should be true for the flash info, but I am not 100% sure about that right now. Look for it in the metadata panel switched to "EXIF". If an information is not there, it is probably not available in LR elsewhere (except perhaps via a plugin).
    Note: The WB values (temp, tint) of "As Shot" do not necessarily equal those displayed by the camera of by the camera maker's software. Actual WB values heavily depend on the raw processing and camera profiles used, and because Adobe/ACR uses different ones compared to the camera maker, there may be substantial differences. I think there was a thread somewhere here in the forum about that...

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

  • Colour cast using auto White Balance in ACR 7.4

    I am experiencing a yellowish colour cast when I set the White Balance to Auto in Adobe Camera Raw. This happens with pictures taken with the Nikon D7100 and also the Nikon D50.
    Here is an example,
    White Balance set to "As Shot":
    White Balance set to "Auto":

    RASouthworth wrote:
    So I would conclude the ACR auto wb process is apparently not as reliable as the camera determination, and certainly inferior to direct measurement on a neutral object.
    Oh, Auto WB is reliable for what it was designed to do...take the image colors into consideration when determining the auto white balance. It's doing exactly what it's supposted to do...the fact that it's often not what you want shouldn't be a surprise. The way a camera determines WB is by using a WB sensor (either the sensor itself or an external sensor) which is much more accurate than measuring image colors after capture. I've seen Auto WB help in certain cases where there simply is not white neutral in which to measure but I've found manually adjusting WB the best solution in most cases.

  • Aperture incorrectly reading white balance data from RAW file?

    I'm having some problems with both Aperture 1.1.2 and 1.5 importing RAW files from a Nikon D70 and a Canon G6. In both cases, Aperture is not reading the "as shot" white balance correctly.
    With the G6, Aperture is always setting a fixed color temperature of 6016K, and a fixed tint of -15, regardless of the image in question. If I read the same image using Adobe Camera Raw, or Lightroom, then it I get the white balance value as set in the camera.
    With the D70, it's picking up a different white balance value from the one set in the camera, always one far warmer than it should be, and with a green tint. Again, the Adobe tools get the right value out of the RAW file. With both cameras I have experimented with setting the white balance manually on the camera, and also with the "auto white balance" setting, but it makes no difference to Aperture.
    Obviously I can change all of the values manually, but it's very time consuming, and in most cases the in-camera value is pretty close to what I need, so I'd much prefer Aperture to use it.
    In any case, I'm worried about the discrepancy between Aperture and Camera Raw on something so basic.
    Anybody got any ideas? I'm hoping I'm just doing something silly, as I have only been using Aperture for a couple of weeks, and maybe something is mis-configured.
    Thanks
    HG

    In any case, I'm worried about the discrepancy
    between Aperture and Camera Raw on something so
    basic.
    Sorry I can't help you directly with Aperture as I haven't bought it - yet. However, re-the above quote, I'd just mention that the interpretation of colour temperature values is not quite as simple as it might seem. Even more so when you bear in mind that RAW converters from 3rd parties like Adobe or Apple are not based on the RAW conversion engine produced by the camera manufacturer - in effect they have to guess/estimate what the temp/tint values in the RAW file actually mean...
    Some time back I made a series of tests using 3 Canon cameras, with ACR, Capture One & the Canon RAW converter. Each produced noticeably different results, and C1 & ACR showed quite different temp/tint values. (The Canon software only showed 'As Shot' - no values). The differences were consistent between shots from each camera (using WB values input or AWB) - but they weren't consistent from one camera to another. Which program produced the best result depended very much on the Camera/Subject/Personal taste...
    Hope someone can help with Aperture specific info, I'm sure there must be a way of making camera specific adjustments to the RAW conversions...

  • Displayed white balance differs from camera value (Canon .CR2 raw)

    I've noticed that Lightroom will often display a sequence or group of pictures with a very visibly different white balance between consecutive frames.
    Looking at the EXIF info in a sample Canon .CR2 raw (EOS-350D), the recorded colour temperature is 5200K (camera set for AWB), but Lightroom reports this as 4950K after import. For the next frame (continuous shot), the EXIF colour temperature is again 5200K, but Lightroom reports 4900K.
    This still happens in LR1.2 (on newly imported photos).
    Why does Lightroom appear to make its own decision for white balance rather than use the recorded value?
    Thanks,
    Barrie

    In any case, I'm worried about the discrepancy
    between Aperture and Camera Raw on something so
    basic.
    Sorry I can't help you directly with Aperture as I haven't bought it - yet. However, re-the above quote, I'd just mention that the interpretation of colour temperature values is not quite as simple as it might seem. Even more so when you bear in mind that RAW converters from 3rd parties like Adobe or Apple are not based on the RAW conversion engine produced by the camera manufacturer - in effect they have to guess/estimate what the temp/tint values in the RAW file actually mean...
    Some time back I made a series of tests using 3 Canon cameras, with ACR, Capture One & the Canon RAW converter. Each produced noticeably different results, and C1 & ACR showed quite different temp/tint values. (The Canon software only showed 'As Shot' - no values). The differences were consistent between shots from each camera (using WB values input or AWB) - but they weren't consistent from one camera to another. Which program produced the best result depended very much on the Camera/Subject/Personal taste...
    Hope someone can help with Aperture specific info, I'm sure there must be a way of making camera specific adjustments to the RAW conversions...

  • White Balance color temperature for custom temperature shots

    Hello,
    I would like to understand why LR and Photoshop too are always show wrong color temperature "As Shot"?
    Let say I shoot with 6000K, set manually (Canon 40D, RAW)
    Canon itself says it's 6000K in the slide info, fine.
    Both Adobe apps says it's 5750K!
    What's going on there?
    Second question - I know the light was EXACTLY 6000K, but the slide has some green in it. Picking white balance in LR gives me 5900K (which is close to the truth) and +31 Tint, which makes slide neutral.
    Of course I can correct Tint manually before the shot by WB Shift in Camera, so the question is: what is the best way - to find more or less appropriate WB shift in the camera, or use WB correction in LR after all?
    Thanks
    UPD. My suggestion is - Adobe doesn't read custom temperature from RAW file, it's just guessing! Is that right?

    The white balance value you see in Lightroom is profile specific. It reads your custom white balance and translates it so that neutrals stay neutral, which is exactly what you want. If it wouldn't do this, your neutrals would shift in color.
    The best way to get a correct white balance is to shoot a white balance (grey) card or use one of those filters on your camera to measure it. You can either set it in camera from the grey card or do it with the dropper in Lightroom and sync over the series. The effect will be the same.
    P.S. unless you shoot a white balance card, you do not know that the color temp of your light is exactly 6000K. That is quite impossible to know. It might be approximately that under certain standardized conditions but you cannot be sure, no matter what you're told by the manufacturer.

  • Image contains camera White Balance setting; LR 5.5 only shows "As Shot", "Auto", and "Custom"

    I have a new, Panasonic DMC-GX7. I shot a bunch of photos as JPGs. When viewing their Exif data using Exiftool, I can clearly see the camera's White Balance setting, as well as the Color Temp Kelvin, WB Red Level, WB Green Level, and WB Blue Level. However, Lightroom 5.5 only shows "As Shot", "Auto", and "Custom" when I click White Balance under Quick Develop on the Library tab or WB under Basic on the Develop tab. Exiftool shows the Exif Version as 0230 and the Panasonic Exif Version as 0405. Is LR looking for the white balance information in some other field? Do I need to configure it somehow for my camera? I am new to LR (but not to image processing), so could use some help figuring this out.

    The whole question is not so simple as converting to DNG. Yes DNG is openly documented, yes the file can be read, but that does not mean it can be correctly interpreted by other software in the future and the best you can then do is starting the PP of your images from scratch. Imagine a DNG with LR adjustments that in some years you open the file in another software, possibly non-Adobe. Even if the file can be read it will not look the same, as the Adobe specific developing instructions could not be strictly followed. Even if all software manufactures agreed on a common set of adjustments, let's say everybody had a Highlights slider and a Clarity slider and so on, which is unlikely, the results would still be different as the underlying algorithms would be different.
    Disclaimer: I only shoot raw and firmly believe it is the best option, but one must be conscious it has some shortcomings related to the future of our images.

  • White Balance - Nvidia / Display port update

    White balance is shifting back and forth. After installing the Nvidia / Display port update, my "brand new" Cinema Display is malfunctioning. White colors change back and forth from pink to blue every 30 seconds. Anyone else having this issue?

    Other users have reported similar issues see :[White Balance Glitch|http://discussions.apple.com/click.jspa?searchID=-1&messageID=12521251]

  • White Balance "As Shot"

    Hello!
    Not sure if this has been brought up before.
    After importing about 20 shots of the same subject, I realised that the camera's white balance sensor only captured the WB correct in one of them. As I was shooting RAW, it shouldn't be a problem to change the other 19 files to match the one that's correct.
    Using the "synchronising" function doesn't do the job as ALL photos had been imported with WB set to "As shot". LR thinks there is nothing to synchronise as the setting "As shot" is already the same on all files!
    Is there a way to tell the program that it should synchronise the actual Kelvin temperature and NOT the "As shot" setting? A way 'round it seems to to manually change the WB of the correct shot and then manually change it back to the previous value and synchronise the other photos to it afterwards. This is not very straightforward though!
    I would appreciate seeing this issue resolved in the next update.
    Many Thanks
    Frank

    > Is there a way to tell the program that it should synchronise the actual Kelvin temperature and NOT the "As shot" setting?
    Select "custom" on the master image before syncing.

  • Can you make white balance/exposure adjustments on top of current adjustments across multiple shots?

    Hi There,
    We have a bunch of shots taken using natural light - the shots all have completely different exposure and white balance adjustments.
    Now that the shots feel like they've been shot at the same time of day (and on the same day) we'd like to start adjusting the white balance accross multiple shots - but use the current white balance/exposure from each individual shot as the starting point - not reset the adjustments.
    Kind of like baking the current settings or making adjustments on top of current adjustments - or make new adjustments relative to the current adjustments.
    Hope that makes sense - is this possible in Lightroom?
    Cheers

    trshaner wrote:
    I've never used the Quick Develop tool:
    Convince me why it's better
    Quick Develop is for artists, not scientists/engineers - sounds like you know how to use it.
    Ya know, some people use Lr with the histogram closed so as not to get distracted by the technical aspects. I could adjust an image using the histogram only, without looking at the image!
    FWIW, amount of temp/tint per increment is fixed for RGB files. I never figured out how it decides the increment for raws, but I'd very much like to know it, in order to normalize relative adjustments when a mix of raw & rgb files are selected.
    PS - I think the original philosophy was:
    1. After importing, take a quick-dev pass in lib module and adjust all the basics in the ball-park, then:
    2. Fine tune in dev module one by one, if need be and schedule allows... (yes I know there is auto-sync in dev module, but it adjust things absolutely, and the context of this discussion is relative adjustment).
    Via that workflow, there's not so much switching back and forth between lib & dev modules for access to the quick-dev panel during development.
    FWIW, it doesn't suit me well-enough either, which is why I invented Gazoo .
    Cheers,
    Rob

  • Correcting White Balance with no white in shot

    Does anyone have any tips for correcting white balance when the footage has no white objects to act as a reference? This was the classic mistake of shooting outdoors with an indoor setting. We were rushing to utilise a gap in the rain!
    Also, is there any way to tell Premiere how to correct WB via a sort of colour matching, by pointing it towards a correctly white balanced still of the scene?
    Thanks
    Davyd

    This is a really tricky thing. There's a lot of ways to approach it. I had similar problems with a WB correction mismatch between presets on my 7D and 70D. No white in either shot.
    I exported a few frames in to PS first to get a rough idea with what I was dealing with.
    Use the Info window to check something grey.
    Alternately, if there is nothing grey, you can use skin tone patches. This is a common tool used by skin retouchers in PS. Grab a small sample or two from the desired skin tones, either from a 5x5 grab with the eyedropper or just grabbing a small section with the lasso tool and Gaussian Blurring that to heck and back. Once you get a bit of a palette of skin tones you like, you can use that as a reference for your work with the Fast Color Corrector.
    To be honest, I feel the FCC is a little underpowered and I wish I had my AAVC 6 Channel HSL tool from Vegas when color correcting.
    As a Photoshop geek, I am a little uncomfortable with the video color correction toolset.
    To export a frame, click on the viewing panel and hit Ctrl-Shift-E.
    Try opening the frames in Adobe Camera Raw and you can get some temp and tint values that can also help you with your Prem Pro toolset.
    Remember to watch out for channel clipping when making dramatic changes in WB.

  • White balance settings always display 5000K 0 Tint

    Been searching on this, found a few things, but nothing helpful.
    In the past few weeks, it appears that Aperture is no longer interpreting my cameras white balance settings properly. The colors themselves are fine, however, the adjustment applet always shows 5000k with 0 tint. I'm not quite sure when this started, but it's quite frustrating. This appears to be happening on everything newly imported. (I can only verify JPG at the moment, as I'm seeing this on a Canon S95 and 60D, which both don't have RAW support yet in Aperture).
    Anyone ever see this happen, or no of a solution? I'm using Aperture 3, latest updates etc. on OS X 10.6.4. My older files all appear fine, it's just these recents, from these two cameras. Unfortunately, I've sold my other gear, and don't have an older cam around to test. Either way, other products, Adobe, seem to be reading things properly.
    Thanks for any input.

    So all these files are JPEGs?
    Note that white balance works very differently with JPEGs and RAW files. There really is no "white balance" information in a JPEG, and you can't adjust them the same way. That's one of the big advantages of RAW files. I suspect once Aperture supports the RAW files for those cameras, then you'll get proper white balance. Until then, with JPEGs you're kinda SOL. It's a bunch more work. But that's the nature of the medium.

  • White Balance panel just shows, Auto, As shot and Custom but im shooting Raw?

    In my White balance panel, its only have 3 option to choose from, but the rest is nowhere to be seen like the cloudy,daylight,shade, flourescent and tungsten. but im shooting raw in my camera, i dont know why there is no enough options to choose from.

    If you click on an image that is showing you no white balance options, and look the two boxes highlighted in red in the image below, what do those two fields say?

Maybe you are looking for