This discussion is archived
19476 Views 112 Replies Latest reply: Nov 19, 2009 1:12 PM by Iggy65
Currently Being ModeratedSep 3, 2009 5:08 AM (in response to Gary Sumlak)
Gary Sumlak wrote:
Mmm, all quite perplexing.
You said you used a Profile created by a Spider2. Was that since upgrading to SL or prior? Although the article ref posted by A P P L says the old profile should still be valid, if you have not generated a new profile since installing SL, maybe try creating a new one.
Yes, tryed both solutions: an old profile, and a brand new one.
But, the more you describe the problem, the more it sounds like your 100% white is set too close to the black point, and the 0% white (black) is actually set to be in the gray tones, so that you can never achive 0% white while the display is on. As a reference, when you screen is off, the screen should look like what 0% white (black) should look like when the screen is on with a full range picture displayed. If black on the screen does not look "black", but a grayish tone, then you black level is off. This would absolutely prevent your screen from dimming as much as you are use to. If SL can not detect your display, it will use a generic profile that may or may not be appropriate for the screen (in your case not).
In fact, this is absolutely not related to profiles in my opinion. The problem is not color or white point issue, but clearly related to backlight range setting.
Using the F1 key, the very bottom setting should be "Screen Off". The very first step up (on mine) is about 10% lit (completely subjective guess). Still bright enough that I can easily read the display though.
That's right! But since Snow Leopard, and only with 9CC2 displays, the very first step is about 50% lit (subjective too)... Too bright for a first step
Again, if you go through the profile setup manually with SuperCAL, you will see exactly what the brightness level curve is (you will actually see a graph). The process will only take a couple minutes and may point to a solution not previously considered.
I'll try this, but I'm pretty sure profiles can't do anything about the brightness range of the backlight for a display?
Thanks!macBook Pro 13" 2.53Ghz, Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 6:56 AM (in response to NiCOOo)Some update, from another topic.
There is no DisplayVendorID file for 9CC2 panel in Snow Leopard (both on iMac and MBP). That's probably the reason of the "no detection" on the display in 10.6...
If you want, you can check this in SL: /System -> Library -> Displays -> Overrides
I've loaded the version from (thanks to pumppi):
...but it doesn't seem to fix the backlight level issue!
I think there is a trail to follow with "IOBackLightDisplay", but I have my limits in this exploration.
Hope someones with more skills can go ahead!MacBook Pro 13" 2.53Ghz, Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 9:25 AM (in response to NiCOOo)
Well, not sure my english is good enough, but I have at home my MacBook Pro 13" (9CC2) and my brother's one (9CC2 too).
Both laptop are set a the same visual level of brightness: the Snow leopard one (my own MBP) is a level 1, but my brother's one is set at level 8 (but both show same brightness).
When both are set to level 1, my brother's one is really (really!) less bright (but less power eater).
Any chance you could post a picture of your brother's MBP and yours, side-by-side, both at brightness level 1?13" MacBook Pro, Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 10:46 AM (in response to uriaha)I'll try to do that tomorrowiMac Alu 24' 2.4Ghz (mid 2007) — MacBook Pro 13" 2.53Ghz (mid 2009), Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 11:33 AM (in response to NiCOOo)Besides being very subjective, that could be a normal variance in the LCD panels. I have two identical Dell 22" LD monitors side by side, from the same manufacturing run and their appearance isn't nearly the same with identical settings (and I can't get them to be identical no matter how they're set).G5, Mac OS X (10.5)
Currently Being ModeratedSep 3, 2009 12:43 PM (in response to direwolf8)No, I've noticed the problem before having my brother's MBP 13" at home.
11The difference is clear, on my own display... (before / after SL)iMac Alu 24' 2.4Ghz (mid 2007) — MacBook Pro 13" 2.53Ghz (mid 2009), Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 1:08 PM (in response to NiCOOo)It's obviously a bug in the AppleBacklight.kext kernel extension of Snow Leopard.
When you replace /System/Library/Extensions/AppleBacklight.kext (Snow Leopard version 170.0.2) with the version 1.6.0 from Leopard 10.5.8, after a reboot you have again the brightness levels on your MacBook Pro 13" known from Leopard.
I've opened a bug report at Apple, problem ID 7195636 - I don't know if Apple engineers read this discussions...
BTW, when you want to automate the brightness adjustment of your MacBook Pro in conjunction with a LED Cinema Display, maybe my BrightnessSync preference pane helps. It's still beta, but it works fine with Snow Leopard. See http://www.bernhard-baehr.de/ => BrightnessSync.MacBook Pro 13", Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 1:33 PM (in response to NiCOOo)NiCOOo: I just had a clean install of Snow Leopard on my MacBook Pro 13", and I have the exact same problem. It doesn't really bother me that much because I keep my screen brighter, but I do think this isn't a case specific issue and seen that it has affect a lot of people.Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 2:25 PM (in response to direwolf8)I had some extra time today, so I set my MBP to dual-boot Leopard and Snow Leopard. I then compared screen brightness in 10.5 to 10.6 at low, medium, and high brightness, as adjusted by the function keys. Exposure and white balance were set manually and held constant across images. As others have suggested, the minimum brightness on Snow Leopard is roughly equal to the mid-point on Leopard. We weren't crazy!
You can see the results here:
Message was edited by: uriaha13" MacBook Pro, Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 2:34 PM (in response to Pandaholic)@ Pandaholic,
Yes, in my opinion, some thousand of MBP 9CC2 panel owners have this exact problem
Just to confirm, can you check if you have the 9CC2 panel on your MBP 13"?
Thanks for your excellent shot! That's exactly what I'm talking about: hope Apple could fix this ASAP.
By the way: 9CC2 panel too for your laptop?iMac Alu 24' 2.4Ghz (mid 2007) — MacBook Pro 13" 2.53Ghz (mid 2009), Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 2:51 PM (in response to NiCOOo)How do I tell if its a 9cc2 panel?Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 3:01 PM (in response to Pandaholic)Go to Color Sync Utility > Displays > Open Displays > Click Color LCD > At "Factory Profile" on the right side of the window click on Open > in the new window scroll to the second last entry and click on "Apple display make..." > there you've got manufacturer and model.
You can also go to Pref. Panel > Monitor > Color > Select the profile on top (Display or Color LCD) and open it > Go to line mmod > Look at the model number after 0000
Hope this help!iMac Alu 24' 2.4Ghz (mid 2007) — MacBook Pro 13" 2.53Ghz (mid 2009), Mac OS X (10.6)
Currently Being ModeratedSep 3, 2009 3:19 PM (in response to NiCOOo)Yep, 9CC2 panel for me.13" MacBook Pro, Mac OS X (10.6)
Currently Being ModeratedSep 4, 2009 12:50 AM (in response to Pandaholic)There is one thing to do know dear 9CC2 owners:
Hope they'll hear us, and fix it soon...iMac Alu 24' 2.4Ghz (mid 2007) — MacBook Pro 13" 2.53Ghz (mid 2009), Mac OS X (10.6)