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]

Similar Messages

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.

Aperture 3.1 - White Balance Doesn't Update

Since upgrading to 3.1 I have noticed a somewhat annoying behavior with the White Balance data.
When I change from one selected image in a project to another image the White Balance data does not update.
If I deselect so no image is displayed and then select the new image, the data does update.
This only happens with images on which I have not made a manual White Balance adjustment. If I have made an adjustment then the data displays correctly on the adjusted image when it is selected. However, then selecting an unadjusted image causes a reversion to the 'incorrect' behavior.
Note that the image appearance does not change, so the actual image is not affected by this, only the display of the data.
Is anyone else experiencing this?
If so - any suggestions on how to fix?

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

Z1 White Balance Displa Setting

May I ask how to see the white balance setting into the display setting for Xperia Z1? Bec. I have Xperia Z also and the white balance setting is already seen but into my Z1 I can't see the white balance setting to adjust the screen display hope to answer back in able to fix my Xperia Z1 yellow hue tint problem using the "White Balance" in display setting. Thank you

No White Balance option in Z1. Can;t say what made them remove this.
Sony just removed the "optimized backlight option" from this new 14.1.G.2.257 firmware.
YELLOW HUE tint is still there. Display is even more DIM in this new update.
In Short Another update full of bugs have been rolled by Sony.
NFC icon doesn't appear after activating it.
Automatic switch off issue still there.
P.S. Don't ask to update our Z1 again by SUS or PCC, whenever use reports we get only this answer. Why don't Sony make a stable firmware. It has been more then a month and still Z1 has not got a stabel firmware.
Don't forget to give Kudos.

Z1 camera vs z camera, lacks white balance

i have compared the camera shots yesterday. why is the camera of z produces better shots? z1's camera shot samples are so grainy and noisy. im disappoinyed because im planning to buy z1 soon. and it also lacks white balance on display which imprives the over all display quality of the device.
SONY PLEASE DO SOMETHING!!!
IM DISAPPOINTED, I WANT TO BUY Z1,
BUT IT NEEDS MORE IMPROVEMENT.
I HOPE MY CONCERN REACHES YOU.
THANKS A LOT.

It does
http://userguide.sonymobile.com/referrer.php?region=global-en&product=xperia-z1#General-camera-setti...
White balance
This function adjusts the colour balance according to the lighting conditions. The white balance setting icon is available on the camera screen.
Auto
Adjusts the colour balance automatically to suit the lighting conditions.
Incandescent
Adjusts the colour balance for warm lighting conditions, such as under light bulbs.
Fluorescent
Adjusts the colour balance for fluorescent lighting.
Daylight
Adjusts the colour balance for sunny outdoor conditions.
Cloudy
Adjusts the colour balance for a cloudy sky.
This setting is only available in Manual capturing mode.
"I'd rather be hated for who I am, than loved for who I am not." Kurt Cobain (1967-1994)

White balance and RAW

I have been importing RAW files from my Canon S70 for a while, and everything has worked very well. Recently, however, imported RAW files are showing up with the incorrect white balance in iPhoto (different from the one they were taken with on the camera). If I open the same RAW file in any other editor the correct white balance is displayed. Does anyone know how I might fix this?
The weird part is that it didn't used to do this--iPhoto used to display all my RAW files w/ the white balance they were taken with. It was nice because I could just export JPGs directly. Now, however, I have to open them up in another editor and export so they have the correct WB.
Any help would be great, thanks.

Heya Black eyes,
I've never heard of this one before except in an instance where the person was using Photoshop CS to edit the files right after importing them into iPhoto (Photoshop was adding its own colorprofile and throwing off poor iphoto).
Consider removing ~/library/caches, and ~/library/preferences/com.apple.iphoto.plist, and ~/pictures/iphotolibrary/albumdata.xml to the trash.
Restart your computer.
Test iPhoto - does the issue persist?
If so then try creating a new iphoto library by launching iphoto with the option key.
Import from your camera to there.
If it works then your original iphoto library needs to be rebuilt following kbase 107947 and using all 4 options.
If not then I would make sure that the color sync profiles on your system as a whole have not been changed.
Hope that helps!
Cheers!

LR 1.2 - white balance dropper not working

When I click the white balance dropper, I get the magnifying glass. When I move it, the white balance in the navigator updates real time but if I click on my image it zooms instead of setting white balance. This worked fine with 1.1.
Should I uninstall 1.2 and reinstall 1.1? I'm not sure how to go back to 1.1.

I've had that happen a couple of times for no obvious reasons. I've also noted some general 'cursor confusion' but, again, I can't cause the problem.
It's a minor annoyance.

Nvidia Display Driver stopped responding and has recovered, kernel mode 186.60

I have tried just about everything, including first downloading new drivers, HP put in a new display card and has had it back to the factory two other times.
It still happens and produces a black screen anywhere from 8 to 15 seconds. It happens in all programs, showing no one activity over another.
I think it has to do with the TouchSmart technology, because it's a large "laptop" in technology. It finally happened during the night when HP Advisor was monitoring and they asked for feedback. MAYBE they will discover the problem. It's particularly hard when I had to ship it back to HP (at their expense) and do without it, then have to reinstall things all over again!
I wish someone had the answer!

Sorry it took me a while to get back to my TouchSmart. Here are the details on the "Optional" Windows update that seems to resolve this issue. Hope this helps -PH
    nVidia - Display - NVIDIA GeForce GT 230
   Installation date: ‎10/‎21/‎2010 8:43 PM
   Installation status: Successful
   Update type: Optional
   nVidia Display software update released in June, 2010
   More information:
      http://winqual.microsoft.com/support/?driverid=20366045
   Help and Support:
      http://support.microsoft.com/select/?target=hub

Dell XPS 15 l502x mini-Display Port stopped working after update.

After the updates on the 11-10-2014 my mini-display port (which worked great previously and is part of the Intel Graphics) stopped working.
Am running Arch 64bit with Slim + E19
The symptoms are:
1. Detects monitor from the laptop and xrandr throws no errors
2. Enlightenment thinks the screen is connected and it appears in the screen setup as on.
3. The monitor no longer recognizes that there is a laptop plugged in and just stays off...
kernel.log
Oct 13 10:10:19 localhost kernel: [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder B
Oct 13 10:10:19 localhost kernel: [drm:cpt_serr_int_handler] *ERROR* PCH transcoder B FIFO underrun
Oct 13 14:09:35 localhost kernel: [drm] Wrong MCH_SSKPD value: 0x16040307
Oct 13 14:09:35 localhost kernel: [drm] This can cause pipe underruns and display issues.
Oct 13 14:09:35 localhost kernel: [drm] Please upgrade your BIOS to fix this. (Will look for an update...)
lspci | grep Intel | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
Here are the packages that I think I may have to swap around...
[2014-10-11 19:16] [PACMAN] removed ati-dri (10.2.8-1)
[2014-10-11 19:16] [PACMAN] removed intel-dri (10.2.8-1)
[2014-10-11 19:16] [PACMAN] removed nouveau-dri (10.2.8-1)
[2014-10-11 19:16] [PACMAN] removed svga-dri (10.2.8-1)
[2014-10-11 19:16] [PACMAN] removed lib32-intel-dri (10.2.8-1)
[2014-10-11 19:16] [PACMAN] removed lib32-nouveau-dri (10.2.8-1)
[2014-10-11 19:16] [PACMAN] upgraded apache-ant (1.9.4-2 -> 1.9.4-3)
[2014-10-11 19:16] [PACMAN] upgraded libdrm (2.4.56-1 -> 2.4.58-1)
[2014-10-11 19:16] [PACMAN] installed mesa-dri (10.3.0-3)
[2014-10-11 19:16] [PACMAN] upgraded wayland (1.5.0-1 -> 1.6.0-1)
[2014-10-11 19:16] [PACMAN] upgraded mesa (10.2.8-1 -> 10.3.0-3)
[2014-10-11 19:16] [PACMAN] upgraded mesa-libgl (10.2.8-1 -> 10.3.0-3)
[2014-10-11 19:16] [PACMAN] upgraded libva (1.3.1-2 -> 1.4.0-1)
[2014-10-11 19:20] [PACMAN] upgraded linux-lts (3.14.19-1 -> 3.14.20-1)
[2014-10-11 19:27] [PACMAN] upgraded xf86-video-ati (1:7.4.0-3 -> 1:7.5.0-1)
[2014-10-11 19:27] [PACMAN] upgraded xf86-video-intel (2.99.916-2 -> 2.99.916-3)
As far as I can see my options are to try and roll back via pacman -U in my /var/cache... or to figure out how to make my Nvidia HDMI output work using Synergy...
I suspect this is some type of driver regression (kernel/mesa/xorg) but am not sure as I have not seen much information about this issue online.
Unless someone has a better idea... when I get time to try to resolve the issue I will update this post.
Ok I missed this from dmesg:
[11671.333426] WARNING: CPU: 0 PID: 486 at drivers/gpu/drm/i915/intel_dp.c:137 intel_dp_max_link_bw.isra.9+0x3e/0xa0 [i915]()
[11671.333428] invalid max DP link bw val 0, using 1.62Gbps
[11671.333430] Modules linked in: ctr ccm bnep ipt_REJECT xt_conntrack iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core fuse v4l2_common ecb videodev media btusb bluetooth 6lowpan_iphc coretemp hwmon intel_rapl x86_pkg_temp_thermal intel_powerclamp joydev mousedev snd_hda_codec_hdmi kvm_intel arc4 snd_hda_codec_realtek snd_hda_codec_generic kvm iwldvm snd_hda_intel snd_hda_controller crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel cryptd snd_hda_codec r8169 iwlwifi snd_hwdep dell_wmi snd_pcm sparse_keymap iTCO_wdt snd_timer snd mii iTCO_vendor_support dell_laptop microcode pcspkr dcdbas dell_smo8800 psmouse serio_raw
[11671.333467] thermal soundcore i2c_i801 shpchp evdev mac_hid mei_me mei lpc_ich wmi processor ac battery pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) udlfb syscopyarea sysfillrect sysimgblt fb_sys_fops tun nfs lockd sunrpc fscache vhba(O) bridge stp llc brcmsmac cordic brcmutil led_class bcma mac80211 cfg80211 rfkill bbswitch(O) ext4 crc16 mbcache jbd2 sd_mod sr_mod crc_t10dif cdrom crct10dif_common atkbd libps2 ahci libahci ehci_pci libata xhci_hcd ehci_hcd scsi_mod usbcore usb_common i8042 serio i915 button intel_gtt i2c_algo_bit video drm_kms_helper drm i2c_core
[11671.333506] CPU: 0 PID: 486 Comm: Xorg.bin Tainted: G W O 3.16.4-1-ARCH #1
[11671.333509] Hardware name: Dell Inc. Dell System XPS L502X/0YR8NN, BIOS A04 03/25/2011
[11671.333511] 0000000000000000 00000000c0982604 ffff8800b2b4fa80 ffffffff8152ba1c
[11671.333515] ffff8800b2b4fac8 ffff8800b2b4fab8 ffffffff8106e45d ffff880037c92000
[11671.333518] 0000000000000000 0000000000000004 ffff88014e2d8c00 ffff8801b5a2f800
[11671.333521] Call Trace:
[11671.333528] [<ffffffff8152ba1c>] dump_stack+0x4d/0x6f
[11671.333534] [<ffffffff8106e45d>] warn_slowpath_common+0x7d/0xa0
[11671.333537] [<ffffffff8106e4dc>] warn_slowpath_fmt+0x5c/0x80
[11671.333553] [<ffffffffa00f543e>] intel_dp_max_link_bw.isra.9+0x3e/0xa0 [i915]
[11671.333566] [<ffffffffa00f5539>] intel_dp_compute_config+0x99/0x660 [i915]
[11671.333579] [<ffffffffa00da214>] __intel_set_mode+0xb14/0x1670 [i915]
[11671.333608] [<ffffffffa00dd4e6>] intel_set_mode+0x16/0x30 [i915]
[11671.333638] [<ffffffffa00de623>] intel_crtc_set_config+0xa83/0xdd0 [i915]
[11671.333666] [<ffffffffa0025fa1>] drm_mode_set_config_internal+0x61/0xe0 [drm]
[11671.333690] [<ffffffffa002984b>] drm_mode_setcrtc+0x2ab/0x5b0 [drm]
[11671.333712] [<ffffffffa0019b9f>] drm_ioctl+0x1df/0x680 [drm]
[11671.333728] [<ffffffff811d4db0>] do_vfs_ioctl+0x2d0/0x4b0
[11671.333737] [<ffffffff811df4ee>] ? __fget+0x6e/0xb0
[11671.333745] [<ffffffff811d5011>] SyS_ioctl+0x81/0xa0
[11671.333753] [<ffffffff815317a9>] system_call_fastpath+0x16/0x1b
[11671.333758] ---[ end trace 64be8044e26ca3c5 ]---
Last edited by scmurcott (2014-10-13 19:12:07)

So I downgraded those packages and the kernel with no luck.
I tried to get the HDMI working via Synergy... and failed
I then tested the Display Port on Windows and it did not work there either - exhibiting the same symptoms as Linux - the OS sees the monitor but no data was transferred.
So I ended up using one of my Display Link monitors at work... the USB monitors were ok, just an irritation with a flickering mouse.
I hope it is the miniDP>HDMI adapter and not the port... very frustrated by this problem.
I hope to test another adapter soon.
I think as nobody else is experiencing this issue that it may well be hardware/firmware related.
Hope there is a happy end to this post but not feeling so positive right now.

Raw Update 2.3 + Nikon D90 = Wrong White Balance Temperature

Hi folks. Wonder if someone has had a similar issue and/or has any insights.
Here's the background:
- Aperture 2.1.2 on OS 10.4.11
- Downloaded/installed Raw Update 2.3
- Imported ~800 NEFs from a D90
- On ~15-20 NEFs, pictures show up blue (white balance at ~2500)
- The affected NEFs are semi-randomly distributed among the ~800
Here's why it's weird:
- NEF displays correctly in Nikon View (the thumbnail and full picture)
- NEF displays correctly in the Finder (the thumbnail)
- NEF displays correctly in the preview and thumbnail *in Aperture* but only until the preview and thumbnail processing completes at which point they turn blue (this is why it's especially weird)
- Peeking into the Aperture package, the NEF thumbnail shows up correctly but the preview and thumbnail files show up blue.
If I delete the NEFs from Aperture, close down, and repeat I get the exact same problem on the exact same NEFs. This leads me to believe that there's something specific to the NEFs but it must also be linked to Aperture and more specifically, it's thumbnail/preview process since they show up fine in Nikon View, the finder and Aperture before the thumbnail/preview processing takes place.
Obviously I can't downgrade to Raw Converter 2.1 or 2.2 since my files are from a D90, and I shoot in raw (not raw + jpeg) only so have been limping along with Nikon's software.
Any ideas out there?
Thanks!
Message was edited by: rbhansen57

Hi,
I simply can't see the NEFs.
OS X 10.5.5
Aperture 2.1.2
Nikon D90
Import runs fine, and the thumbs are there, but when opening a NEF a big thumb (7x4.5cm on the 24" screen) is displayed in the middle for a second, and then it turns into a dark red message "Unsupported Image Format".
It's general - no NEFs work for me.
I import directly into Aperture - do you import via the Nikon Software?
Previously I had an Olympus E400 - the RAWs worked fine in Aperture (directly imported).
My strange observations are:
With the Olympus E400 (10MB) the size of the JPG files were 6-7MB and the RAW files (called .ORF) were 21MB.
With the Nikon D90 (12.3MB) the size of the JPGs are around 6.5MB (4288x2848 pixels), but the size of the NEFs are just around 11MB (I did expect over 21MB) and the pixels are 256x170 (although the picture says 4288x2848 on the camera itself).
I'm new to this support site - do Apple supporters take time to read our questions and join these discussions?

I just ran a software update for Java and MacBook Pro SMC, now my Mini Display Port to HDMI TV is not working. The TV is flickering. The Mac Display is fine.

I was just watching / streaming TV off Safari on my actual TV.
I'm using a Mini-Display Port to HDMI cable for the connection to the external display.
Software update popped-up and said there was an update for Java and for SMC.
I ran the update and upon the computer restarting, my external display (my TV) is no longer working. It is now flickering.
It won't work in Mirroring or set up as an extended display.
I've reset SMC / PRAM / Safe Mode / Even restored from a Time Machine backup (From before the updates were done).
What could it be?!

I keep saying this over and over, in the hope that people who do a search will find it. Apple cannot possibly test for or be reponsible for the bazillion combinations of adapter, cables, and TV's out there. The only monitors that are 100% guaranteed to work with the MacBook Pro are the Cinema Displays and Thunderbolt Displays, because, they're made by Apple. They're expensive, but they work perfectly.
My guess is that you bought a cheap MDP to HDMI cable, or have a defective one. From my reading of these boards over the past few months, cheap cables have a high failure rate. And the regular priced ones have only a slightly less of one. Try a new one. Make sure you do not damage the Thunderbolt port.

Do I need to download Mini Display Port to VGA update?

I want to be able to watch movies from the MBP on the TV. (Panasonic 32" about 5 years old). Air Play doesn't work through the ATV, the stream is erratic and unwatchable. Both HDMI ports are in use for other things. So I got a Mini Display Port to VGA adapter and a VGA cord and plugged it into the PC input on the TV. I get the screen to come up (no sound, is that normal?) so it seems to work.
Now I read that there is an update for the Mini Display Port to VGA. I downloaded it then was unable to open it because it said it was from an "unidentified source" (Apple!!!!) Do I need this? The article that described this was dated 2009, so I'm thinking it is way obsolete but I want to be sure.
And what about sound and VGA? Do I need a separate audio in connection, and if so, to what input since the PC input is VGA only.
I know that's a lot of stuff. Thanks.
Mid-2012 MPB 13" 2.9 ghz 8 gb ram
10.8.5

Steve1000,
VGA only supplies video, so no sound is normal. You’ll need another connection to provide sound — perhaps through your audio out (headphones) port?
When you have the Mini DisplayPort to VGA adapter in use, run Software Update; if it doesn’t offer the adapter’s firmware update, then your adapter already has it installed.

Will my Airbook (11" late 2010) w/ NVIDIA GeFORCE 320M 256MB using the Mini Display Port to Dual-Link DVI Adapter support the Dell 3007WFHC (30") monitor at full resolution (2560X1600)

Will my Airbook (11" late 2010) w/ NVIDIA GeFORCE 320M 256MB using the Mini Display Port to Dual-Link DVI Adapter support the Dell 3007WFHC (30") monitor at full resolution (2560X1600).
Works fine at 1280X800 (with out without MDP DL DVI Adapter) - cannot get any higher resolution

Hi ddickson01,
The MacBook Air 11 inch late-2010 model does support 2560 x 1600 resolution on an external display. See this specifications article for reference -
MacBook Air (11-inch, Late 2010) - Technical Specifications
Thanks for using Apple Support Communities.
Sincerely,
Brett L

I have a Samsung HD TV and I purchased a Mini Display port to HDMI Adapter today. For some strange reason I get no display on my HD tv. I even tried switching a few HDMI cables and nothing popped up. I made sure my computer was updated. Help pls

I have a Samsung HD TV and I purchased a Mini Display port to HDMI Adapter today. For some strange reason I get no display on my HD tv. I even tried switching a few HDMI cables and nothing popped up. I made sure my computer performed all software updates, and I even tried calling Apple Support. They just told me to keep trying different hdmi cables and see if anything pops up. Does anybody know what the problem is? My HDMI cable is from "rocketfish" also my display port is too.

You may have the screen refresh rate set higher than the TV is generally able to track reliably. It may be able to get there most times, but occasionally loses sync because it is out of its nominal range.
I suggest you sit down with the manual for the TV and find out what resolutions at what refresh rates it intends to support through VGA, and make sure your screen settings are near (or below) those limits.

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 - Nvidia / Display port update

Similar Messages

Maybe you are looking for