Seriously cannot believe the PWM frequency is 240Hz. I was shocked out of my mind when I first saw that. It needs to be on the order of kHz to avoid eyestrain for a very significant proportion of the population. Did Apple just forget about accessibility, or did they underestimate it?
Slight aside. I was thinking of buying a Google Pixel 11 but I learned that they have the same problem. I will go into a store and see if the Pro version (which can do 480 Hz) is OK.
Even if I'm not sensitive I am wary of this, what if it causes subtle eye strain that has long-term consequences?
I'd be fascinated to see how common this really is. Is it something that affects .0001% of users, more, less? At Apple scale an issue like that could hit millions of people. Given the newness and expense of the product one would assume not that many OLED Macbook Pros have shipped. So it's surprising that this issue didn't come up in testing if we're talking about more than a handful of people.
PWM sensitivity has been an issue on the iPhone for a long time, but the prevailing wisdom is that it affects only a small percentage of users, and then only at certain lower brightness levels. Consider it like a food allergy, we don’t rearchitect the entire food supply for everyone around the sensitivities of a few.
That said, I have my doubts about prevailing wisdom being true here.
I'd be fascinated to know how many people Apple tested this on. 240Mhz is an absurdly low modulation frequency for an OLED. They are basically doing large scale field research without controls or consent.
It's hard to put a number on it (e.g. do people with eyesight problems or headaches actually know it's their display?) and it may also be influenced by other factors. I have used phones with 240Hz PWM dimming for years and haven't had an issue. However, I quickly get eyestrain when looking at e.g. a Samsung S26 Ultra. It's probably the combination of 240Hz PWM, FRC for emulating 10-bit on an 8-bit panel, and maybe the two types of pixels (narrow and wide, for the privacy display) that makes it painful for me.
I can also imagine that lower frequency PWM dimming can be more problematic on a display that covers a larger portion of your sight. Many people also probably use their laptop/computer screen for a longer time without looking away (aside from phone addicts).
A small aside: this is why I truly hate when people argue 'oh well, his only happens in 1% of cases, it's not worth supporting/solving'. With sufficient scale, and even without sufficient scale, it's thousands or even millions of people!
Agreed, that wasn't my point. I wasn't suggesting it's fine if it only affects a small number of people. More confused as to how it could slip through testing if it affects a substantial number - given how few units have likely shipped.
It's likely to impact far more than .0001% of users. I'd put it closer to 12% - roughly the same percentage of the population that suffers from migraines. Granted, the degree of which it impacts the person will vary, but if these displays earn the reputation of triggering them, migraine sufferers will steer clear.
This has been an issue for all Apple OLED displays since they came out. I bought the iPhone Mini when it came out but couldn't stand it because of the PWM on the display. I had to get an SE instead which used an LCD display.
I'm one of the ones who is very sensitive to this. I get occular migraines often. It has become fairly difficult to find displays that don't have these problems as everyone moves to PWM dimming on everything. Even lightbulbs are a difficult purchase for the same reason (at least Ikea makes some that have zero flicker and are cheap).
Apple is pretty bad at testing, they released the first Retina MBP with ghosting that remained for a minute or even more (I had one).
I use Apple products a lot, but one thing I learnt many many years ago, is never buy the first of anything new they do. Most of the time it will be fine, but when it’s not it’s just bad.
I'd love for more research to be made into PWM sensitivity, if only to find out roughly how many people experience problems with it.
I've never had issues with it other than when trying to film certain old displays, but then again, I've never had issues with PAL TV sets running at 50 hz interlaced, nor even old PC CRTs running at 60, which definitely was not 'flicker-free', so I'm probably on the far end of the spectrum compared to the PWM sensitive.
It's an easy thing to forget, as with many accessibility features. And it's going to suck to have the nominally best display be one you just can't use if want to not feel like gouging your eyes out.
I notice PWM all around me all the time. Lots of cheaper LED lights use it, and I see it whenever I move my eyes, also when not consciously looking for it - instead of a blur I see series of lamps as a brief afterimage.
As a child I got headaches from CRT monitors at 60hz and I could see them flicker. I haven't noticed the PWM on modern monitors, but maybe these Apple ones would trigger me?
I haven't taken notice of the brand, but I certainly have also noticed a few cars with horrible PWM. It really does look bad I think.
I miss how amusement parks looked at night when I was a kid, all bathed in warm, colorful glowing lights. They are still bathed in warm colorful lights, but half of them now have shitty PWM.
Usually tail lights are made up of a matrix of LEDs. They could dim them by only energizing a checkerboard pattern of half of the matrix (using flat DC, not PWM), then energizing the whole matrix when the brakes are applied. If the PWM duty cycle is less than 50% for some reason, then they could energize that portion of the matrix instead.
The most likely explanation I can find for slow PWM is that it's easier to comply with radio frequency interference rules, while no regulation discourages slow PWM and few customers care. A non-PWM driver would work, but it would cost ever so slightly more.
There probably should be a regulation about it because it has the potential to disorient other drivers.
I'm a little baffled that GM continues to do this even on later models. I can pick them out a long way away, at night especially. It makes their cars look cheap and possibly dangerous.
It's odd that I/we notice it more on their high-end nameplate (Cadillac), where they theoretically have more money to address these sorts of issues.
The cheap LEDs are not intentionally pulse-width modulated (at least not unless they’re dimmed, and dimming a cheap LED is asking for trouble).
They are deeply modulated at 2x the mains frequency because they use a very simple drive circuit that lights them up whenever the absolute value of the input voltage exceeds some threshold.
I am sensitive to PWM, but not CRT's (I have an old Sony CRT I use to play retro games). The reason is that CRT's do not turn the entire screen on/off like PWM does, they draw scanlines. This isn't nearly as bad as what PWM does. It's the on/off of the entire screen rapidly that is the issue.
In fact there is research being done in the retro gaming scene of using CRT-like scanline drawing to mimic what CRT's do for modern displays. This allows "blackframe like" insertion without the flicker. Only issue is you need a very high refresh rate display to take advantage of it and there aren't many of those.
I haven't been able to upgrade to oled displays since the first few generations practically tore out my eyes and gave me headaches. I'm still on VA or LED panels. Easy brightness, super gentle. Not the most accurate with color, but I can use them for a very long time and never come anywhere near the pain of a 15 minutes on an OLED phone in the dark.
> But some people are particularly sensitive to this kind of modulation and can experience eye strain, headaches and other forms of discomfort when looking at displays that use it.
So that tiny fraction of users would be well served with some other display and can either return their MacBook or use an external monitor if and when they find out that they're in that cohort.
I am shocked that Apple would release a screen with such a low PWM frequency. Here is a paper showing humans can perceive flicker at frequencies more than double their display’s rate: https://www.nature.com/articles/srep07861
The change in that study was dramatically different: they had half the screen black and half white and were flipping which side was which at that rate. Yes, most people could perceive that. The study included 10 participants, all in their 20s. They didn't ask about headaches other observed effects afterward.
The purpose of that study was to show that the traditional fusion frequency, which is in the range of 50 to 90 Hz for most people, is valid only for what it was initially measured, i.e. the threshold where a sequence of complete static images is perceived to consist of continuous movements.
But when some new display technology is based on showing various image fragments at moments shifted in time, expecting that the eye will integrate them over time to form complete images and continuous movements, that may require higher sampling frequencies, up to 10 times higher, due to the interaction with the fast subconscious eye movements.
The study results are not surprising at all, and this is an effect that should be kept in mind by anyone who designs displays.
It's not even about perception at all. For some (like me) it seems to be related to muscles in the eyes reacting all the time and fatiguing, it seems such muscles can react much faster than our "perception" of flicker, so something like a 10khz PWM driven display still causes fatigue, even though there's no way you can see it. People that get headaches are probably experiencing something different.
There are monitors that output 240 FPS. I don’t see how you can do PWM at that frequency. That would be one high per frame. It’s not even PEM at that point!
I am not particularly sensitive, but switching the ipad pro for the oled model, I just don’t like the screen that much, and it is hard to put the finger on why. Side by side, the screen has better blacks and peak brightness and I am sure it beats the LCD empirically on many metrics. But I don’t like the colors as much, and perhaps subconsciously, the flicker is turning me off.
If it’s as low as 240hz, anyone will see a stop motion effect by waving an open hand in front of the screen at 50% brightness.
I’m curious if this is a harmonic mode for a high speed PWM where pulses are either not even widths or the driver loses some power at the 240hz cycle. May perceive similarly.
I have a couple windows laptop workstations with high dpi OLEDs (one with 240hz refresh rate) that I love and don’t perceive this so I’ll have to check.
I have one of these laptops, I tried waving my hand in front of the screen at 50% brightness and I don't observe anything unusual.
I think I am pretty insensitive to this effect, though. Other than occasional seeing a bit of 60 Hz flicker out of the corner of my eye from Christmas lights, automotive LED tail lights, etc. I don't tend to notice flicker.
>Gripping any phone will result in some attenuation of its antenna performance with certain places being worse than others depending on the placement of the antennas. This is a fact of life for every wireless phone. If you ever experience this on your Phone 4, avoid gripping it in the lower left corner in a way that covers both sides of the black strip in the metal band, or simply use one of many available cases.
Reminds me of 'battery gate', which was another situation where what they said/did was actually reasonable, but haters had to spin it into something nefarious. Apple makes many missteps, but these are way overblown.
I was expecting to read this and learn that the display was reasonably engineered and that there is some small subset of people who have extreme PWM sensitivity who have problems. But no, Apple modulates at 240Hz, according to plenty of articles.
We’re no longer in the dark ages of flicker. There’s actual industry guidance: IEEE 1789. And 240Hz, at any respectable depth of modulation, does not meet the low-risk limit, let alone the no-observable-effect limit.
I am wondering whether this is actually just an amazing firmware goof: the reports seem to suggest that operating at full brightness mitigates the problem, which makes little sense for an OLED display. An OLED showing 50% (post-gamma) gray ought to drive the pixels the same way as an OLED at 50% brightness showing white. And this display supports HDR, so even 100% brightness white isn’t really 100%.
I’m wondering if a little engineering mistake snuck in: some (most?) LCD displays dim by PWM-dimming the backlight, and plenty of backlights have current-to-light transfer functions that inherently low-pass filter the light. If someone naively ported the same logic to an OLED (which doesn’t have a backlight), they might have implemented brightness controls by applying a 240Hz envelope to the pixel excitation waveform. This makes no sense at all as an actual implementation, but I can totally see an AI doing it and writing tests to validate it :)
Even if there is a genuine engineering factor that requires low frequency PWM, I bet Apple could mostly mitigate the problem by deliberately mismatching the phases. For decades, pre-LED stadium lights had rather extreme flicker at 120Hz, but it was tolerable because the overall system was engineered to roughly evenly split the lights between three electrical phases, giving an effective modulation depth near zero.
I haven’t seen one of these displays myself. I find 120Hz flicker to be extremely obvious and very very unpleasant, and if these displays really do modulate in a nasty way at 240Hz, I expect I’ll be able to see it, albeit rather less obviously than at 120Hz. Also, pretty much any modern phone can see this in slo-mo video mode :)
Wait... so operating at 100% brightness mitigates this? I bought this mac and have been reading about this. Stare at computer 15+ hours a day coding, but I also never use anything less than 100% brightness.
PWM is usually only used for dimming. So at 100% brightness there is no PWM being used. I'm not sure how this apple monitor works, but that's the basic gist for most screens that use PWM for dimming.
But the monitor specs show 1000 nits sustained and twice that as the peak, so that means that some PWM is required at 100% brightness, or peak brightness is somehow "over-driving" the panel?
If it’s the “hybrid” design I mentioned later in the thread, then it could be that normal white is simply driving less than maximum current through the pixel regardless of the envelope duty cycle.
If you have a modern-ish phone to go with that Mac, try taking a slo-mo video of your screen (preferably with content with decent sized patches of something other than black or dark gray) at different brightness settings. Maybe even make a big gradient and display that at various brightness settings.
I believe this is the limit of the panel controller. The panel of the macbook is pretty high resolution, that means they need to scan really fast to reach the require refresh rate(120hz), then they have to scan even faster to do "pwm". The controller has to scan really, really fast.
This is one of the worst articles in terms of information per word density! Too many words and so much beating around the bush before it even discusses what the heck it's talking about.
When I actually went to the source for the 240hz claim, I didn’t reach the same conclusion as the testers?
Maybe they just let their rigol scope spit out 240hz, but 480hz worst case and I would actually say 960hz. I think what’s happening with the tandem oled is they both pwm at 480hz and 180 degrees out of phase giving effective 960hz when both are in use. Which appears to be most of the usable brightness.
Edit: I’m so confused.
“The PWM behavior is interesting, because we can see DC-dimming for all brightness levels. Usually, OLED panels use DC-Dimming only at higher brightness levels. The frequency is very low at 240 Hz, however, and this might be an issue for sensitive users, despite the DC-dimming. ”
https://www.notebookcheck.net/Amazing-OLED-panel-Apple-MacBo...
You’re right - looking at the scope pictures, the horizontal period of the grid is 2ms, and the period of the wave is just over that.
A 240Hz wave would have a period of 4.17ms. 480Hz is 2.08ms. Much closer to the oscilloscope waveforms. And even then the waveforms are periodic, with smaller troughs at every second dip.
I wish I could see their test setup. It would be ironic if the panel was fully DC dimmed and the troughs were from another light source or something…
I’m not sure why the scope is saying 240 though. It makes me doubt my understanding :-/.
[Edit: Ah - got it! It’s measuring the frequency of the very lowest points - the ‘every second dip’]
The difficulty here is that it's 480Hz top-to-top, but there are two definitions of dip-to-dip depending on if you count every 'dip' from 100% (480Hz), or just the ones that reach the lowest voltage ⃰ (240Hz).
⃰ ⃰(brightness - presumably the test setup is an LDR or something?)
Here's my hypothesis: I'm guessing that the reviewer's is using some kind of photodetector is sensitive, to different extents, to different portions of the scree. And that the actual display modulates at 240Hz but that some portions of the screen are 180 degrees out of phase with other portions. Or that one of the subpixel colors is out of phase with the others. This could explain the weird alternating-depth signal at ~2ms intervals.
That doesn't look like it's not even close to being able to focus on a single subpixel or even a single row without additional optics.
In any case, the 0% and 25% waveforms look pretty bad. In my experience, light with sharp, short pulses (like "driverless" LED lights produce) are unpleasant, but the unpleasantness is related to how bright the source is compared to everything else in the field of view. (The 0% and 25% waveforms are solidly at twice the frequency of driverless LEDs, which will make the effect considerably less bad.)
Older samsung galaxy phones (till ~S21) had HW 960fps mode where it recorded 0.2s on sensor before switching back to normal fps. It is not macro, but maybe it could show the flicker rate of the whole screen or halves out of phase.
> Or every second time a particular value is reached.
The value is waving, so a complete cycle is when it got back to where it started: that is, not just its value but its _direction of change_ is also the same.
(A value waving in 3D could coincide with its start value multiple times before it completes a whole cycle.)
> [Edit: Ah - got it! It’s measuring the frequency of the very lowest points - the ‘every second dip’]
So that's the danger of [the authors] just reading the number off the screen without understanding what the scope is showing.
To measure frequency, typically the scope will measure the max and min of a waveform, then select a point halfway between them as the trigger point, then measure the time between successive triggers. Also, the trigger usually has an intentional hysteresis, so that noise near the midpoint does not cause multiple triggers on a slowly-rising waveform.
The little dips don't go down far enough below the midpoint to activate the hysteresis window, which is why it only counts every second dip.
In this case that's not necessarily incorrect, though. With the pulses alternating in amplitude by that much, there will be a component of the brightness variation which is at 240Hz and still visible (if the pulses were more closely matched, then it would be fainter). You don't need the trigger to measure this frequency in a single shot, either.
(The waveform looks more than a little odd, to me. Like they say, the DC value is changing as well, so the circuitry should be able to just output a flat value. The pulses don't really look like typical PWM, either. So I don't really know what exactly is going on there)
Their method is a photo detector driving the oscilloscope, right?
How can they assume the rise/fall slope in those plots is characterizing the driving electrical signal? Wouldn't a PWM driver be able to have much faster transitions and look more square than that at these time scales?
It makes me wonder if this is the response of the organic phosphors and the difference in apparent "depth" of the dip is really just a difference of duration, since the dips are very V-shaped, rather than bottoming out.
It is slightly odd that it has this paired rhythm, but I don't think you can assume it is "DC-dimming" rather than just PWM quanta that are being anti-alias filtered by the phosphors and measurement methodology.
240 Hz looks correct to me. Of course it also has 480 Hz and other even higher components but the lowest significant component is 240 Hz. You can't disregard that half of the dips are much deeper. That will create a lower frequency flickering.
The authors are correct. The signal repeats every 4.2 ms, so the fundamental frequency is unambiguously 240 Hz. There is an even stronger second-harmonic component at 480 Hz, but this doesn't erase the 240 Hz flicker.
Hey, Rigol is dependable ;) - What do you mean in tandem? I thought oled doesn't use a backlight (I have little to no knowledge about displays). If it did, you would probably see a difference in amplitude depending on the diode you are using.
At least they probably measured with some form of photo diode instead of poking their osci into their mac trying to find the correct signal. This would measure the effective frequency for the eyes, no? So it would be 240Hz.
As someone who’s had a concussion, this is really interesting. For me this is how any screen was to me, not just bright OLED ones. Even more interestingly it’s essentially only screens— backlist posters at the mall (paper with a backlight) still affect it but less so. To me perhaps it’s focusing on something on a screen that does this, but it’s really interesting to see this affect the general population.
It’s also odd to think about lack of ability to concentrate, and I wonder if screens cause this optically somehow but to a less noticeable degree even when less intense than this new one? (Independent distracting contents)
I noticed that adding a severe red filter to all my screens helped me significantly with the concussion and am also curious about that, would that impact the intensity of a refresh perhaps? Is blue light specifically the problem? I’m unsure but have a plethora of subjective experience.
I’m glad for this to enter public consciousness a bit and would love to see more research on the screen itself impacting our brain.
curious; do you mean like a red plastic see-thru filter applied on top of the screen (filtering the backlight too, like those screen protectors), or a software screen effect that makes everything on screen appear red (which on an OLED screen would probably be the same thing)?
red/blue/green detectors (cones) in our eyes use different paths and have different "refresh rates" than luminous intensity sensors (rods), im wondering if filtering to a single color makes the rods take over for visual pattern processing
I met the diagnostic criteria for a concussion and went to the ER only to be told that I didn't have one because I was wearing a helmet when the accident in question happened. Me feeling funny and having missing memories apparently didn't matter. They charged me $800 for the privilege of having my blood pressure taken and receiving some WebMD print-outs about banging one's head.
I guess next time I have one I'll just skip the doctor and hope I don't die or whatever.
I had to return the Steam Deck OLED and LCD because their displays PWM was burning my eyes out. Sore eyes for days, having problems to focus properly. I hope this is a learning process and it will get better from the manufacturer side. But I hoped that after my personal Steam Deck fiasco as well.
PC gamer here. I love my OLED tv but will never use one as a gaming monitor. They just suck at it.
In a year you will get normal Apple users start showing us burn in on their Macs, and its not going to be a good look for Apple. I guess this is why they made the full lid of the laptop much easier to replace in this generation, they are going to need that when people start wanting their burn in fixed in a year or so.
LCD most certainly has color degradation. About 8 or 9 years ago I was able to compare a almost brand new surface pro 5 to my 3 year old one. I was shaken by the difference in difference.
Don't forget the OLED stutter on slow moving scenes because of sample-and-hold. It's why motion interpolation (soap opera effect) exists. I can't watch OLEDs because of it. Looks horrible.
The soap opera effect has nothing to do with OLEDS.
It is to do with higher framerates on movies than we are used to, making movies look like cheaper filmed tv shows. Not a specific display technology working differently.
Peter Jackson famously had this issue when trying to show The Hobbit in 48fps, and that was in projectors in theaters.
Notice on the wikipedia page for 'Soap Opera Effect' it doesn't mention the term OLED once.
The shell is 1:1 to a mbp. I predict the following things will happen.
Water damage- folks using their semi dry hands to touch the screen- that water is going to drip straight down to the logic board!
Injury- those sharp corners at the top of the keyboard are just waiting for a power user to swipe.
Screen separation. Touch screens were made with durability in mind- the hinge on the touchscreen mbp is identical in range to the stock mbp. Can’t wait till gen 2
I'm glad that this is bringing attention to flicker sensitivity.
Here are some other things that people are sensitive to:
- CRI on white LEDs (and flourencents).
CRI is how clean the spectrum is in comparison to the sun or a incandescent bulb, where the specturm is completely even.
- Motion blur
Motion blur on LCDs (such as ~50% of Nintendo Switch 2s) can hurt eyes trying to keep track of what is going on.
On the other end is motion stutter on OLEDs. Because of sample-and-hold, the blur goes away but the image stutters on slow moving scenes instead. If your eyes are sensitive to PWM (mine are) it's quite annoying to watch OLED movement as well.
Is that what I'm seeing on my LG C series? Every so often when I'm watching streaming video, and the scene changes, the action seems to skip frames for maybe a quarter of a second. It happens rarely enough that I haven't narrowed it down to the TV, the attached Chromecast, the streaming app, or the content.
The only setting I recall changing on the TV is the one that stops the soap-opera effect.
I think you're seeing telecine judder. The video's framerate doesn't find the diplay's refresh rate, and the TV doesn't handle it well. This is why my old Pioreer Kuro switched to 48hz on 24fps content, and it was amazing.
Objectively speaking high fps is a better representation of motion. As a gamer I got used to high framerate content very quickly. I recommend biting the bullet, getting over the soap opera connotation, and enjoying all your screen has to offer.
Not it hurts to watch the judder of 30fps camera pans.
+1 on the attention. There are probably so many humans around the world (I'd estimate in the millions easily, assuming this affects even 1% of the population) who get eye strain and headaches from their oled devices (or even "modern" LEDs! Brake lights are terrible!) but never realize the cause.
Btw for anyone wondering, recent "Chinese" phones appear to do a damn good job. I have a recent BBK device, and I run eye comfort mode on 24/7, and despite being hyper sensitive to pwm (my previous oled phone was bad), this is quite comfortable.
When I was a kid I learned that the CRT screen refresh rate must be set to at least 60Hz otherwise it looks like crap and is pain to look at. My cousin had his set to some lower value and would claim not so see any issue. His father said "I don't know how these damn kids stare all day long at the screen, I stare half an hour and I get a headache!" because you're one setting away from not having the headache but you won't let me change it because reasons.
My parents have a plasma TV and I can clearly see it flicker, although it doesn't cause any pain.
Same for the 8514/A - which, although it was released a couple of years earlier, formed the basis for most "SuperVGA"-style clones.
In the first half of the 90s, pretty much every ISA graphics card had a 1024x768 @ 43i mode, and fancier ones could often do 1280x1024 at the same refresh rate (often accompanied by an ear-splitting whine coming from the monitor!)
This situation lasted until programmable PLLs that could do 72p began to take over in the mid 90s, swiftly followed by 90p. But by then the idea that anything above 800x600 was a recipe for eye-strain had been baked into the lore, and corporate IT departments in particular refused to risk going beyond it until well into the LCD era.
Back when desktop PCs were more common things to find in livingrooms, I improved so many lives by increasing the refresh rate of the monitor.
Sometimes, people didn't notice the issue and wondered why I was so motivated to fix a thing that they didn't perceive, but they noticed a positive improvement 100% of the time I spent a few minutes finding a good refresh rate and adjusting the geometry.
---
That said: Phosphor persistence varied, and therefore so did the the impact of refresh rates. So even though I was tuned into the thing, I never noticed any issues at all when working with a DEC VT330 terminal; the image was not flickery at all despite its 60Hz refresh rate. It accomplished this by using phosphors of relatively long persistence.
There was some ghosting evident on rapidly-scrolling text, but it worked well-enough for its normal intended uses.
Same with the Samsung CGA monitor I had back in the day. It's not like I could adjust its 60Hz refresh rate, but it was fine.
Things were far worse at 60Hz on the SVGA ViewSonic 5e that replaced the CGA kit. I spent a fair bit of time dialing out the 60Hz graphics modes in MS-DOS. (Text was always OK: VGA text mode is 70Hz.)
OLED doesn't bother me much (I'm fine with iPhone's OLED screen even at 60FPS mode), but my eyes hate low CRI, flickery LEDs.
Bottom of the barrel, eye searing cool white LEDs with bad CRI and flicker control makes my life really harder. Low quality florescent bulbs also create eye strain for me.
The best solution I have found is 90CRI, dimmable Philips LED bulbs. They grow warmer as you dim them, and they create a very comfortable environment for me. Also, a big Bauhaus branch in my city uses mixed temperature LEDs to tune resulting color and temperature. Since ceilings are so high, you don't see the lamps and feels like you're walking under sunlight. It's that good, kudos to them.
Brake lights could be terrible but headlights are much worse because they are always on at night, they got brighter and are pointed to cars coming into the other direction. Furthermore for some reason it seems that newer cars point their lights almost horizontally. It's as bad also when a car is following me. I never switched my mirror in the low reflection position as often as in the last few years.
Brake lights and headlights are ridiculous. They look like blinking long trails if your eyes move at all. How was this never picked up before LED came to market in cars
I am pretty sure incandescent lights don't strobe like that because the filament takes some time to stop glowing. I don't know for sure, though, and I've never seen high speed footage of them to know how dim they get.
It doesn't help that, for possibly aerodynamic reasons, headlights on new cars have become "squinty" instead of the large lenses they used to have, which concentrates the intensity at a small point instead of a more diffuse area. The driver sees the same amount of light, but oncoming traffic sees far more intense and distracting points than the soft glowing blobs they used to be.
I was driving this weekend in the dark, and there was a car parked with hazard warning lights on which are animated strips. So it went from not lit at all to everything on with such intensity that we couldn't make out the make/model of car, but the worst part was we couldnt see anything around it. I ended up driving about 5km/h past it just in case.
> Furthermore for some reason it seems that newer cars point their lights almost horizontally.
Over the years cars have become taller.
My first car (2000) was 1385mm tall, while its successor (2015) was 1475mm - 9cm difference despite the latter being essentially the same model as the former (in e.g. Australia they were both called Corollas).
Also more people than ever drive SUVs, with lights really high up.
I didn't originally get rid of my first car before getting the next and the difference in driving experience was huge.
Agreed. A couple years ago I got a fancy 4k LG OLED monitor (32GS95UE-B, with the improved subpixel layout), and had to return it two days later. My eyes were literally red from strain, which is how I learned I'm likely PWM flicker sensitive (and that too has only a slight 240hz flicker according to rtings).
Now I go purely for IPS and make sure it's DC-dimmed. I'm really glad the new MBP screens are an extra and not the new default yet.
Odd. A traditional 35mm cinema projector produces much deeper brightness modulation at a much lower frequency. Were you ever affected by film projection?
Haven’t noticed, though I rarely go to the cinema.
It’s worth noting though that for the monitor it may be used 10+ hours a day, while watching a movie is a one-time two hours - this is also why I don’t mind my oled tv being tiring to my eyes. I do feel it after prolonged sessions, but I don’t use it nearly enough for it to matter.
This happened to me with the exact same monitor model! I generally don’t have issues with OLED screens so I still don’t know what made that particular monitor so evil. I’m not convinced it was completely caused by the PWM, I think it might be related to the matte coating and text fringe combined with the PWM being the cherry on top.
I switched to a MiniLED screen and it all went away. I even tried to keep the monitor for gaming but I can’t last more than half an hour.
Also flicker on bad LED lighting. A lot of bad LED lighting flickers at ~60Hz. In rooms lit by that, you can wave your hand or a thin object back and forth, and if you look carefully, you can perceive a "shutter" effect where you're only seeing the snapshots of its position where the light is on.
The thing that makes that so insidious is that not everybody can easily perceive that.
(The reason why such flicker is common in cheap LED bulbs: they turn AC into DC using a half-wave rectifier, which just chops off half the AC wave. This is also why you can still see the effect in rooms lit by multiple lights, because the flicker is in sync, synchronized to the incoming AC.)
If you are building a space for other people and you are responsible for the lighting, please check for this. If you can't perceive it yourself, find someone who can.
The power supply is the weak point in LED room lighting. The best power supply for LEDs is switch-mode PWM, high frequency, and with thermal management designed by an engineer who understands therodynamics.
Unfortunately all those things are expensive so you rarely find such bulbs in the cheap bin at Home Depot.
Bulbs are actually a very bad form factor for LEDs, because they concentrate two heat-generating components - the PSU and LEDs - into a small chassis. LED tape with a separate power supply is probably the best solution that's not a full-custom DC light fixture.
Except bulbs have interfaces that are universal within any given political area. The bulbs are standard. The sockets are standard. They're cheap to buy. They're easy to replace. ~Anyone can do the work.
When a component of a fixture that separates the PSU and driving electronics from the LED fails, things are much harder to deal with than just replacing a light bulb.
(I can open up an LED driver and replace a capacitor, or troubleshoot a failed LED board, but I still don't want to. I prefer to spend my time in other ways.)
This is a great point. What mitigates it is that with a properly designed power supply that doesn't cook the diodes, LEDs last 30,000 hours. Which is 27 years if we assume the lights are used 3 hours per day. So it might not be necessary to replace the LEDs more than once or twice over the life of the house.
With a bulb, you're replacing both the PSU and LEDs together. Why the aversion to doing that with a non-bulb fixture?
I agree that throwing away a whole fixture (diffuser and all) because of compoment failure is wasteful, but I think LED tape is actually better than bulbs here: You can independently swap the PSU, the LEDs, and the mechanical parts.
Mind you, LED tape is pretty inefficient due to using standard voltages and then balancing current with resistors, but it's probably worth the repairability tradeoff for most.
> With a bulb, you're replacing both the PSU and LEDs together. Why the aversion to doing that with a non-bulb fixture?
There is no standard interface for the latter.
(Have you seen how poorly some folks mount things and splice wires/connect terminals? I have. Most idiots can manage to screw in a light bulb, though.)
It's very unfortunate that our electric codes are based primarily on incandescent lighting. If we were designing electricity from scratch, we'd probably be set up with 240v 3 phase AC for big loads (ovens, heaters etc) and 48v DC for lighting and most electronics. Requiring every device to have its own rectifier is a lot less efficient than putting a single good rectifier in a central location.
Manufacturers are selling DC bulb systems these days. Unfortunately, the ones I've seen sell the accompanying rectifiers (which need maybe $50-100 of power electronics inside) for multiple thousands of dollars, and they're DRM locked to the more expensive bulbs by proprietary protocols.
I find the inefficiencies of the old system more manageable.
DC doesn't buy you that much for electronics. You still need to do DC-DC conversion to 12V or 5/3V for the electronics itself.
And to avoid ground loops, you also need fully isolated DC-DC converters. So you end up with the same power supply architecture as for AC-DC, saving only on buffer capacitors.
As an experiment, I converted my homelab to 48V DC to operate from the battery directly after my attempts at making a UPS failed. It works, but it's barely more efficient than doing a double-conversion.
I'm now redoing lighting in my house, and _there_ the DC power makes a lot of sense. I'm planning to use commercial-grade DALI, with tunable white setpoint. It uses true DC dimming, so there's no flicker whatsoever.
> Requiring every device to have its own rectifier is a lot less efficient than putting a single good rectifier in a central location.
Is it, though?
You'd have to deal with additional wiring losses due to the lower voltage between the central rectifier and the devices, and the various individual devices would still need their own step-down converters to turn that 48VDC into something they can actually use.
On top of that: the central rectifier would have to be sized for peak load, while in reality the vast majority of the time it would be running at only a fraction of that. That's not exactly ideal for efficient operation. Individual power supplies can be designed specifically for a single device and operate at its sweet spot most of the time.
> You'd have to deal with additional wiring losses due to the lower voltage between the central rectifier and the devices
No. Everybody always complains about voltage drop. It's not a problem with LED lighting loads because they use so much less power. Let me prove it to you.
Assume we use the same 14-gauge copper Romex for our 48VDC lighting circuit that is already inside most home walls in the USA.
DC resistance of 14-gauge copper wire: 0.002525 ohms per foot.
Voltage drop over a circuit:
Current x Ohms/foot x Two-way distance
--------------------------------------
Nominal Voltage
Assume we're driving a 13-watt LED bulb (typical 100W incandescent equivalent) that is 50 feet from the supply.
Current would be 13w/48v = 270mA.
.270A x 0.002525Ohms/foot x 100feet
-----------------------------------
48v
= 0.00142V
So the voltage drop is 0.14%. Any voltage drop less than 3% is considered
acceptable by NEC.
Oh, but what if I want to run more than one bulb? Fine, let's do 10
bulbs on the same 14-gauge supply wire. Now the voltage drop is 1.4%. Still less than half the maximum limit.
And this is 14-gauge wire. What about 12-gauge? Well, that's 0.001588 ohms/foot.
.270 x 0.001588 x 100
---------------------
48
Now for 10 bulbs the voltage drop is eight tenths of a percent.
Running LED room lighting in a standard American house at 48VDC on the 14-gauge wire that's already in the walls is completely doable.
Yes, we still need constant-current supplies in or near the bulbs, and those are not 100% efficient. Keep in mind also that some of that 13 watts we assumed above is for typical Home Depot 120VAC bulbs that have builtin rectifiers and [probably] crappy power supplies, so the waste power used by the constant-current supplies I'm talking about here -- which are simpler than the supplies used in Home Depot bulbs -- is probably less.
Fine. So we've got serious 3-phase for big loads, and 48VDC for everything else.
Which circuit does the blender connect to, or the kettle? The air fryer? The coffee machine?
How do I power a space heater to warm up a chilly room for the baby on a particularly cold and windy night?
Where does the window air conditioner connect that I need because my landlord is cheap and there's an intolerable heatwave?
The audio system? The guitar amp? The gaming rig? The vacuum cleaner?
I guess we plug that stuff into 3-phase outlets, which we'll need to have everywhere -- right? Fine.
---
So we've got other stuff, too, that's a little lighter. Phones, laptops. Lights. Stuff. That can all be made to convert 48VDC down to whatever it needs internally, but that conversion requires electronics that are local to the device. We haven't eliminated that at all.
But sure: It runs on 48VDC that is sourced from some manner of manner of central power supply. Neat, I guess?
---
But why?
It sounds like all we've really accomplished here is adding more wires, and more complexity.
I'm struggling to figure out how any of this is presents any meaningful advantage.
(Oh, I know! Let's keep our existing single-phase circuits, and add both 3-phase AC and 48VDC! Whooo boy! Now we've got a real clustefuck cookin'!)
> Which circuit does the blender connect to, or the kettle? The air fryer? The coffee machine?
3-phase.
> How do I power a space heater to warm up a chilly room for the baby on a particularly cold and windy night?
3-phase, and it's not obvious why you need the additional extraneous detail to explain why you want a space heater.
> Where does the window air conditioner connect that I need because my landlord is cheap and there's an intolerable heatwave?
3-phase, and again, it's not obvious why you need the additional extraneous detail.
> The audio system? The guitar amp?
DC, and DC.
> The gaming rig?
DC or 3-phase, depends on how much power it needs. Worth noting that some PC power supplies already draw more power than most 120V circuits should be carrying. (1500W is the commonly cited limit, and there are gaming rigs with larger power supplies than that.)
> The vacuum cleaner?
Depends on how much power it needs, and whether it's recharging a battery or running a powerful motor directly.
DC mains, even at low voltage (which also means a higher current capability for the same amount of power, and thus thicker cables and/or higher resistive loss), is more dangerous than AC because it doesn't stop flowing; AC goes to 0 twice a cycle, so arcs have a chance to extinguish. DC switchgear needs special provisions for breaking arcs, such as "blowout coils".
Some early electrical installations, as in late 19th/early 20th century, used DC. Most have disappeared, with the exception of some surviving early elevators and perhaps some huge industrial motors, converted to running from a rectifier.
> Some early electrical installations, as in late 19th/early 20th century, used DC. Most have disappeared, with the exception of some surviving early elevators and perhaps some huge industrial motors, converted to running from a rectifier.
... and vehicles. DC is still very common in mobile installations.
> If you can't perceive it yourself, find someone who can.
Or just use your phone’s slo-mo feature to take a 240 FPS video (which then gets played back at 30 FPS). 60 Hz flicker becomes extremely visible. More than once I’ve noticed the strobe effect and then confirmed it this way.
60Hz flicker is rare. Most cheap/driverless LEDs are full-wave rectified or at least alternate half-wave pixels and thus flicker at twice the mains frequency, giving 120Hz in the US.
Even many expensive LEDs seem to have some sort of flicker, I can only guess that they're cheaping out on some capacitor and enough of the rectification ripple leaks through. We had the technology for high frequency output in ballasts with CFLs, if they can do that then surely non-flickering LED bulbs should be a solved issue
There are four general categories of LED luminaire:
- Driverless, common as 120V chip-on-board light sources and as 120V strips. These are basically made out of diodes and resistors. They are awful. There are advanced designs that are slightly less awful.
- Self-contained devices with little driver ICs. You’ll find these in screw-in lamps and some integrated fixtures. They range from surprisingly good to awful, both in terms of flicker and dining performance. They have hazardous voltages inside (no isolation), so they’re essentially always supplied as a unit with 120V input. There are also 12VAC devices like this.
- Constant current light source (typically a few hundred mA at a voltage around 15-56V). The light source may be literally just an LED. The driver will be remote, possibly inside the same fixture, and the output may be NEC Class 2 or otherwise quite safe. These are the best, especially with a good driver. Flicker may be essentially zero.
- Constant voltage, usually in the form of tape, usually 24V but also seen as 12V and 48V. Sometimes there is a current limiting IC that gives equal brightness across a range of voltage. These are a bit less efficient than constant current devices. They can operate with no flicker at all at full brightness, and they can be PWM-dimmed. Trying to dim them by reducing voltage gives very inconsistent results.
The type of LED used has surprisingly little to do with how fancy or expensive a fixture is. Constant current drivers tend to show up only in fancier fixtures, but plenty of extremely expensive fixtures use awful light sources.
When I've had a coffee too much, I notice the 120 Hz flicker even more. But even when I'm tired and don't, my mood still noticeably increases when I leave flickery spaces. (I sometimes test my hunch with the slow-motion cam as I am leaving.)
I've tried looking for studies to prove or disprove my experience. They should be easy to find, right? Humanity is replacing the entire planet's lighting with LEDs after all! Comment sections have been busy with people arguing about PWM flicker for years, probably longer. What is the best study you can find? For me, it is always the one from 1989 about pre-LED 60 Hz office lighting (that said it had adverse effects). Seriously...?
I wish I was a Bitcoin billionaire, for many reasons, but doing another study on flickery LED lighting seems like the lowest-hanging fruit of our entire civilization. I live in a country that is regulated to hell and back, and yet even our street lights flicker visibly, not to mention classrooms, children's bedrooms, and the screens that people stare at for hours every day. I don't get it.
Not everybody can see this, but, if you want to help someone see PWM sources, choose a single color (e.g., red, largely in case the primaries are time separated), make a simple dot or line, and wave it around in the peripheral vision of your doubter.
Humans are very sensitive to flicker in peripheral vision. Have them look at something across the room and then blow their mind.
(Note: easier with a phone, but doable with a laptop.)
There are tools that will report the flicker level of lights. Or a basic test that often works is pointing your phone camera at a light, close up, sometimes will show the flicker, or using the slow-mo setting on the camera.
Americans being Americans. Most of the world operates on 50Hz electricity, which would result in a different flicker. Consequently, when travelling to another continent, it is worth checking camera settings and adjusting them to the local frequency.
Again: the USA is large, but other countries (usually with different systems) do exist.
Seconding these (the beefier of which do also, from time to time, reach unthinkably deep discounts in Bezosland—especially if you’re flexible on SKU and willing to stockpile).
Alongside Soraa if you’re doing something extra classy that needs to be perfect and bulletproof; and the “flicker-free” portion of Waveform Lighting’s range if you’re… price-insensitive in your domestic sphere.
A couple cautions from experience with the Phillips: most are fantastic and long-lived. But I’ve had batches with high rates of… we called it “cradle death,” I’m sure there’s a more sensitive term now… and they seem to get grumpy easily in enclosed/recessed fixtures and around water.
The failure mode: they go dim fairly suddenly, then they usually fail off and occasionally to a low tone with periodic bright strobe. Great lamps though, for the reasons we’re sensitive to around these parts!
These are what I buy, they are great. But I recommend checking locally first. In my area, at least, the government and/or power company subsidize LED bulbs so they're substantially cheaper if I buy locally instead of from Amazon.
Lucky, here in NZ you can't really get the old halogen lights anymore, and 90% of the LEDs sold here are trash.
And often these big brands like Philips don't sell there flicker free high CRI lights in NZ. (like the Philips LED light above. While yes I "can" buy it from Amazon US, but it's exceptionally expensive.)
Edit, I can't even order them from Amazon US, since the lights are for 120v power, and we have 240v.
Be aware that Philips changed their drivers to lower power-factor versions, if you care about electrical characteristics. I have tested similar models dropping from 0.95 to 0.75, or 0.99 to 0.85 or so.
I was building a lego set with my son several years ago and at some point (after the sun went down) realized I could no longer distinguish between the green and grey pieces, though it had been obvious under natural light. It was a striking demonstration of CRI.
I had this exact same experience with my son recently, although the most difficult part was distinguishing colours in the instructions. I now have a bunch of 72W halogen bulbs and I'm in the process of putting together heat-tolerant light fixtures.
Color rendering with LEDs is so terrible. And buying proper lights is either close to illegal (e.g. halogens) for efficiency reasons, or high quality LEDs are almost impossible to buy - "call us for quote" and similar nonsense.
The absolutely worst were the default indoor lights in Australia. There must have been some giant shipment of worst possible lights that they purchased to light up every bathroom in the country.
This world wide transition to cheap LEDs stole a lot of joy from the world.
Not in Switzerland. It gives me 1-2 german shops. Swiss retailers sometimes admit such products exist, but always out of stock.
And if you try to do some research and find high CRI lights that test well, those are pretty much impossible to buy.
Looking forward to the price going down and perhaps a good refurbished deal.
The only use case I can think of for this machine is testing iOS touch interactions without a physical phone. Just this one specific purpose and it's not one that would require prolonged use.
Most won’t use it. Steve Jobs was right, everyone is frisky at the beginning of the day and may use it a few times, but as the day goes on you’ll quickly get tired of it, particularly at the angle a standard laptop monitor sits at, and making a laptop with the screen sitting flat is utterly ridiculous.
It's not just cultists - millions of MacBook users want the lightest, longest lasting, best looking MacBook Pro they can get. For most of those people, this is that laptop, and touch is secondary.
If Apple had released this exact machine without touch it would still sell just as well.
i could not use OLED screen for programming and > 4h screen time a day. too much strain on the eyes. i have LG Gram laptop and it has really good IPS 2560x1600 panel with great color coverage. but it's hard to find a good laptop with IPS screen today as OLED is almost everywhere now.
I'm surprised by Apple putting out a laptop display with slow PWM. That's the kind of detail Apple has a reputation for paying attention to when other companies don't.
Apple in 2026 is just like any other manufacturer. They don't care about excellency anymore, the products just need to look good in ads and sell for a high price.
So that’s why Apple continued to offer 5K and 6K monitors which aren’t cheap, are and are the best you can get other than getting a professional production grade type monitor, which by the way cost a ton more, and most people can’t afford them.
The frequency is the frequency. If you have a problem with it, it’s your bad luck because the frequency over the years has been somewhere between 30hz and 120hz thru the years depending upon the use case.
PWM on LCD backlights usually doesn't flicker at all. It's smoothed to reduce the flicker to very low intensity. Which makes the frequency nearly irrelevant.
Apple still making some good products also doesn't disprove my statement.
I'm also absolutely still bitter that they broke the Display Stream Compression in DisplayPort 1.4 to do so, meaning any non-Apple monitor on the planet that worked perfectly in Catalina (like my 4K HDR @ 144Hz monitors) was nerfed.
"Apple worked a miracle, getting the bandwidth to drive a 6K monitor!" No, they just said "fuck you, standards". My monitors were neutered heavily (HDR @ 60Hz, SDR @ 95Hz), hell, downgrading the monitors reported capability to DP 1.2 improved resolution options, though not to where they should be.
Apple has been using low PWM screen for nearly a decade on iphone and ipad now. There’s just been limited demand to improve this in the market outside of china.
There’s also trade off to high pwm, usually worse color accuracy. But at least give us a toggle!
252 comments
[ 2.5 ms ] story [ 33.5 ms ] threadEven if I'm not sensitive I am wary of this, what if it causes subtle eye strain that has long-term consequences?
That said, I have my doubts about prevailing wisdom being true here.
I can also imagine that lower frequency PWM dimming can be more problematic on a display that covers a larger portion of your sight. Many people also probably use their laptop/computer screen for a longer time without looking away (aside from phone addicts).
I'm one of the ones who is very sensitive to this. I get occular migraines often. It has become fairly difficult to find displays that don't have these problems as everyone moves to PWM dimming on everything. Even lightbulbs are a difficult purchase for the same reason (at least Ikea makes some that have zero flicker and are cheap).
I also had one, for probably 6 years or so, and never experienced this.
I've never had issues with it other than when trying to film certain old displays, but then again, I've never had issues with PAL TV sets running at 50 hz interlaced, nor even old PC CRTs running at 60, which definitely was not 'flicker-free', so I'm probably on the far end of the spectrum compared to the PWM sensitive.
It's an easy thing to forget, as with many accessibility features. And it's going to suck to have the nominally best display be one you just can't use if want to not feel like gouging your eyes out.
1. CRT display phosphors had afterglow.
2. the cathode ray was a dot moving across the screen, that might be easier on eyes than whole OLED screen flashing at once.
As a child I got headaches from CRT monitors at 60hz and I could see them flicker. I haven't noticed the PWM on modern monitors, but maybe these Apple ones would trigger me?
I miss how amusement parks looked at night when I was a kid, all bathed in warm, colorful glowing lights. They are still bathed in warm colorful lights, but half of them now have shitty PWM.
Or they could raise their damn PWM frequency.
There probably should be a regulation about it because it has the potential to disorient other drivers.
It's odd that I/we notice it more on their high-end nameplate (Cadillac), where they theoretically have more money to address these sorts of issues.
They are deeply modulated at 2x the mains frequency because they use a very simple drive circuit that lights them up whenever the absolute value of the input voltage exceeds some threshold.
Increasing the refresh rate on my monitor was something I was happy to learn was possible.
In fact there is research being done in the retro gaming scene of using CRT-like scanline drawing to mimic what CRT's do for modern displays. This allows "blackframe like" insertion without the flicker. Only issue is you need a very high refresh rate display to take advantage of it and there aren't many of those.
Searching just gives me the same “PWM Sensitivity” webpages without any peer reviewed research.
So that tiny fraction of users would be well served with some other display and can either return their MacBook or use an external monitor if and when they find out that they're in that cohort.
But when some new display technology is based on showing various image fragments at moments shifted in time, expecting that the eye will integrate them over time to form complete images and continuous movements, that may require higher sampling frequencies, up to 10 times higher, due to the interaction with the fast subconscious eye movements.
The study results are not surprising at all, and this is an effect that should be kept in mind by anyone who designs displays.
I’m curious if this is a harmonic mode for a high speed PWM where pulses are either not even widths or the driver loses some power at the 240hz cycle. May perceive similarly.
I have a couple windows laptop workstations with high dpi OLEDs (one with 240hz refresh rate) that I love and don’t perceive this so I’ll have to check.
I think I am pretty insensitive to this effect, though. Other than occasional seeing a bit of 60 Hz flicker out of the corner of my eye from Christmas lights, automotive LED tail lights, etc. I don't tend to notice flicker.
If you want to use PWM in an application like this you need to start at like 600hz. This is how fast the subfield drive on a plasma TV is.
I have to use incandescent lightbulbs for certain fixtures because I sometimes need a break from engineers who think they are smarter than me.
>Gripping any phone will result in some attenuation of its antenna performance with certain places being worse than others depending on the placement of the antennas. This is a fact of life for every wireless phone. If you ever experience this on your Phone 4, avoid gripping it in the lower left corner in a way that covers both sides of the black strip in the metal band, or simply use one of many available cases.
tl;dr: you're holding it wrong.
https://www.wired.com/2010/06/iphone-4-holding-it-wrong/
We’re no longer in the dark ages of flicker. There’s actual industry guidance: IEEE 1789. And 240Hz, at any respectable depth of modulation, does not meet the low-risk limit, let alone the no-observable-effect limit.
I am wondering whether this is actually just an amazing firmware goof: the reports seem to suggest that operating at full brightness mitigates the problem, which makes little sense for an OLED display. An OLED showing 50% (post-gamma) gray ought to drive the pixels the same way as an OLED at 50% brightness showing white. And this display supports HDR, so even 100% brightness white isn’t really 100%.
I’m wondering if a little engineering mistake snuck in: some (most?) LCD displays dim by PWM-dimming the backlight, and plenty of backlights have current-to-light transfer functions that inherently low-pass filter the light. If someone naively ported the same logic to an OLED (which doesn’t have a backlight), they might have implemented brightness controls by applying a 240Hz envelope to the pixel excitation waveform. This makes no sense at all as an actual implementation, but I can totally see an AI doing it and writing tests to validate it :)
Even if there is a genuine engineering factor that requires low frequency PWM, I bet Apple could mostly mitigate the problem by deliberately mismatching the phases. For decades, pre-LED stadium lights had rather extreme flicker at 120Hz, but it was tolerable because the overall system was engineered to roughly evenly split the lights between three electrical phases, giving an effective modulation depth near zero.
I haven’t seen one of these displays myself. I find 120Hz flicker to be extremely obvious and very very unpleasant, and if these displays really do modulate in a nasty way at 240Hz, I expect I’ll be able to see it, albeit rather less obviously than at 120Hz. Also, pretty much any modern phone can see this in slo-mo video mode :)
https://www.imec-int.com/en/articles/displays-health-patches...
Apparently brightness consistency between pixels is poor at low drive current, so designers often use a separate PWM envelope to compensate.
And there are even papers studying the choice of frequency, e.g.:
https://pubmed.ncbi.nlm.nih.gov/41411543/
Unsurprisingly, 240Hz is not actually recommended (at least that’s what I get from the abstract, and I’m not about to pay to read the rest of it).
But we are still in the dark ages where industrial standards are not public.
> At 240Hz, the brightness fluctuation repeats 240 times per second; at 14,880Hz, it repeats almost 15,000 times per second.
Was that written for people who don't know what "Hz" means, or who don't know that 14880 is almost 15000?
clearly AIGC
Maybe they just let their rigol scope spit out 240hz, but 480hz worst case and I would actually say 960hz. I think what’s happening with the tandem oled is they both pwm at 480hz and 180 degrees out of phase giving effective 960hz when both are in use. Which appears to be most of the usable brightness.
Edit: I’m so confused.
“The PWM behavior is interesting, because we can see DC-dimming for all brightness levels. Usually, OLED panels use DC-Dimming only at higher brightness levels. The frequency is very low at 240 Hz, however, and this might be an issue for sensitive users, despite the DC-dimming. ” https://www.notebookcheck.net/Amazing-OLED-panel-Apple-MacBo...
A 240Hz wave would have a period of 4.17ms. 480Hz is 2.08ms. Much closer to the oscilloscope waveforms. And even then the waveforms are periodic, with smaller troughs at every second dip.
I wish I could see their test setup. It would be ironic if the panel was fully DC dimmed and the troughs were from another light source or something…
I’m not sure why the scope is saying 240 though. It makes me doubt my understanding :-/.
[Edit: Ah - got it! It’s measuring the frequency of the very lowest points - the ‘every second dip’]
⃰ ⃰(brightness - presumably the test setup is an LDR or something?)
Here's notebookcheck's review methodology:
https://www.notebookcheck.net/How-does-Notebookcheck-test-la...
And the sensor they use might be this one:
https://www.thorlabs.com/item/PDA100A2
That doesn't look like it's not even close to being able to focus on a single subpixel or even a single row without additional optics.
In any case, the 0% and 25% waveforms look pretty bad. In my experience, light with sharp, short pulses (like "driverless" LED lights produce) are unpleasant, but the unpleasantness is related to how bright the source is compared to everything else in the field of view. (The 0% and 25% waveforms are solidly at twice the frequency of driverless LEDs, which will make the effect considerably less bad.)
Surely someone on HN has the equipment and curiosity to double-check all this as a Sunday afternoon project?…
The value is waving, so a complete cycle is when it got back to where it started: that is, not just its value but its _direction of change_ is also the same.
(A value waving in 3D could coincide with its start value multiple times before it completes a whole cycle.)
To measure frequency, typically the scope will measure the max and min of a waveform, then select a point halfway between them as the trigger point, then measure the time between successive triggers. Also, the trigger usually has an intentional hysteresis, so that noise near the midpoint does not cause multiple triggers on a slowly-rising waveform.
The little dips don't go down far enough below the midpoint to activate the hysteresis window, which is why it only counts every second dip.
(The waveform looks more than a little odd, to me. Like they say, the DC value is changing as well, so the circuitry should be able to just output a flat value. The pulses don't really look like typical PWM, either. So I don't really know what exactly is going on there)
How can they assume the rise/fall slope in those plots is characterizing the driving electrical signal? Wouldn't a PWM driver be able to have much faster transitions and look more square than that at these time scales?
It makes me wonder if this is the response of the organic phosphors and the difference in apparent "depth" of the dip is really just a difference of duration, since the dips are very V-shaped, rather than bottoming out.
It is slightly odd that it has this paired rhythm, but I don't think you can assume it is "DC-dimming" rather than just PWM quanta that are being anti-alias filtered by the phosphors and measurement methodology.
At least they probably measured with some form of photo diode instead of poking their osci into their mac trying to find the correct signal. This would measure the effective frequency for the eyes, no? So it would be 240Hz.
It’s also odd to think about lack of ability to concentrate, and I wonder if screens cause this optically somehow but to a less noticeable degree even when less intense than this new one? (Independent distracting contents)
I noticed that adding a severe red filter to all my screens helped me significantly with the concussion and am also curious about that, would that impact the intensity of a refresh perhaps? Is blue light specifically the problem? I’m unsure but have a plethora of subjective experience.
I’m glad for this to enter public consciousness a bit and would love to see more research on the screen itself impacting our brain.
red/blue/green detectors (cones) in our eyes use different paths and have different "refresh rates" than luminous intensity sensors (rods), im wondering if filtering to a single color makes the rods take over for visual pattern processing
I am pretty sure an awful lot of people have suffered concussions and have never been diagnosed as such because they never went to ER.
I guess next time I have one I'll just skip the doctor and hope I don't die or whatever.
I had to return the Steam Deck OLED and LCD because their displays PWM was burning my eyes out. Sore eyes for days, having problems to focus properly. I hope this is a learning process and it will get better from the manufacturer side. But I hoped that after my personal Steam Deck fiasco as well.
https://www.youtube.com/watch?v=H43wnV-v7V0 Single OLED isn’t good enough long term. (Gamers will however claim it’s OK. 9 hours a day is 3285 hours in a year.
It is to do with higher framerates on movies than we are used to, making movies look like cheaper filmed tv shows. Not a specific display technology working differently.
Peter Jackson famously had this issue when trying to show The Hobbit in 48fps, and that was in projectors in theaters.
Notice on the wikipedia page for 'Soap Opera Effect' it doesn't mention the term OLED once.
https://en.wikipedia.org/wiki/Soap_opera_effect
https://en.wikipedia.org/wiki/Motion_interpolation
It caused by the frame rate, not the "how" of you got there. Cameras that record natively in 60 fps cause the same effect, without interpolation.
I have the original 5k Studio Display, and it's been worth every penny.
Not true!
I had a first-gen Dell 24" 4K monitor (P2415Q) since 2015 and by 2024 it had visible burn-in of the Windows task bar.
For example, could we overlay a software dimmer while driving the panel at max brightness?
Or would it be possible to tune PWM settings from the OS?
Or would this be possible to tune with a firmware change?
Idk how these things work.
Here are some other things that people are sensitive to: - CRI on white LEDs (and flourencents). CRI is how clean the spectrum is in comparison to the sun or a incandescent bulb, where the specturm is completely even.
- Motion blur Motion blur on LCDs (such as ~50% of Nintendo Switch 2s) can hurt eyes trying to keep track of what is going on.
The only setting I recall changing on the TV is the one that stops the soap-opera effect.
OLED sample-and-hold causes blur.
Not it hurts to watch the judder of 30fps camera pans.
Btw for anyone wondering, recent "Chinese" phones appear to do a damn good job. I have a recent BBK device, and I run eye comfort mode on 24/7, and despite being hyper sensitive to pwm (my previous oled phone was bad), this is quite comfortable.
My parents have a plasma TV and I can clearly see it flicker, although it doesn't cause any pain.
In the first half of the 90s, pretty much every ISA graphics card had a 1024x768 @ 43i mode, and fancier ones could often do 1280x1024 at the same refresh rate (often accompanied by an ear-splitting whine coming from the monitor!)
This situation lasted until programmable PLLs that could do 72p began to take over in the mid 90s, swiftly followed by 90p. But by then the idea that anything above 800x600 was a recipe for eye-strain had been baked into the lore, and corporate IT departments in particular refused to risk going beyond it until well into the LCD era.
Sometimes, people didn't notice the issue and wondered why I was so motivated to fix a thing that they didn't perceive, but they noticed a positive improvement 100% of the time I spent a few minutes finding a good refresh rate and adjusting the geometry.
---
That said: Phosphor persistence varied, and therefore so did the the impact of refresh rates. So even though I was tuned into the thing, I never noticed any issues at all when working with a DEC VT330 terminal; the image was not flickery at all despite its 60Hz refresh rate. It accomplished this by using phosphors of relatively long persistence.
There was some ghosting evident on rapidly-scrolling text, but it worked well-enough for its normal intended uses.
Same with the Samsung CGA monitor I had back in the day. It's not like I could adjust its 60Hz refresh rate, but it was fine.
Things were far worse at 60Hz on the SVGA ViewSonic 5e that replaced the CGA kit. I spent a fair bit of time dialing out the 60Hz graphics modes in MS-DOS. (Text was always OK: VGA text mode is 70Hz.)
Bottom of the barrel, eye searing cool white LEDs with bad CRI and flicker control makes my life really harder. Low quality florescent bulbs also create eye strain for me.
The best solution I have found is 90CRI, dimmable Philips LED bulbs. They grow warmer as you dim them, and they create a very comfortable environment for me. Also, a big Bauhaus branch in my city uses mixed temperature LEDs to tune resulting color and temperature. Since ceilings are so high, you don't see the lamps and feels like you're walking under sunlight. It's that good, kudos to them.
Over the years cars have become taller.
My first car (2000) was 1385mm tall, while its successor (2015) was 1475mm - 9cm difference despite the latter being essentially the same model as the former (in e.g. Australia they were both called Corollas).
Also more people than ever drive SUVs, with lights really high up.
I didn't originally get rid of my first car before getting the next and the difference in driving experience was huge.
Now I go purely for IPS and make sure it's DC-dimmed. I'm really glad the new MBP screens are an extra and not the new default yet.
It’s worth noting though that for the monitor it may be used 10+ hours a day, while watching a movie is a one-time two hours - this is also why I don’t mind my oled tv being tiring to my eyes. I do feel it after prolonged sessions, but I don’t use it nearly enough for it to matter.
I switched to a MiniLED screen and it all went away. I even tried to keep the monitor for gaming but I can’t last more than half an hour.
The thing that makes that so insidious is that not everybody can easily perceive that.
(The reason why such flicker is common in cheap LED bulbs: they turn AC into DC using a half-wave rectifier, which just chops off half the AC wave. This is also why you can still see the effect in rooms lit by multiple lights, because the flicker is in sync, synchronized to the incoming AC.)
If you are building a space for other people and you are responsible for the lighting, please check for this. If you can't perceive it yourself, find someone who can.
Unfortunately all those things are expensive so you rarely find such bulbs in the cheap bin at Home Depot.
When a component of a fixture that separates the PSU and driving electronics from the LED fails, things are much harder to deal with than just replacing a light bulb.
(I can open up an LED driver and replace a capacitor, or troubleshoot a failed LED board, but I still don't want to. I prefer to spend my time in other ways.)
I agree that throwing away a whole fixture (diffuser and all) because of compoment failure is wasteful, but I think LED tape is actually better than bulbs here: You can independently swap the PSU, the LEDs, and the mechanical parts.
Mind you, LED tape is pretty inefficient due to using standard voltages and then balancing current with resistors, but it's probably worth the repairability tradeoff for most.
There is no standard interface for the latter.
(Have you seen how poorly some folks mount things and splice wires/connect terminals? I have. Most idiots can manage to screw in a light bulb, though.)
I find the inefficiencies of the old system more manageable.
And to avoid ground loops, you also need fully isolated DC-DC converters. So you end up with the same power supply architecture as for AC-DC, saving only on buffer capacitors.
As an experiment, I converted my homelab to 48V DC to operate from the battery directly after my attempts at making a UPS failed. It works, but it's barely more efficient than doing a double-conversion.
I'm now redoing lighting in my house, and _there_ the DC power makes a lot of sense. I'm planning to use commercial-grade DALI, with tunable white setpoint. It uses true DC dimming, so there's no flicker whatsoever.
Is it, though?
You'd have to deal with additional wiring losses due to the lower voltage between the central rectifier and the devices, and the various individual devices would still need their own step-down converters to turn that 48VDC into something they can actually use.
On top of that: the central rectifier would have to be sized for peak load, while in reality the vast majority of the time it would be running at only a fraction of that. That's not exactly ideal for efficient operation. Individual power supplies can be designed specifically for a single device and operate at its sweet spot most of the time.
No. Everybody always complains about voltage drop. It's not a problem with LED lighting loads because they use so much less power. Let me prove it to you.
Assume we use the same 14-gauge copper Romex for our 48VDC lighting circuit that is already inside most home walls in the USA.
DC resistance of 14-gauge copper wire: 0.002525 ohms per foot.
Voltage drop over a circuit:
Assume we're driving a 13-watt LED bulb (typical 100W incandescent equivalent) that is 50 feet from the supply.Current would be 13w/48v = 270mA.
So the voltage drop is 0.14%. Any voltage drop less than 3% is considered acceptable by NEC.Oh, but what if I want to run more than one bulb? Fine, let's do 10 bulbs on the same 14-gauge supply wire. Now the voltage drop is 1.4%. Still less than half the maximum limit.
And this is 14-gauge wire. What about 12-gauge? Well, that's 0.001588 ohms/foot.
Now for 10 bulbs the voltage drop is eight tenths of a percent.Running LED room lighting in a standard American house at 48VDC on the 14-gauge wire that's already in the walls is completely doable.
Yes, we still need constant-current supplies in or near the bulbs, and those are not 100% efficient. Keep in mind also that some of that 13 watts we assumed above is for typical Home Depot 120VAC bulbs that have builtin rectifiers and [probably] crappy power supplies, so the waste power used by the constant-current supplies I'm talking about here -- which are simpler than the supplies used in Home Depot bulbs -- is probably less.
Which circuit does the blender connect to, or the kettle? The air fryer? The coffee machine?
How do I power a space heater to warm up a chilly room for the baby on a particularly cold and windy night?
Where does the window air conditioner connect that I need because my landlord is cheap and there's an intolerable heatwave?
The audio system? The guitar amp? The gaming rig? The vacuum cleaner?
I guess we plug that stuff into 3-phase outlets, which we'll need to have everywhere -- right? Fine.
---
So we've got other stuff, too, that's a little lighter. Phones, laptops. Lights. Stuff. That can all be made to convert 48VDC down to whatever it needs internally, but that conversion requires electronics that are local to the device. We haven't eliminated that at all.
But sure: It runs on 48VDC that is sourced from some manner of manner of central power supply. Neat, I guess?
---
But why?
It sounds like all we've really accomplished here is adding more wires, and more complexity.
I'm struggling to figure out how any of this is presents any meaningful advantage.
(Oh, I know! Let's keep our existing single-phase circuits, and add both 3-phase AC and 48VDC! Whooo boy! Now we've got a real clustefuck cookin'!)
3-phase.
> How do I power a space heater to warm up a chilly room for the baby on a particularly cold and windy night?
3-phase, and it's not obvious why you need the additional extraneous detail to explain why you want a space heater.
> Where does the window air conditioner connect that I need because my landlord is cheap and there's an intolerable heatwave?
3-phase, and again, it's not obvious why you need the additional extraneous detail.
> The audio system? The guitar amp?
DC, and DC.
> The gaming rig?
DC or 3-phase, depends on how much power it needs. Worth noting that some PC power supplies already draw more power than most 120V circuits should be carrying. (1500W is the commonly cited limit, and there are gaming rigs with larger power supplies than that.)
> The vacuum cleaner?
Depends on how much power it needs, and whether it's recharging a battery or running a powerful motor directly.
Because these discussions always come down to details, and I've found it beneficial to get them out of the way at the beginning.
> > The audio system? The guitar amp?
> DC, and DC.
Like here, for instance. No. Audio systems and guitar amps can be quite big.
> DC-to-DC can be substantially simpler and more efficient.
Except the whole system isn't DC-DC. There's still a central AC-DC component required.
This is already common. E.G. Computers currently do ac->12v dc (for in case transmission)->1vDC (for transistors). DC->DC is basically free.
Some early electrical installations, as in late 19th/early 20th century, used DC. Most have disappeared, with the exception of some surviving early elevators and perhaps some huge industrial motors, converted to running from a rectifier.
... and vehicles. DC is still very common in mobile installations.
Or just use your phone’s slo-mo feature to take a 240 FPS video (which then gets played back at 30 FPS). 60 Hz flicker becomes extremely visible. More than once I’ve noticed the strobe effect and then confirmed it this way.
- Driverless, common as 120V chip-on-board light sources and as 120V strips. These are basically made out of diodes and resistors. They are awful. There are advanced designs that are slightly less awful.
- Self-contained devices with little driver ICs. You’ll find these in screw-in lamps and some integrated fixtures. They range from surprisingly good to awful, both in terms of flicker and dining performance. They have hazardous voltages inside (no isolation), so they’re essentially always supplied as a unit with 120V input. There are also 12VAC devices like this.
- Constant current light source (typically a few hundred mA at a voltage around 15-56V). The light source may be literally just an LED. The driver will be remote, possibly inside the same fixture, and the output may be NEC Class 2 or otherwise quite safe. These are the best, especially with a good driver. Flicker may be essentially zero.
- Constant voltage, usually in the form of tape, usually 24V but also seen as 12V and 48V. Sometimes there is a current limiting IC that gives equal brightness across a range of voltage. These are a bit less efficient than constant current devices. They can operate with no flicker at all at full brightness, and they can be PWM-dimmed. Trying to dim them by reducing voltage gives very inconsistent results.
The type of LED used has surprisingly little to do with how fancy or expensive a fixture is. Constant current drivers tend to show up only in fancier fixtures, but plenty of extremely expensive fixtures use awful light sources.
I wish I was a Bitcoin billionaire, for many reasons, but doing another study on flickery LED lighting seems like the lowest-hanging fruit of our entire civilization. I live in a country that is regulated to hell and back, and yet even our street lights flicker visibly, not to mention classrooms, children's bedrooms, and the screens that people stare at for hours every day. I don't get it.
Humans are very sensitive to flicker in peripheral vision. Have them look at something across the room and then blow their mind.
(Note: easier with a phone, but doable with a laptop.)
Again: the USA is large, but other countries (usually with different systems) do exist.
PHILIPS LED A19 Ultra Definition Soft White Light Bulbs, 4-Pack 800 Lumen, 2700K, Dimmable, Flicker-Free, 60 W Equivalent, CRI95 True Colors, EyeComfort Technology
https://www.amazon.com/LED-Definition-Flicker-Free-Equivalen...
I also have some 75 W and 100 W equivalents, but they get pretty pricey, at least in Bezosland.
Alongside Soraa if you’re doing something extra classy that needs to be perfect and bulletproof; and the “flicker-free” portion of Waveform Lighting’s range if you’re… price-insensitive in your domestic sphere.
A couple cautions from experience with the Phillips: most are fantastic and long-lived. But I’ve had batches with high rates of… we called it “cradle death,” I’m sure there’s a more sensitive term now… and they seem to get grumpy easily in enclosed/recessed fixtures and around water.
The failure mode: they go dim fairly suddenly, then they usually fail off and occasionally to a low tone with periodic bright strobe. Great lamps though, for the reasons we’re sensitive to around these parts!
And often these big brands like Philips don't sell there flicker free high CRI lights in NZ. (like the Philips LED light above. While yes I "can" buy it from Amazon US, but it's exceptionally expensive.)
Edit, I can't even order them from Amazon US, since the lights are for 120v power, and we have 240v.
The joys of living on a fairly small island.
The absolutely worst were the default indoor lights in Australia. There must have been some giant shipment of worst possible lights that they purchased to light up every bathroom in the country.
This world wide transition to cheap LEDs stole a lot of joy from the world.
The only use case I can think of for this machine is testing iOS touch interactions without a physical phone. Just this one specific purpose and it's not one that would require prolonged use.
If Apple had released this exact machine without touch it would still sell just as well.
The frequency is the frequency. If you have a problem with it, it’s your bad luck because the frequency over the years has been somewhere between 30hz and 120hz thru the years depending upon the use case.
Apple still making some good products also doesn't disprove my statement.
I'm also absolutely still bitter that they broke the Display Stream Compression in DisplayPort 1.4 to do so, meaning any non-Apple monitor on the planet that worked perfectly in Catalina (like my 4K HDR @ 144Hz monitors) was nerfed.
"Apple worked a miracle, getting the bandwidth to drive a 6K monitor!" No, they just said "fuck you, standards". My monitors were neutered heavily (HDR @ 60Hz, SDR @ 95Hz), hell, downgrading the monitors reported capability to DP 1.2 improved resolution options, though not to where they should be.
There’s also trade off to high pwm, usually worse color accuracy. But at least give us a toggle!
https://discussions.apple.com/thread/1533218?sortBy=rank
https://www.wired.com/2007/05/apple-lcd-lawsu/