7 Replies Latest reply: Mar 11, 2012 6:28 AM by 1 Open Loop
Ian Lewis Level 2 (205 points)

I'm using Aperture 3.2.2 and when I use the white balance 'pipette' tool to select neutral grey area no changes are applied.  I think I know how this tool works as I have used it in the past.  The image I am trying to adjust I also know needs adjusting as it was shot using bounced flash off an cream surface.  Of course I can manually change the white balance using the temperature and tint sliders but have found better results in the past using the select neutral grey.


Anyone else having this issue and know of a fix?

MacBook Pro, Mac OS X (10.7.3), MacBook Pro 13" 2.8GHz 4Gb 750Gb
  • léonie Level 10 (90,699 points)

    Is it only on certain images that the white balance pipette tool does not work, or is it a general problem?


    If it does not work on any images, delete the Aperture Preference files, as described in

         Aperture 3: Troubleshooting Basics: http://support.apple.com/kb/HT3805

    for sometimes user interface elements do not work, when preference files are corrupted.


    If only some images cannot be adjusted, then try the library "first aid": repairing permissions and library.




  • Kirby Krieger Level 6 (12,510 points)

    Ian -- Rebooting my clear this clog.  Worth a check prior to the further trouble-shooting Léonie recommends above.


    With the WB eyedropper ("pipette" is better, imho), I have better results when I zoom the Image to 100% first -- but that's for getting it to select the correct pixels, not for getting to select _any_ pixels.


    Post back with your results, if you don't mind.  It's unusual, at least afaik.

  • léonie Level 10 (90,699 points)

    1+!   Reboot first!

  • léonie Level 10 (90,699 points)

    OT: Kirby, I grew up with Unix machines, and I still feel the normal "up time" of a healthy system should be at least a year  without reboot - that is why I always forget about "reboot". To me, rebooting is synonym to surrender and disgrace; even if I know perfectly well, that to keep your Mac happy, alive, and kicking, you should reboot frequently - to clear Memory Leaks, etc. But really, system software should not be leaking memory in the first place.


    Usually I reboot only, if there are memory leak warnings in the Console window, or if I want to avoid force-quitting an unresponsive Application, but am too lazy to terminate it from the Terminal Window.



  • Kirby Krieger Level 6 (12,510 points)



    I grew up with Windows 3™  ^oo .  As a consultant, the second question was always, "Have you rebooted?"  (The first, of course: "Is your computer plugged in and turned on?").  If you had to do a "hard boot" after every command, you knew that you'd found a real bug.


    Apple's OS has declined substantially in "normal up time" in just the last few years (I am pretty sure I didn't re-boot my first Mac until I upgraded the OS -- and I'm on only my second Mac).  Such, I suppose, is partly what one pays for run-away success.

  • léonie Level 10 (90,699 points)

    (The first, of course: "Is your computer plugged in and turned on?").

    That hasn't changed at all over the years

  • 1 Open Loop Level 2 (350 points)

    I think you forgot ...


    Did you do a clean install of the OS? (always my favorite)


    Although rebooting a PC can cause other issues. I recall reading about a user complaint where rebooting caused their cup holder to stop working. When the system rebooted, the CD tray was pulled back in.