Incorect White Balance interpretation

Hi,
I have been trying out Aperture 3 for some days and recently run across something like that: I was doing a session with white balance calibrated manually on my camera to 5300K with -3 tint. Adobe Camera Raw reads white balance setting (As shot) exactly as it was set on the camera. Aperture displays something around 4900K and tint -1. Anyone has the idea why? Is there a way to teach Aperture to read WB as it was set on the camera?
regards,

For the future-- the only thing automatic anything on a camera is good for is quickly setting a balance or an exposure. Then flip it to manual. If you study your monitor on set, you'll find stuff you will want to tweak anyway-- lighting adjustments, dialing back half a stop, etc. I almost always shoot at least half a stop under, so I have a little more latitude during color correction.
The light meter is almost a lost art-- because everyone seems to think the camera IS a light meter. There are a bunch of hoops to jump through to understand a light meter viv a vis video exposure- but it is darned useful in lighting your set-- experimentation will tell you how you want your shadow areas to be exposed, how many stops difference do you want your subject and bg to have?

Similar Messages

White Balance Setting Problem

APPLE COMPUTER:
THREE BASIC QUESTIONS THAT NEED TO BE ANSWERED.
1. HOW DOES THE WHITE BALANCE TOOL WORK IN APERTURE?
2. HOW DO YOUR SOFTWARE ENGINEERS AND "PHOTOGRAPHIC CONSULTANTS" USE IT TO SET WHITE BALANCE?
3. WHAT ARE THE SIMILARITIES AND/OR DIFFERENCES IN ITS USE AS COMPARED TO SIMILAR TOOLS IN CAPTURE ONE PRO AND ADOBE PHOTOSHOP?

Test Results:
Aperture 1.1:
Image Temperature: 3594
Tint: -17
When using the white balance tool on a white section of a photo, the RGB values changed from R 255 G 234 B 192 to R 255 G 230 B 197 and the Temperature changed to 3946 and Tint to 12.
The photo still remained unacceptable.
When usint the white balance tool on a grey section of the same photo, the RGB values cahnge from R 211 G 178 B 126 to R 208 G 180 B 162 and the Temperatue changed to 3154 and Tint to 2.
The photo still remained unacceptable but was notably improved.
Using Capture One Pro, the results were as follows:
Temperatue: 3850
Tint: -10
When using the white balance tool on a white section of the same photo, the RGB values changed from R 255 G 241 B 200 to R 244 G 244 B 244 and the Temperature changed to 2500 and Tint to -16.
Photo was very acceptable with no perceivable colour cast.
When using the white balance tool on a grey section of the same photo, the RGB values changed from R 190 G 153 B 108 to R 153 G 153 B 153 and Temperature to 2550 and Tint to -2.
Photo was very acceptable with no perceivable colour cast.
From this quick test on a photo, I can draw the following conclusions:
1. Aperture interprets temperature and tint data differently from Capture One Pro, although this likely due to the use of a camera profile within Capture One Pro;
2. Using the white balance tool in Aperture on a "white" section does not neutralize the RGB values;
3. Using the white balance tool in Aperture on a "white" section does not correctly remove a colour cast within a photograph;
4. Using the white balance tool in Aperture on a "grey" section does not neutralize the RGB values; and
5. Using the white balance tool in Aperture on a "grey" section does not correctly remove a colour cast within a photograph, although it does work better.

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.

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.

Help with RAW files and custom white balance.

ive long had this issue with RAW shooting and adobe photoshop and lightroom, my main subject is a saltwater reef aquarium that is lit by artificial lighting, i shoot canon and use the custom white balance setting to get everything looking proper and it works good.. to an extent.. if i shoot jpg the photos all turn out as shot, if i shoot RAW the white balance in adobe programs is totally messed up and you cant fix it.. if i use DPP by canon, its perfect and looks just as shot or just a a jpg would look.. my question is how can i get adobe lilightroom to render my RAW files correctly.
below are all 3 images, first one was converted and exported to jpg in canon DPP without any adjustments and is what the photo should look like, second has been exported from photoshop, and 3rd i added a link to the actual RAW file. why cant my lightroom interpret these properly?
heres a link to the actual RAW file
https://www.dropbox.com/s/5a39ctllwgrem7a/_MG_8971.CR2
this was a raw converted in canon dpp, and its what the aquarium looks like, and is what the photo should look like. just to note, any other editing or viewing program besides adobe products all render the image correctly.
this is what photoshop and lightroom do to my Raw files, theres no way to adjust anything to get even remotely close to correct..

The white-balance Temperature of this image as computed by the camera is way beyond the 50,000K upper limit as you can see when you open the file in LR or ACR, so Adobe cannot reach the As Shot WB temperature number and stops at 50,000K which is still too blue -- although EXIFtool says: Color Temp As Shot : 10900, so maybe Adobe's wildly high 50,000K number is based on a faulty camera profile that exaggerates blues:
However, using the Camera Standard makes things not nearly so garish blue, and it is possible to use Photoshop to neutralize things even more:
However, as you say, other raw converters do ok with this image despite the high WB temperature, so I think the Canon T3/1100D profile needs some work, but probably won't get it since it is not a high-end camera.
For example, here is the default conversion from LibRaw that is part of RawDigger, and in my opinion is an improvement on the camera rendering though perhaps lacks a bit of saturation:
As another example, here is RawTherapee's conversion, after I neutralized the auto-tone and color values it applies by default, and appears to be a bit too saturated but that could be easily adjusted:
I would agree that Adobe is doing something wrong with this camera in this lighting. A clue is the bright green color of the top-central coral which seems to be yellow in the non-Adobe renderings.

Another white balance presets/settings question

(this is related to two other posts regarding white balance presets, but didn't want to hijack those threads with my own specific questions...)
i've got a canon s70, and have been messing around with a friends copy of aperture. the raw files of my camera are recognized (though the aperture camera support page identifies it as not optimized support), but the problem is that the white balance settings in camera are ignored.
when i view a raw file from my camera in aperture, the exif data shows that it is recognizing different white balance settings (various numbers are displayed here, for example, 1 for auto, 3 for tungsten, 6 for manual, etc). however, the temp. and tint settings are the same for all the images, regardless of wb setting (5278K temp, -18 tint).
so, here are my questions:
- is there any setting i'm missing that would let aperture correctly interpet the wb temp for a specific setting? in another thread regarding canon cameras and wb someone stated that aperture reads wb 'as shot', but it seems odd that it would recognize these different wb settings but apply the same temp and tint calculations across the board.
-i noticed that i can create white balance presets and apply them manually. i was wondering if it's possible to apply preset wb settings automatically. for example, is it possible to create an approximate wb setting for 'tungsten' (3), and then have it applied to all images with the '3' setting, either automatically on/immediately after import, or through an applescript or automator action?
while i could use lightroom, atm lightroom is lacking some features that i crucial to my wider image management/workflow needs (though it does correctly interpret my white balance settings). aperture seems like the best bet for me, but i would rather not go through my library of raw files and manually change the wb settings for each image.
thanks in advance for any help.

I don't know about your other white balance issue, but yes, you can apply a white balance to a selection of images.
Create a set of WB presets (one for daylight, cloudy, fluorescent, tungsten etc.). This takes moments and will be available on any future occasion.
Select and apply your WB preset to an image
Fine tune as needed (since in-camera auto white balance or presets often do not nail it)
Select Lift/Stamp tool
Click on your adjusted image
In the Lift/Stamp HUD, deselect all adjustments except the WB
Select all target images
Click "Stamp Selected Images" button in the Lift/Stamp HUD

Separate luminance and color white balance

I know this is a quite peculiar idea, but i roundtrip to Photoshop a lot just for this..
we all know white balance affects how contrast and luminance of different image areas are interpreted by the software, and at times, especially in low or mixed light, I find that the 'color wise correct' white balance is often different to the 'luminance wise best' one..
i hope this doesn't sound too tortuous, and i really don't know if it would be hard to implement, but it would definitely help a lot with image quality..

ok..
I usually do this for low light portraits or mixed light situation, but it really works for everything, and is quite similar to the "tone" part of topaz detail plugin, for example..
we always choose WB to have a pleasant or correct color rendition, right?
but if we are in black and white, different WB settings affect different areas of the image, lightwise..
and i find out that there is always a sweet spot, depending on the lighting, where noise is better and shadows are better distributed, and and that usually doesn't match to the color WB sweet spot..
this is the original auto wb image
and its bw equivalent
here wb is tweaked to better balance shadows and contrast
but you can see colors are way off..
to give a better idea..
original:
two wbs, obtained with layers color blend mode of original onto bw tweaked
i realize at this size the difference may look small, but it really changes the balance of light, especially with low light or underexposed or mixed light shots..
hope now it's more clear..
cheers
Tommaso

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.

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.

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.

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

Canon White Balance Presets?

Does anyone know if Aperture can read or take advantage of my camera's preset white balance information? In ACR, this is usually a dropdown menu with choices (for my Canon 10D anyways) listed as:
As Shot
Auto
Daylight
Cloudy
Shade
Tungsten
Flash
Any help you be great. Thanks!

I suppose that in a given RAW converter (in this case
Aperture), one will get the same result by setting
the preset "Daylight" on the camera (and using "as
shot" in the converter) versus having the camera set
to whatever other preset, or auto, and entering the
values for Daylight above.
Yes, if Aperture is interpreting the camera's 'Daylight' preset as the same value as quoted above (and remember the values are likely to be different for every camera). Other converters I've used don't respect the exact values for WB that I've input into the camera, but produce their own interpretation of these values, thus show different numbers. So it's unlikely that Aperture is using the same 'numbers' as Canon do for their presets, (though I don't have Aperture yet, so that's a guess).
The actual values would need to be found for each RAW
converter you want to use of course.
Also for each camera with a given converter.

Does Aperture always apply white balance to RAW files?

Hi Aperture users,
I have been an Aperture user for many years. Aperture handles the white balance of my Canon XTi RAW files just as I want it to: it interprets the RAW data by applying the white balance selected at the time of the photo. I.e., when Aperture decodes the RAW file, it makes it look more-or-less like the in-camera JPG with respect to the white balance.
However, in the past several months, many well-known contributors of this forum have stated "RAW is RAW -- Aperture will not apply any camera settings." This statement was made in response to many "novice" questions about why a RAW photo in Aperture did not look anything like the JPG from the camera.
So, my questions:
Does anyone have a camera to whose RAW files Aperture does not apply in-camera white balance settings?
Does everyone else agree that this exception to "RAW is RAW" is acceptable?
thanks,
nathan

Hi Nathan -- I was hoping someone much more informed than me would weigh in with some engineering truth. All I got on offer is the thin gruel of observation.
Mr Endo wrote:
So, my questions:
Does anyone have a camera to whose RAW files Aperture does not apply in-camera white balance settings?
Does everyone else agree that this exception to "RAW is RAW" is acceptable?
1. I don't. RAW is sensor data. Most cameras record the White Balance camera setting as a metadata tag attached to the RAW data (The WB has no effect at all on the captured data.) Most RAW converters use this setting as the default WB. Some RAW converters perform "colorimetric interpretation" -- they basically compare the data captured to a generic color space and assign a WB. (This is, I assume, the same thing a camera set to "Auto WB" does. My camera is superb at assigning a WB for any mixed scene; it's repeatably bad, though, whenever the actual scene is truly colored (meaning "away from average").) In both cases -- 1. using the attached-to-the-RAW-data WB, and 2. analyzing the captured data to intelligently predict the WB -- a WB is applied to the RAW data. It has to be, in order to produce an image from the data.
2. The problem here isn't that this is an exception -- it's that different people mean different things when they say "RAW". The RAW data is RAW data. As above, the WB setting has no effect on it. But the image derived from the data -- any image produced from the data -- much have a WB set (and, for human use, a tone-curve applied). Some people mistaken think that RAW is an image format, or that the image produced by the RAW converter is a "RAW" image. It is not. RAW data must be converted to an image format in order to be displayed as an image. The conversion must apply a WB.
I have found it useful (though perhaps mistaken) to conceive of my data-gathering to picture-making as following these steps:
. Capture a pattern of light. This is just data.
. Convert the data to an image. RAW conversion done by Aperture. (NB: the settings for this can be changed.)
. Adjust the image to my artistic satisfaction
. Convert the adjusted image to an image format file
. Publish the image-format file in one or two now standard forms: to be viewed on a computer monitor, or as a print.
I mention only because at some point I consciously added the "Convert data to image" step in order to better grasp the process. RAW data is RAW data -- but that step identifies an intermediate that many overlook. At that step the information recorded along with the RAW data and stored in the RAW file is applied to the RAW data.
To me, "RAW is RAW" is correct. "Aperture will not apply any camera settings," is wrong.
I am happy for any clarifications or corrections.

White balance information from camera lost?

I don't know what's up with Lightroom and reading the white balance data stored in the .nef files from my camera. Quite frankly it seems that Lightroom eighter has some "interpretation" of Nikon's colors, or that it simply disregard all white balance info.
Is this problem .nef (Nikon)-specific, or does this whitebalance/color-interpretation problem appear with all raw formats?
//Svein

I calibrate against a CBL. As for "how far off", that depends on what calibration I've gotten, but it seems that Lightroom has a predefined "as shot" that is nowhere near the calibration done in-cam. I have verified this against what NX and Bibble gets, and for direct 60degree-north sunlight, Lightroom's interpretation is visibly blue-ish.
//Svein

Incorect White Balance interpretation

Similar Messages

Maybe you are looking for