RGB % values no longer visible in white balance selection tool loupe

When using the white balance selection tool in LR3.3 RC the RGB values no longer show in the loupe window while moving the tool around the picture. The only way I can get the values to show is to stop moving the tool and then click any one of several keys (e.g. Ctrl, or Shift, or Alt, or \, etc.) As soon as I then move the tool the RGB values again disappear until I stop and again click one of the keys. It had worked fine previously in LR3 (?before I updated from 3.2 to 3.3 - that is, the values would show continuously as I moved the tool around the image. Any thoughts about what to do?
Thanks.

Tom Hogarty wrote:
We did catch this bug and it will be fixed in the final Lightroom 3.3 release. Thanks for posting your experience.
Regards,
Tom Hogarty
Lightroom Product Manager
Nice to see you here Tom.. Thanks for the update. Is it somehow related to some of the other issues being reported about the TAT tool, just thinking they are both perhaps "pointer" related?
Jay S.

Similar Messages

Local white balance adjustment tool

I really like the new local white balance adjustment tool. If I could change something will be to give a real color temperature to the tool instead of a number from -100 to 100. Let me give you an example of how I used it today.
I forgot to bring some gels for my flashes for a photo shoot. I was using the flashes to illuminate the foreground and I had fluorescent lightening on the background. It was the perfect opportunity to try the new tool. I knew exactly what the color temperature for both front and back were. I applied the background color temperature of 3200k to the picture and when to locally change the foreground. At this point I was guessing what it should be at. My monitor is color calibrated but I was under fluorescent lights with my laptop. Instead I could have added +2200k or dialed 5500k to the local adjustment tool.
Please let me know if you need more information.

I'm sorry I found another discussion about this topic already. Shame on me I didn't do a more thorough search on it before.
You can find that discussion here
http://forums.adobe.com/message/4138582#4138582

I am on Lightroom 5 and the exposure and white balance adjustment tools on the right side of the scr

I am on Lightroom 5 and the exposure and white balance adjustment tools on the right side of the screen have disappeared. How do I restore them?

Right click on one of the other panel headers e.g Tone Curve and a menu will pop up for you to select Basic.
How it gets de-selected is not apparent but several users have had this happen since the release of version 5. It has ahppened to me on at least two occasions.

White balance selections, Quick Develop and Develop...let's talk

One thing that isn't well-known is that the adjustments in Quick Develop and the adjustments in Develop are *fundamentally different* from each other.
Develop is basically designed to provide *absolute* adjustments to RAW images. It can be used for JPEGs too, but in that case, the white balance setting is not absolute as it's already been corrected in-camera. So the WB settings are meaningless since you don't know where to begin and the temperatures are removed for the same reason. You just start where you are and get warmer or cooler.
Quick Develop is designed to provide *relative* adjustments to all images. What this means is, if you have many images selected and hit the right exposure arrow ">" you'll increase the effective exposure of all of those images from wherever they are now to that plus 1/3 stop. If you hit the ">>" you'll get 1 stop increments.
Since QD is always making *relative* adjustments, it may be reasonable to assume that you have a known, corrected starting point from which to make relative adjustments. That may be why the daylight and other options are available in QD. I personally think this is a bad assumption as you don't know what corrections have been applied in-camera. Thus, I think those options shouldn't appear in QD just like they don't in Develop.
Comments?

The relative vs. absolute of the QD vs. Dev modules is something I'm not familiar with LR enough to dispute. However isn't the point of LR's non-destructive nature, that all actions on an image are relative to the initial baseline, whether it is a RAW or JPG (or Other).
Granted applying a preset WB set of values against a JPG does not make a lot of sense in the development of a repeatable workflow, but if a set of WB values improves a JPG image, who cares. Its all non-destructive and I can reset at any time.
I tend to not like operating in applications that are too stringent in keeping me walled into the "right" way of doing things. Particularly based on the super intelligent decision of the software developer because they know how it is supposed to work. (I have license to berate this group because it is my vocation) Changing the user interface from one module to another (if they both do the same thing) or from one file type to another is not a good thing. Consistency is paramount to user freindliness. If indeed the QD and the Dev modules work differently then it is expected that the controls be labeled differently to express this difference. If a selection is detrimental to the image or will cause application issues it is better to leave the selection visible (for consistency) and disable it (gray out) to keep it from being selected.
The abreviation of White Balance: to WB: in the application is also bad form. It is jargony and does not assist new users to understanding. Screen real estate is scarce and I understand the inclination to do this, but there is a cost.
- Morey

White Balance Selector Tool operation

The WB selector tool still appears as though it only selects one pixel in the the "Pick a Target Neutral" array display window, the one with the x over it (regardles of whether you scale the matrix to 16x16 or 5x5 with the scale slider. It does not appear to allow averaging of adjacent pixels to reduce the effect of random noisy pixels messing up the wb. This has already been brought up in previous threads and the LR team apparently dismisses the concern. Reminder to Adobe Labs: we don't all shoot with relatively noiseless Nikon D3/ D700s. Our cameras do produce significant color noise even at relatively low ISOs. So when we attempt to find a neutral patch or pick a spot on a neutral whibal card with the color picker tool, we see a random array of various shades of gray, some a little more purple, some a little more green in the tool's selection window. Depending on which pixel we place the X on, we get a different white balance. EVEN THOUGH WE ARE HOVERING OVER WHAT IS SUPPOSED TO BE AN EVENLY LIT NEUTRAL BALANCE CARD! Could you guys please talk with your Photoshop colleagues and figure out how to give us a 5x5 or NxN pixel averaging white balance picker. Or maybe you confirm that I am wrong and in fact this tool already DOES average all the pixels I see in the "Pick a Target Neutral" pixel array display? This would be far more useful an option than the ability to put a decorative flourish at the bottom of a menu panel! Thanks.

In addition to the point being made above in regards to a 3x3 or 5x5 pixel eye dropper for the selection of your color balance(color temperature), it would be great to have an eye dropper to select & set your black, white & mid grey(18%) point inside of lightroom to not only neutralize any color cast but also to set your tonal values with a x-rite color checker or similar reference.

White balance selector tool in LR

just a general question here: when using the "white balance selector" eyedropper tool in LR, is this effectively equivalent to neutralizing the greys in PS, i.e. via the midtones eyedropper in a levels adjustment? just curious...

If you have both PS/Adobe Camera Raw and LR applications, you may find this this link helpful:
http://forums.adobe.com/message/3436153?tstart=0
I have both PS CS5 and LR 3, but do 99% of my digital camera and scanner image processing in LR. For things like dust spot removal on slide and negative scans PS CS5 spot healing brush and clone stamp tools are superior to LR's. I also don't need "spot removal" and initial frame cropping of scans to be non-destructive. Once this is done I open in LR and do everything else non-destructively.

White balance selector tool

When i select the wb tool in the develop mode and move it over the image the RGB numbers do not show up in the floating grid.
Is there somthing I need to select for this to work ?
Ken

Ken,
It's a known bug with 3.3RC.
Hal

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.

Does your HP Webcam 5210 White Balance work?

My HP Webcam 5210 White Balance don't work? so all I get is yellow. My HP 4110 webcam White Balance works great. I tried the 5210 on 2 computers and the white balance don't work on either of them so HP is sending me another 5210 webcam. Has anyone experience this or does anyone have a 5210 webcam who's white balance works? HP don't have a Webcam board so I'm not sure where this goes?

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.

How-To: White-balance your image properly Attn: Aperture Team @ Apple

Since Aperture's white balance eye-dropper is more-or-less useless I have taken it upon myself to discover a means to accurately white-balance an image using Aperture.
My method is as follows:
1. Open my desired image in Aperture and hit Z to view at 100%
2. Open up /Applications/Utilities/DigitalColor Meter
3. In DigitalColor Meter, go into preferences and select the following options:
Magnification Factor: 8x
Refresh behavior: Refresh continuously
[X] Float window above other apps
4. Set DigitalColor Meter's "Aperture Size" to the third or 4th notch to get a fairly large radius
5. Move the cursor over the image until DigitalColor Meter's "Aperture" box is over a portion of the image that you want neutral and hit Command(Apple)-L
to lock it at that position
6. Adjust the White Balance controls in Aperture until DigitalColor Meter reads equal (or approximately equal) R G B values
You now have an image that's white balanced accurately for the area you selected. If it is not satisfactory, click on DigitalColor Meter and hit Command(Apple)-L to unlock and repeat the 5th and 6th steps above with a new area.
Notice to Apple's Aperture Team: This is how white balance should work in Aperture. The white balance eye-dropper currently produces pretty random results. When working on this tool for a future update, look at allowing the user to set a radius for sampling the image and build the DigitalColor Meter into the application. This would bring Aperture closer to being a real professional tool.
Dual G5 2.5GHz, 4GB RAM, GeForce 6800 Ultra DDL Mac OS X (10.4.3)

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.

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

Adobe Bridge - White balance metadata

When I browse raw files from my Canon EOS Rebel XT/350D in Adobe Bridge I always look at the Metadata tab to check for the f-stop value, speed, white balance settings, etc. of the currently-selected raw image file.
I noticed that the pictures shot in Automatic White Balance appear on the upper-left portion of the Metadata tab as an icon indicating AWB. However, whenever I take pictures with manually-set white balances, such as shade, day light, tungsten, etc., the metadata tab no longer indicates the white balance I chose, instead, it either shows an icon of a camera or two dashes, as in --.
Is there any way I can set Adobe Bridge to show the appropriate White Balance icon for pictures I take with manually-set white balances?

Hi Curt,
Thanks for your reply. Yes, White Balance is checked in preferences/metadata. All of the Exposure metadata entries are also checked.
I forgot to mention that my version of Camera Raw is 4.5 (the latest).
You know, although White Balance is checked, I cannot find a White Balance text entry on any of the metadata lists (File properties, IPTC core, Camera Data (EXIF), etc.). The only place where I can see the White Balance setting in on the upper left corner of the Metadata tab, under the f-stop value.
Here is a personal question for you: When you browse your pictures in Adobe Bridge and you select one that was taken with a specific White Balance (not Auto), does your Adobe Bridge display an icon for that particular White Balance setting? I just want to eliminate the possibility that this happening only in my computer.
Thanks a lot for your time and attention.

The Lightroom Manual is Not Clear on Options for the White-Balance Tool

In the section "Working with image tone and color" the Lightroom manual states:
Specify a neutral area in the photo
1. In the Basic panel of the Develop module, click the White Balance Selector tool to select it, or press the W key.
2. Move the White Balance Selector into an area of the photo that should be a neutral light gray. Avoid spectral highlights or areas that are
100% white.
3. Set options in the toolbar as needed.
Sets the White Balance Selector tool to dismiss automatically after clicking only once in the photo.
Displays a close-up view and the RGB values of a sampling of pixels under the White Balance Selector.
Zooms the close-up view in the Loupe...."
Item 3 is unclear. I selected the white balance selector, and moved it to an area as instructed,
but I cannot find any toolbar with the options described.
How do I get to this mysterious toolbar?? Everyone seems to think its a simple thing, but I cannot find it and I am not able to set any of the options described!
While I am sure this is a simple thing, I think that the manual should be much more clear about this description; what is there now is very inadequate.

It should be directly underneath the image preview - press the T key if it's not there.

Working Without White Balance

Camera: Nikon D90
Adobe CS5 Design Suite
My goal is to work in Photoshop and Camera Raw without using White Balance.
As I understand, the camera stores within the raw NEF file what was seen by the camera chip without correction. For example, if the camera chip sees say 10,000 red photons, this is stored as say 200. If the camera chip sees 20,000 red photons, this is stored as 400. Hence, it is linear. Of course, the actual storage is as a Bayer array.
http://www.cambridgeincolour.com/tutorials/camera-sensors.htm
In theory, from the raw NEF file, one should be able to reconstruct the image that fell upon the camera chip.
On the camera itself, there are many camera White Balance settings. However, it lacks a "None" i.e. "As Is" setting meaning do not assume anything about the light source and make no correctons. Just record the photon levels and give me back the same image that was focused on the camera chip.
As an experiment, I shot a daylight scene using 2,500K (obviously, an extreme value) for the white balance. When I look at the raw file in Camera Raw, the "As Shot" shows a heavy blue tint. Hence, Camera Raw was using the 2,500K white balance selecting of the Nikon for the "As Shot" setting in Camera Raw. Looking at the Camera Raw basic panel White Balance drop down items, there is no "None". Hence, Camera Raw always assumes there is a White Balance and makes corrections.
Why would I want to do this? For example, I have multiple varied color light sources. I want to see exactly the image my eye sees. I do not want the camera making corrections since there is not a single light source for it to make assumptions about how to correct.
Is there a way in Photoshop or Camera Raw to show me the image without any white balance correction. Thanks in advance.

Petrula wrote:
Camera: Nikon D90
Adobe CS5 Design Suite
My goal is to work in Photoshop and Camera Raw without using White Balance.
As I understand, the camera stores within the raw NEF file what was seen by the camera chip without correction. For example, if the camera chip sees say 10,000 red photons, this is stored as say 200. If the camera chip sees 20,000 red photons, this is stored as 400. Hence, it is linear. Of course, the actual storage is as a Bayer array. In theory, from the raw NEF file, one should be able to reconstruct the image that fell upon the camera chip.
On the camera itself, there are many camera White Balance settings. However, it lacks a "None" i.e. "As Is" setting meaning do not assume anything about the light source and make no correctons. Just record the photon levels and give me back the same image that was focused on the camera chip.
The sensor is linear, but the sensitivities of the red, green and blue channels differ, so one must take these differing sensitivities into account when rendering the image from the raw data. As demonstrated by others, channel multipliers of unity (UniWB) do not yield the intended result. To obtain your intended result, empirically determined multipliers would be necessary. When used for white balance, these multipliers are chosen to that a white target will have equal RGB values in the rendered image. For your purpose, multipliers would need to be chosen so that the white target would assume the color of the incident light. In other words, if the white target were illuminated with reddish light, the image would be reddish and not white.
Why would I want to do this? For example, I have multiple varied color light sources. I want to see exactly the image my eye sees. I do not want the camera making corrections since there is not a single light source for it to make assumptions about how to correct.
Is there a way in Photoshop or Camera Raw to show me the image without any white balance correction. Thanks in advance.
On the camera itself, there are many camera White Balance settings. However, it lacks a "None" i.e. "As Is" setting meaning do not assume anything about the light source and make no correctons. Just record the photon levels and give me back the same image that was focused on the camera chip.
As an experiment, I shot a daylight scene using 2,500K (obviously, an extreme value) for the white balance. When I look at the raw file in Camera Raw, the "As Shot" shows a heavy blue tint. Hence, Camera Raw was using the 2,500K white balance selecting of the Nikon for the "As Shot" setting in Camera Raw. Looking at the Camera Raw basic panel White Balance drop down items, there is no "None". Hence, Camera Raw always assumes there is a White Balance and makes corrections.
Why would I want to do this? For example, I have multiple varied color light sources. I want to see exactly the image my eye sees. I do not want the camera making corrections since there is not a single light source for it to make assumptions about how to correct.
Is there a way in Photoshop or Camera Raw to show me the image without any white balance correction. Thanks in advance.
I infer that you want the captured image to reflect the spectra of the actual scene luminances (or more likely a metameric tristimulus match) rather than how you perceive them. The human visual apparatus exhibits chromatic adaption, whereas the sensor does not. The CIE xyz model assumes complete chromatic adaption and the color models based on CIE models need a white point to operate, so you are attempting to use ACR in a manner other than for which it was intended. There is an interesting exercise on the Stanford web site that shows how one can use a digital camera (the Nikon D70) in conjunction with a spectrophotometer to obtain spectrophotometric data from the camera. To recreate the actual spectra, two additional colored filters are required, but if one merely needs a metameric tristimulus match, perhaps only the three native CFA filters of the camera would be needed.
http://scien.stanford.edu/pages/labsite/2006/psych221/projects/06/clintonk/index.htm
Going back to ACR, experience indicates that if one wants to recreate the appearance of a colorful sunset or a candlelit scene (cases that exceed the limits of chromatic adaption), a daylight color balance works best. It would seem intuitively that an equal energy illuminant (CIE Illuminant E) would be appropriate. This corresponds to a correlated color temperature of approximately 5455K.
http://en.wikipedia.org/wiki/Standard_illuminant

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.

RGB % values no longer visible in white balance selection tool loupe

Similar Messages

Maybe you are looking for