Ask Slashdot: Does LED Backlight PWM Drive You Crazy?
jones_supa writes "I would like to raise some discussion about a hardware issue that has increasingly started to bug me: backlight flicker, from which many LED-backlit monitors suffer. As you might know, the backlight and its dimming is driven by a pulse width modulated square wave, essentially flicking the LEDs on and off rapidly. Back in the CRT days a 100Hz picture was deluxe, due to the long afterglow of the display phosphor. LEDs, however, shut off immediately and my watering eyes and headache tell that we should be using frequencies in multiple kHz there. Unfortunately we too often fall behind that. As one spark of hope, the display review site PRAD has already started to include backlight signal captures to help assessing the problem. However with laptops and various mobile gadgets, finding this kind of information is practically impossible. This issue sort of lingers in the background but likely impacts the well-being of many, and certainly deserves more attention."
So do LEDs bother your eyes? I think CRTs gave me headaches far more often than has any form of flat panel display, at least partly because of the whining noise that CRTs emit.
One thing I do know was/is a problem with monitors and eyestrain has to do with fluorescent lighting in the room. We can't see it with the naked eye, but the fluorescents are also flickering at 60hz and I've had it happen in the past that if the CRTs I was using were out of sync, (running at 75hz or similar) after a while I'd get weird eye strain from something we can't consciously perceive but our eyes still try to correct for. I usually solved the problem by either setting the CRT sync rate as high as it would go or syncing it to 60hz, or preferably getting rid of the fluorescent lighting completely in my workspace when possible. Maybe a similar effect is at work here?
For over thirty years now I've been working with various display devices of a wide variety of design, manufacture, size and refresh rates. About sixteen years ago I started having the symptoms you describe -- headaches, watering eyes, etc. The internet back then isn't what it is now, so my first reaction was NOT to post something on a tech forum and open myself up to a lot of ridicule and abuse. Instead, I made an appointment with an ophthalmologist. After a thorough examination and some tests he advised me to take occasional breaks from the monitor throughout the day and rest my eyes. He also gave me some techniques to use for this. I took his advice and my symptoms went away virtually overnight. I have not had any problems since.
You should go see an ophthalmologist -- not an optometrist -- but a real eye expert. You might be surprised to learn that your problem has nothing to do with refresh rates or anything of the sort.
Proverbs 21:19
Am I the only one who has an issue with this definition? I realize that English is an evolving language, but it seems like this became a new definition because too many people were too fucking stupid to understand the actual meaning of the word. Similar to how the word "epic" no longer has the same impact it once did. Perhaps we can redefine "figuratively" to have the classic meaning of "literally".
I suspect author is also bothered by wifi signals emanating from his router.
If my eyes are watering after a long session its because my screen is too bright, which is exactly the opposite of what he postulates as the problem (on off cycles of LEDs). Brighter requires longer "on" cycles, which in turn are less perceptible. Yet for most people overly bright screens are the source of complaints.
Ah, the good old "it doesn't happen to me, he's a liar" reasoning.
PWM lighting is annoying if the frequency isn't high enough. Rates that that drive me crazy don't drive everyone else crazy. I perviously didn't know why some displays made me slightly nauseous and others didn't until I started to dabble in electronics and learned what PWM actually is and built a circuit that gave me headaches.
I don't understand how the carrier frequency is chosen in consumer goods, but it seems in times past it was based around whatever clock source was conveniently available, and those sources are generally completely arbitrary. I found is rather funny how one arbitrary number can make me hate your product if it wasn't high enough.
To be fair, things are a lot better for me now than they used to be. Probably because the conveniently available clock sources are faster now, or maybe some switched to adjusting the current directly? Maybe also that VFDs and LED displays have given way to LCD displays. And nothing was worse to me than a CRT with phosphors that decayed faster than the retrace. Yetch.
More Twoson than Cupertino
I don't understand how the carrier frequency is chosen in consumer goods
I do. I write firmware that does backlight PWM for a living (among other things).
Everyone used to do high frequency flicker-free PWM, in the kilohertz range. Then they noticed that you can improve the motion handling capability of an LCD panel but flickering the backlight at the same frequency as the screen refresh. It's kind of like how a CRT's phosphors fade and thus flicker at the refresh rate. Turns out it stops LCDs blurring with motion too.
In practice most monitors do both. They use high frequency PWM to set brightness and then switch that on and off at a low frequency like 60Hz. This is what causes the annoying flicker, but hay, at least the crappy review sites can say motion reproduction is better than the competition.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC