White balance in kelvins

Can anyone please explain the difference between adobe camera raw white balance settings (temperature and tint) and white balance in the camera which is measured in kelvins.
let's say i like 5350 for temperature, and  -8 for tint white balance settings. how much would that be in kelvins on my camera?
thank you

Temperature = degrees Kelvin. That's the blue/yellow axis that refers to black body radiation as it heats up ( http://en.wikipedia.org/wiki/Black-body_radiation ).
Tint is just the other axis at 90 degrees to that. The tint axis is green/magenta.
You adjust (fine-tune) along the same two axes in the D800, by moving the point vertically or horizontally. But camera and ACR won't necessarily agree as they interpret things a little differently. In any case: If you shoot raw, there's no need to make fine adjustments to this in camera. Do it in ACR. The camera white balance setting does not affect the sensor data or the file itself. ACR just reads the camera setting to get a rough starting point.

Similar Messages

  • How to copy White Balance settings betweenJPG files

    Hi all,
    Due to a stupid mistake I ran half a day in Joshua Tree National Park with my camera set to only save JPGs instead of RAWs... grrrr.
    I have relevant WhiBal shots from this period, but I cannot figure out how to set the white balance on the related shots since the temp scale in the Basic section of the develop module only seems to works with a relative -100 to +100 setting instead of the Kelvin scale normally used in the RAWs.
    Any ideas on how to "copy" and/or set the white balance in a JPG based on the adjusted value from another JPG?
    Any ideas greatly appreciated!
    Claus.

    Hi John,
    Thanx for the suggestion!
    I thought about this and experimented with it. However it seems that when working on JPGs this method just copies any "+nn" adjustment blindly to the target photos without any consideration to differences in the basic color ballance of the target photos.
    I guess the problem may basically be that if the JPGs do not have any saved info inside the file on the assumed White Balance in Kelvin used by the in-camera JPG conversion there may be no way to make such a relative adjustment between two JPG files.
    So does anybody know whether this info is available in a JPG file converted in cameray? In my case it's a Canon 20d.
    Claus.

  • A dumb question about kelvin and white balance in Lightroom

    I keep reading a high kelvin number is cooler and a low number is warmer, but in light room, in the develope module, the lower number ( 3500 ) is blue, and a higher number, (7000) is very yellow. What am I missing?

    Lee is essentially correct with his analysis but incorrect with the details. The Kelvin colour temperature scale is between Yellow and Blue, not Red and Blue as stated.
    There's a lot of confusion about this, with many digital photographers missing the significance of the difference between cyan and blue, magenta and red etc.
    To be fair, the printing industry has added to the confusion by traditionally calling printing inks Blue, Red and Yellow when they really are cyan, magenta and yellow.
    Even Adobe can get it wrong. In the initial Lightroom beta release, the temperature scale had the colours Cyan at one end and Yellow at the other. I suggested it be changed to Blue to make it correct and less confusing which thankfully was implemented in the next update.
    Despite decades of working with colour both in the darkroom and with Photoshop, I too struggle with the counter-intuitive approach of the colour temperature reading in Lightroom.
    Essentially, if you shoot in light that is too blue, then you need to add Yellow. So the Kelvin number displayed in Lightroom isn't the 'Mired' correction or the amount of Yellow added, but a readout of the scene's original colour temperature before the Yellow correction.
    This can be really useful. I use several different branded flash units with various reflectors and attachments. I recently ran a test, shooting a Macbeth colour checker with all the different combinations.
    I then used the White Balance Selector (dropper) on the neutral 5 patch and wrote down the resulting colour temperature.
    From that I could work out what filter corrections I needed to use on each flash and reflector to produce consistent daylight balance.
    Most flashes seem to be around 6000ºK but I had variation between 5200ºK & 6400ºK with the combinations.

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

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

  • Exif white balance - why can't I see it?

    I have a Canon 5D and I'm trying to figure out how to display the camera's white balance settings in Aperture. I have added White Balance and White Balance Index to the metadata tab, but the only thing showing is either a 1 or a 0 in White Balance. I'd like to see what setting was used on the camera, such as Auto, Daylite, Tungsten, Custom, Kelvin, etc.
    Thanks,
    Andrew

    Try looking at the White Balance in the adjustment panel. It should show the value that it received from the WB setting on your camera.
    TO associate the different WB settings you see there with the Daylight/Tungsten/etc, you could take a series of photos starting with the first WB Setting and so on and then place them in Aperture and check the values in the WB settings panel.

  • Ufraw forgot default white balance presets

    After some upgrade in the recent days, ufraw and gimp-ufraw no longer know the default white-balance presets of "Daylight", "Shade", etc. Additionally, in gimp-ufraw, there is a missing pixmap (red x indicates) next to the still-extant WB options (which are "Camera", "Manual", and "Auto").
    Thanks for all help and work, Arch is lovely and great.
    EDIT: on x86_64. Forgot to include at first, sorry.
    Last edited by cookiecaper (2008-07-24 00:11:03)

    In Develop/Basic next to the big 'Turkey Baster' and the WB: there is a dropdown triangle set to 'As Shot'.
    Dev is in Kelvin and QD is relative.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
    http://donricklin.blogspot.com/

  • D200 white balance presets problem or ACR problem?

    Last night I was playing around with my D200 and an SB800. The scene was just a sofa with a Gretag-Macbeth 24 Patch Color Checker. The object was to see what results I got with the SB800 with the D200 set to the various preset White balance values. (I should point out that the lighting was mixed, but that is not relevant to the results I see.)
    I set the D200 to each of the preset white balance values and then opened the NEF file in ACR. The preset temperature (from the D200 Manual) and the temperature/tint values reported as "As shot' by ACR are shown in the table below.
    D200 ACR 'as shot'
    preset temperature/tint
    tungsten 3000 2950 / 0
    fluorescent 4200 3950 / +31
    daylight 5200 4950 / -3
    flash 5400 6150 / -9
    cloudy 6000 5550 / -7
    shade 8000 7100 / +3
    First of all I don't care if the temperature reported by ACR agrees with the preset temperature quoted by Nikon. What puzzles me is the discontinuity in the values reported by ACR when going from 'flash' to 'cloudy'. Is this a problem with ACR or with the Nikon preset values for these two settings?

    >First of all I don't care if the temperature reported by ACR agrees with the preset temperature quoted by Nikon. What puzzles me is the discontinuity in the values reported by ACR when going from 'flash' to 'cloudy'. Is this a problem with ACR or with the Nikon preset values for these two settings?
    Bob,
    A full answer to your question would require a response by Thomas Knoll or some other ACR expert with knowledge of how Nikon records the white balance and the algorithm used to apply the white balance. However, I can bring up a few points which may shed some light on the matter.
    One should first consider what white balance information Nikon cameras write to the NEF file. The following table refers to the D70 and similar Nikon cameras before encryption of the WB.
    http://www.ozhiker.com/electronics/pjmt/jpeg_info/nikon_mn.html
    The settings of daylight, flash, tungsten, etc are written as descriptive strings, not actual degrees Kelvin. Nikon considers daylight to be 5200K, but Thom Hogan writes that this value often produces a blue result and 5400K might be better.
    The bias value refers to fine tuning between the above descriptive settings, approximately 100 Mired per increment. Finally, the red and blue coefficients are recorded (green would be redundant). Some raw converters such as DCRaw use these coefficients for the "as set" white balance. There is nothing corresponding to the ACR tint, which adjusts in the magenta green axis, whereas the color temperature slider adjusts in the yellow-blue axis. The degrees Kelvin figure specifies the white balance only for a black body radiator.
    Thus there several ways to interpret the WB data. Mr. Knoll has written previously that ACR attempts to produce a neutral white balance appearance rather than the WB numbers. An interesting experiment would be to determine which converter (ACR or Nikon Capture) gives a more neutral white balance on your color checker with the above settings.
    Bill
    http://www.adobeforums.com/cgi-bin/webx/.3bbc87b2/0

  • Does Lightroom read white balance settings in NEF files?

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

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

  • White Balance in LR vs. Aperture

    I'm comparing LR and Aperture for use with my Pentax K10D. What's amazing is how different the RAW conversion is in each program. I now have a full appreciation of RAW files as "digital negatives" and the software programs as "developers".
    For example, a RAW file that appears properly exposed on my K10D will also be properly exposed in LR. However, that same file will be overexposed by 2/3 a stop in Aperture (of course this is recoverable, but interesting nonetheless). I imagine this has something to do with the different tone curves applied to the RAW file by the camera, Aperture and LR. LR seems to be more similar to what is done in-camera on the Pentax K10D.
    One thing I can't figure out though is why white balance values would be different in each program. I thought WB was simply stored as a number (kelvin) in the camera, and the RAW converter just reads that number. Clearly I'm mistaken here, because in several test photos I opened in both Aperture and LR, the white balance is dramatically different. (Both WB settings are "as shot"). For example, for the same photo, in Aperture WB was 5950 and in LR it was 4550.
    The programs must have a different way of calculating or displaying this info, because when I use Aperture's WB settings in LR, or vice versa, the images don't look the same at all. The tint sliders seem to be very different as well.
    Any insight you could offer on this would be appreciated. At the end of the day I can produce very similar results in both programs with adjustments, but I'm trying to figure out which one's default settings are closest to what I prefer.
    Finally... what effect do the following preferences have, and is it advisable to use them?:
    - "Make defaults specific to camera serial number"
    - "Make defaults specific to camera ISO"

    If you consistently get White balances in LR that are far off, it could be that the WB decoding algorithm for this camera is wrong. You might want to submit a bug report in that case. You should be able to see the actual white balance in the manufacturer's software (don't know if pentax makes any). You can also open it up in the open source dcraw (or its outstanding GUI derivative
    ufraw) program. The author of dcraw has basically cracked all the RAW formats that are in use and it almost always reads white balance correctly. Also, exiftool might read those values.

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

  • White Balance Discrepancies

    Hi All,
    I'm having a real head-scratcher here, and wondering if anyone else has run into this. The white balance in Lightroom is much different than what it's supposed to be (as set by the camera). For example (D200 NEF, sunny day, ~2pm):
    Camera WB setting: flash.
    Nikon Capture 4: 5400K
    Lightroom 1.4: 6150K (-9)
    WB: daylight
    NC: 5200K
    LR: 4950 (-3)
    WB: 5300K
    NC: 5300K
    LR: 5000K (-4)
    WB: 5600K
    NC: 5600K
    LR: 5250K (-6)
    You'll notice there's no consistent difference. What gives? Even stranger, when I flip back and forth between the programs, the images appear the same. I know LR and NC have different ways of converting NEF files, but shouldn't these still be reading as the same numerical temperatures?
    Thanks,
    Martin

    Even though Kelvin sounds quite scientific and the idea seems to be based on a scientific well-known concept (black body radiation) there is no standard for how to apply this to color rendition. This is obvious already from the need of a "tint" value. In a well behaved system, you should not need this as the black body radiator only has one parameter - its temperature. So the color rendition process is far more complex than just assuming a black body radiator!
    Here is some reading I found on this forum by one of the main writers of the ACR/Lightroom RAW code:
    >Thomas Knoll - 10:47am Sep 25, 05 PST (#1 of 101) Edited: 25-Sep-2005 at 12:57pm
    This is the normal and expected result of Adobe Camera Raw and Nikon using different camera profiles and algorithms, and is not a bug.
    Because of the different camera profiles being used, when matching white balance values Camera Raw can either match the white balance appearance (which colors are exactly neutral) or the white balance numbers (exact Kelvin/Tint numbers). In these cases, Camera Raw chose to match the appearance, not the numbers.
    Even if the white balance matches, I don't expect an exact overall appearance match since Camera Raw and Nikon software use a different tone curve and rendering algorithms for non-neutral colors.

  • White Balance Why ?

    Hello All, I am by professional standards a beginner videographer of about 5 years experience. I have seen lots of advice around saying set your white balance for this or that lighting. I film a lot of theatre shows with lots of vivid colour, when I used auto white balance the colours were always wrong different shades ETC so I bought a grey card and set my white balance using this and the colours now look very similar to what I am filming. My question is why would you change your white balance according to lighting ? surely once it is set correctly you want it to accurately reflect what the camera is seeing.

    I seldom have the opportunity to do a manual white balance at stage shows, because when I arrive to set up cameras, the house lights are on and the curtain closed and I have no access to the "actual show lighting" until the show is going. So I just use the "Incandescent" setting on all cameras and that has worked well for me. Lighting can and will change throughout the show also, so at least if all cameras are set the same, the color is consistent and I can make tweaks when editing.
    Of course, when I have the opportunity I will always go for the manual white balance (or preset that looks good) for best results.
    Different light sources (sunlight, overcast, incandescent, flourescent, etc.) all have different color "temperatures". Some are warmer (redder), some are cooler (more blue), and so forth. I vaguely remember some of this from sixtth-grade science class, with "kelvin" numbers and such. The human eye compensates for this automatically and always see white objects as white, and other colors then follow suit. Video cameras are not so good at this - AWB attempts it, but doesn't always get it right. That is why the presets and manual option, to TELL the camera, THIS IS WHITE. Once it is calibrated to what "white" is, then all the colors look correct under that particular light source.
    To a degree, footage shot with the wrong WB can be corrected during editing, but often it can be so far out of whack that it never looks quite right. There is no substitute for getting it right when shooting! If someone looks like a blueberry or a sun-burned Martian on tape, good luck getting a nice skin tone in post....
    Thanks
    Jeff Pulera
    Safe Harbor Computers

  • White balance setting not importing from Canon 5D

    I shoot in RAW with 2 Canon 5Ds. On both bodies, the white balance is set to K (Kelvin temp) and is dialed to 5500. But when I import into Aperture, the white balance on the files is not at 5500 for either camera. One camera's files display a whte balance of 5102 with a tint of -16. The other, 5428 and -9. Sure, I know how to batch correct this manually after import, but is there a way I can get it right in the first place?

    That's normal. If you shoot RAW, Aperture will not care what white balance you set on the camera. Once it's imported, then Aperture will try to get the best WB (not sure the logarithm). If you want all your pictures to be 5500K, set one to be 5500K and then lift and stamp the rest.

  • Tricky problem. Opening RAW with Javascript. White balance problem.

    Hi all. Hopefully someone can help with this - its a tricky one.
    I've been using a javascript to send RAW and DNG files to Photoshop CS5 for automatic processing. The script opens the files directly into PS, apparently bypassing Adobe Camera Raw. It always renders the photos with the ACR default settings which can be set in either ACR on Lightroom. The standard Adobe settings are WB (As Shot), Brightness (+50), Contrast (+25).
    My problem is that it ignores any changes I have made to the RAW files in ACR. So if I want to use a custom white balance, its not possible to use the javascript. The script ignores the 'custom' white balance and resets it to 'As Shot'.
    I've tried changing the default values in ACR but the options are As Shot, or a set Kelvin preset such as Tungsten, Sunlight etc. Nothing helps.
    Is it possible for the script to be mindful of the custom adjustments - especially subtle changes to WB - that I have made in ACR?
    The script is below...
    var stacks = app.document.stacks;
    var stackCount = stacks.length;
    for(var s = 0;s<stackCount;s++){
          var stackFiles = getStackFiles( stacks[s] );
          if(stackFiles.length> 1){
               var bt = new BridgeTalk;
               bt.target = "photoshop";
               var myScript = ("var ftn = " + psRemote.toSource() + "; ftn("+stackFiles.toSource()+");");
               bt.body = myScript;
               bt.onResult = function( inBT ) {myReturnValue(inBT.body); }
               bt.send(500);
    function getStackFiles( stack ){
          var files = new Array();
          for( var f = 0; f<stack.thumbnails.length;f++){
               files.push(stack.thumbnails[f].spec);
          return files;
    function myReturnValue(str){
          res = str;
    function psRemote(stackFiles){
          var loadLayersFromScript = true;
          var strPresets = localize ("$$$/ApplicationPresetsFolder/Presets=Presets");
          var strScripts = localize ("$$$/PSBI/Automate/ImageProcessor/Photoshop/Scripts=Scripts");
          var strFile2Stack = "Load Files into Stack.jsx";
          var ipFilePath = app.path + "/" + strPresets + "/" + strScripts + "/" + strFile2Stack;
          var ipFile = new File (ipFilePath);
          $.evalFile( ipFile );
          loadLayers.intoStack(stackFiles);
          app.doAction ('My Action');
          var saveFile = new File('~/desktop/'+(new Date().getTime().toString())+'.psd');
          app.activeDocument.saveAs(saveFile);
          app.activeDocument.close(SaveOptions.DONOTSAVECHANGES);

    Paul,
    this script do perfectly what i need... But unfortunately not in Bridge CS6 :-(
    I use Windows7 64 and CS6. When I run the script from the Extended Script Toolkit, everything works great.
    Then I saved the script in the Bridge folder "startup scripts". At the start of Bridge I get the following error message:
    "Error in C: \ Users \ ... \ AppData \ Roaming \ Adobe \ Bridge CS6 \ Startup
    Scripts \ Stack Batch.jsx
    Line 1: var = app.document.stacks stacks;
    undefined is not an object "
    Bridge and then starts the script is not enabled.
    Thanks for any help
    -kai

Maybe you are looking for