You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Eye strain from LED backlighting in MacBook Pro

There is one relatively serious con of the new LED backlit displays in the new MacBook Pros that seems to not get too much mention in the media. About a month ago I bought a new MacBook Pro to replace my standard white MacBook. One feature of the MacBook Pro that I was unaware of was the introduction of the LED backlit display to replace the CCFL backlight.

Once I started using my new laptop for long periods of time, I noticed severe eye strain and minor symptoms almost similar to motion sickness. After 20 or 30 minutes of use, I felt like I had been looking at the screen all day. Much longer and I would get headaches. If I used the old white MacBook (with its CCFL display), I had no eye troubles at all. Moreover, I could detect a distinct flicker on the MacBook Pro display when I moved my eyes across it - especially over high contract areas of the screen. White text on a black background was virtually impossible for me to read without feeling sick to my stomach because of all the flickering from moving my eyes over the text.

The strangest thing about all of this was that nobody else I showed the screen to could see these flickers I was seeing. I began to question my sanity until I did a little research. Discovering that the MacBook Pro introduced a new LED backlit display started to shed some light (so to speak) on what might be going on. I had long known that I could see LED flicker in things like car taillights and christmas lights that most of my friends could not see. I also knew that I could easily see the "rainbow effect" in DLP televisions that many other people don't see.

My research into LED technology turned up the fact that it is a bit of a technological challenge to dim an LED. Varying the voltage generally doesn't work as they are essentially designed to be either on or off with a fixed brightness. To work around this limitation, designers use a technique called pulse width modulation to mimic the appearance of lower intensity light coming out of the LED. I don't claim to fully understand the concept, but it essentially seems to involve very briefly turning off the LED several times over a given time span. The dimmer the LED needs to appear, the more time it spends in the off state.

Because this all happens so very quickly, the human brain does not interpret the flickers as flickers, rather as simply dimmer light. For most people that is. Some people (myself included) are much more sensitive to these flickers. From what I can tell, the concept is called the "flicker fusion threshold" and is the frequency at which sometime that is actually flickering is interpreted by the human brain as being continuously lit. While the vast majority of people have a threshold that doesn't allow them to see the flicker in dimmed LEDs, some people have a higher threshold that causes them to see the flickering in things like LED car tail lights and, unfortunately, LED backlit displays - leading to this terrible eye strain.

The solution? I now keep my screen turned up to full brightness to eliminate the need for the flicker-inducing pulse width modulation. The screen is very bright, but there are no more flickers and I love my MacBook Pro too much to exchange it for a plain MacBook with CCFL backlighting (which will also supposedly be switching to LED backlighting in 2009 anyway.) The staff at my local Apple store was of course more than helpful and was willing to let me exchange my glossy screen for matte even though I was beyond the 14 day return period. I knew that wasn't the problem though as my old MacBook was a glossy display. I've decided to stick with my full brightness solution. Sitting in a brightly-lit room tends to help alleviate how blinding the full brightness of the screen can be. In a dimly-lit room I guess I just wear sunglasses. Either way, the extreme brightness is worlds better than the sickening flicker I saw with a lower brightness setting

I would caution anybody considering buying a product with an LED backlit display to pay careful attention to make sure you don't have this same sensitivity. Turn the screen brightness down, find a high contract area of the screen, and quickly move your eyes back and forth over the screen. If you can detect the flicker, you may end up with this same problem.

I have no idea what percentage of the population has this sensitivity. I imagine we will hear more about it as more and more displays start using this technology. Hopefully the Apple engineers will come up with a way to eliminate this flicker some of us can see.

Russ Martin

15-inch MacBook Pro, Mac OS X (10.5.4)

Posted on Aug 23, 2008 8:25 AM

Reply
2,489 replies

May 26, 2015 7:53 AM in response to Gurm42

By the way, there IS a way to disable temporal dithering on OSX. It involves a LOT of screwing with KEXT injection and the IOReg settings. There are dithering settings in IOReg that have been known for some time, but they behave differently on Radeon and GeForce chips.


The Amulet Hotkey people have a universal fix, but it is ONLY available to people who buy their video device. Apparently this doesn't just cause eyestrain, it completely botches the ability to run hardware desktop multiplexers because the HDMI bandwidth goes all screwy (imagine a 100% rate-of-change on the entire screen every frame... because basically that's what is happening!)


I'm sending a note to the Amulet guys, but others have posted in their forums with very limited results. I'm not holding my breath at this time. However, it might be worth it to buy one of their units if it gets the fix I want.


I'm actually looking into learning enough XCode to be able to write my own KEXT injection, and make the requisite modifications to the system as an ongoing project. Maybe host it on sourceforge. I'm sure Apple will shut it down, but then again maybe not? Anyone interested in helping/donating?

May 26, 2015 8:05 AM in response to Gurm42

To disable Temporal Dithering for ATI cards in Windows (this information is from 2014, registry values don't always maintain their functionality, YMMV) do this (thanks, Amulet Hotkey Knowledgebase!):


1. Find your Catalyst 2d Driver registry path (in Catalyst Control Center, go to preferences->advanced->Information->Software)

2. Run regedit, browse to that path.

3. Look for the target key, which is either 0000 or 0001 (or both, if you have enough outputs).

4. In that key (or keys), make a new 32-bit DWORD named DP_DisableDither and set it to 1.

5. Reboot.


This should shut down temporal dithering in Windows for Radeon cards of the current generation.

May 26, 2015 8:24 AM in response to Gurm42

Maybe DP_DisableDither is meant only for Display Port (DP). There are also HDMI_DisableDither and TMDS_DisableDither. I tried them all a while ago, but neither of them helped me. WIthout a hardware device one doesn't even know if dithering is really disabled. And maybe it only works for Workstation cards.

May 26, 2015 8:45 AM in response to spprt

spprt, how did you modify them in any substantive way? With a KEXT inject? Wanna chat about this? There are some notes on the differences between Radeon and GeForce and what needs to be set for both/either.


Also, I can pretty much tell just by looking REALLY CLOSELY at the screen if there is temporal dithering happening.

May 26, 2015 9:03 AM in response to Gurm42

Thanks for the posts guys, I didn't actually try disabling dithering in Windows (Bootcamp) because I realised that I can't really use Windows on my Macbook because of my job. Very interesting to hear the link between ATI and temporal dithering though, and to a point this would explain my issues. However I also have problems using my iPhone, some iPads and potentially other screens..


I'm wondering if I have an extreme sensitivity to temporal dithering and another sensitivity to LED light, perhaps the blue light in it. Despite years of searching for answers it's still hard to trace the root of this problem. If only modern Macbooks had Nvidia GFX that would help to confirm or rule out the TD issue.

May 26, 2015 9:39 AM in response to RMartin111

HI Guys, I returned my MBPr last saturday after 15 days of a very hard try with headaches, dizziness and many symptoms described here. I work with computers for about 15 years, 9-5, and never had that issue. I have connected the MBPr to my 2 DELL external LCDs with no differences, so I decided to return it.

I am getting tomorrow the new MBRr with the AMD Radeon R9 M370. I will post here if I fell any noticeable difference with this new card. FYI, as I am using 2 external monitors, the MBPr uses the NVidea card ALL the time, just switching to Iris Pro Graphics when disconnecting the external monitors.


By the way, very informative forum. Thank you all!

May 26, 2015 10:44 AM in response to AMCarvalho

It will be no different.


On OSX, ALL graphics cards have temporal dithering turned on in the kernel. NVidia, Radeon, doesn't matter.


As for your issues, Simon - I too have the same problem. I am going to guess that it is, in fact, a combination issue. I know I'm blue light sensitive, that much is clear. But the "identical monitor works well on a PC with an NVidia card and NOT AT ALL on a Mac" has to be down to the output of the display chip - and that's probably due to temporal dithering.


Many modern devices use this - I guarantee you that your phone is doing it, since nobody is going to spend the $$ necessary to equip a 5" device with a 10-bit-color screen. They're all super-low-power, extremely BLUE-lit, 6-bit-color screens, every last one of them. The notable exceptions are FIRST GEN iPhone 4s's and iPad 2's, which used the very first retina displays in low-yield batches. They were noticeably yellower than the newer models and very likely REALLY supported 10-bit color. Newer Retina displays are 6-bit color like everyone else's, just with more densely packed pixels.

May 27, 2015 12:15 AM in response to Gurm42

Very interesting. If we're relatively confident that this is at least a possibility of what is affecting some of us (and at this stage it seems quite likely), do you think it might be worthwhile setting up a crowdfunding campaign and hiring a Freelancer to develop the kernel extension (KEXT)? I'd imagine that there are a lot of people on this thread who would be happy to chip in a few quid to make it happen.


If we were going to do this we'd need some pretty specific details on what we are needing which is outwith my technical know-how but I'm sure between everyone we could pull it together.

May 28, 2015 2:47 AM in response to SimonStokes

Hi Simon,


I think a crowdfunding campaign to try and make some progress on this problem is a really, really good idea. I'd definitely be willing to make a small contribution to the right piece of work. I'm not a techie, so I don't know for sure that temporal dithering is the right area to focus on, but it sounds from recent exchanges like a reasonable one to have a look at first, if agreement can be reached on what/ who/ how etc. A further campaign to support other work/ investigation could always be considered later.


I for one would love to try and find a workable solution to this issue. I hope others who've viewed this forum might also consider getting on board with this idea. 🙂

May 28, 2015 7:00 AM in response to AMCarvalho

Ok, so I'll get something rolling. I have - in spite of being a 20+ year Internet veteran - never done crowdsourcing/crowdfunding. Do we like kickstarter? Or is there some better place to do it when it's small software development? I don't really anticipate it costing a ton or needing a lot of donations, unless Apple charges for a kit or someone has to be bribed to divulge information... I will need volunteers with different display types though.


This isn't going to be limited to Apple, either. I'm going to make sure that there are patches/apps/etc. for Windows, Mac, and anything else I can think of.


I just bought a Samsung Galaxy Core Prime, and while the screen itself is easy to tolerate, my eyes get really tired because they ARE doing temporal dithering - you can SEE the pixels dancing - so this is a MASSIVE smartphone issue as well.

May 28, 2015 7:17 AM in response to Gurm42

Great to hear that folks are interested in it. Gurm42 - I think Kickstarter is the best way to go as it has the most exposure so we'll have a good chance of making it work. We first of all have to work out what the target we're looking for is - perhaps we should be looking to get an idea from a developer on http://www.freelancer.com/ as to how much nit's likely to cost. I can't imagine it will be that much if we get someone with the right know-how who can work with OSX graphics cards.


I think the scope for how many people this could help in the long run is massive - we should start by getting this KEXT developed for OSX users to test the water and see if this is the problem, and if so I'm sure we could rally up plenty of cash to get multi-platform support in the future.


I love it when a plan comes together..

Eye strain from LED backlighting in MacBook Pro

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.