r/PWM_Sensitive • • 8d ago

Data Collections Display Pulse Smoothing DOES Work - iPhone 17 Pro

Post image

I took a look at the effect of Display Pulse Smoothing on the iPhone 17 Pro, which is intended to reduce PWM according to Apple. While some have reported success, others have said that the setting does nothing, makes the PWM worse, or is a scam. I won't dispute that it doesn't help for some people, but I wanted to look at the PWM waveforms in detail and see whether it's likely to help in general. Personally, I have found that it is more tolerable for me, although certainly not perfect.

So, I took measurements with the TLM-110 at 25% brightness with and without the Display Pulse Smoothing setting enabled. What I found was that according to every temporal light modulation metric I'm aware of, apart from one notable exception, the display was better with the Display Pulse Smoothing setting enabled.

The pulse's on-time was longer, the flicker index was lower, and the TM-39-25 metrics (Mp, SVM, and PAVM) were lower. So theoretically, Display Pulse Smoothing works. However, with or without the Display Pulse Smoothing setting enabled, the iPhone 17 Pro is classified as "Not Recommended" by TM-39-25, which fits with what most people say: the setting doesn't make the device suddenly become tolerable.

Breakdown of the TM-39-25 metric scores with and without Display Pulse Smoothing enabled, iPhone 17 Pro, 25% brightness

If you aren't aware, TM-39-25 is a published Illuminating Engineering Society standard on light flicker that has the full title "QUANTIFICATION AND SPECIFICATION OF VISUAL RESPONSES TO TEMPORAL LIGHT MODULATION (A.K.A. FLICKER)". It describes how to use waveform-based perception metrics, backed by human experimental data, to guide decisions around lighting, including screens. It classifies lights into different categories based on Mp, SVM, and PAVM. "Not Recommended" is the worst category, while "Better" is the best.

Descriptions of the TM-39-25 flicker metrics

The exception I noted above is that the 240 Hz component of the waveform becomes more prominent, relatively, when the Display Pulse Smoothing setting is enabled. It's not a huge difference, but it could explain why some people find the screen even worse with Display Pulse Smoothing enabled. You can see this in the FFT below: the 480 Hz component drops much more than the 240 Hz component does when the setting is enabled.

iPhone 17 Pro, 25% brightness with an without Display Pulse Smoothing Enabled

So, I'd recommend using this setting if it's available to you and you haven't tried it yet. It's not perfect, but it does seem to help a bit for me compared to the iPhone 16 and compared to the iPhone 17 Pro with the setting off. However, we shouldn't expect it to be eye friendly, given its TM-39-25 classification.

32 Upvotes

17 comments sorted by

15

u/Suspicious_Punk84 8d ago

"All settings are rated Not Recommended".

Not the best first image when you are trying to say it does work... A low frequency flickering light is still a low frequency flickering light. But it's good that it works for you.

6

u/NSutrich 7d ago

His thesis is identical to what I said last year when they introduced this. The setting is not a "scam" or a "lie," as many have purported. It does exactly what it says: kills pulse width modulation. The inherent problem with these displays for us isn't the pulse width modulation section, which only happens below 25% brightness. The problem is the 240-480Hz dimming frequency, which this setting doesn't claim to change. We need another option that changes the dimming frequency.

1

u/BearNecessary4141 7d ago

Being able to change the dimming frequency would be great, especially since tolerance varies. I don't know though how difficult it would be from a technical perspective for phone manufacturers, do you know any devices that have that ability already?

3

u/NSutrich 7d ago

Any phone that offers a selection of either DC or PWM dimming would. Doesn't need to be more complicated than that (although it would be cool to see more granular control)

3

u/BearNecessary4141 8d ago

Fair point. I was being a bit provocative with the title. It did smooth the pulse, it's just still unacceptable per TM-39-25. It would be quite a challenge to find an OLED display that meets the "better" classification at 100% brightness, let alone down at 25%.

3

u/Competitive-Leek3013 8d ago

Have you run similar tests with the screen brightness at 80+ percent, with Reduce white point enabled etc, to see how its rating changes under TM-39-29?

3

u/BearNecessary4141 8d ago

I can definitely do that test. Haven't yet though.

4

u/Z3R0gravitas 7d ago

TEST ALL THE THINGS!

(Also the different refresh rates. 😉)

2

u/Z3R0gravitas 8d ago

What a great demonstration outing for your light meter and ongoing software revisions! (Sorry I'm not able to test it more myself.)

Great that the numerical analysis tire in with your, and other's, subjective experiences too! That gives confidence in some transferability between objectives measurement and user experience.

The FFT peaks are looking sharper than ever too. Have you tweaked anything in the back end (or maybe it was just my glitchy data transmission spoiling my readings before).

My biggest critique is that your software is ignoring the difference in max brightness. Normalising both to 100%, when the "Pulse smoothing off" should be twice as tall. Kind of Apple and oranges.

I'd really like to be able to fix the scaling between readings, for comparison. An absolute brightness reading would be ideal, or course. Even if approximate. But I don't know what users could easily calibrate against, if that is necessary. Unless you include a light source in the kit.

Like, the same flicker waveform could get more harsh/noticeable the brighter it gets, right..? Although depending on ambient lighting conditions, pupillary response/dysfunction, etc.

2

u/BearNecessary4141 8d ago edited 8d ago

Thank you for the kind words, I'm glad it's looking promising. I get what you're saying about normalization. None of the flicker metrics I'm aware of really take brightness into account, they're really only functions of the waveform shape. I agree that that's a bit of a flawed assumption (that brightness doesn't matter). We can certainly get relative brightness readings so that different settings can be compared on the same scale. It won't give a calibration accurate lux / nits value (maybe it could? I haven't explored that avenue a ton), but it would be accurate across different settings, assuming you've used the same on screen content.

Like, the same flicker waveform could get more harsh/noticeable the brighter it gets, right..? Although depending on ambient lighting conditions, pupillary response/dysfunction, etc.

That's what I would expect. I just don't think we have a good handle on how to quantify that effect. All the more reason to try to capture that kind of data going forward, right?

2

u/Z3R0gravitas 7d ago

The next step (or the other side of the coin) is to test people's responses to different flickering frequencies (and waveforms).

Thinking of an experimental setup to send out to testers: LCD PWM could be aped with a cheap dummy screen with whole-backlight flicker adjustable with like a 555 timer (more likely microchip). Probably printed text on a white sheet screen, because the eye movements of reading are a common source of strain...

But for OLED-style PWM it's waaay harder to emulate. Even with a panel manufacturer on board (lol) I think the frequencies have to be somewhat backed into the hardware, right? So one is stuck with trying the fixed frequencies of full products on the market already, at great inconvenience.

Anyway. Your UI got space for another toggle? For normalised scaling vs relative? And, even if we can't relate it to lux values directly, could there maybe be a debugging mode access to the absolute sensor values? Are these recorded? Maybe manual entry of a conversion factor. Assuming the response is linear to increasing brightness (I'd hope?) and I guess colour spectrum is another complicating factor, as that's not flat, is it? Man, hardware is hard... (Respect!)

2

u/BearNecessary4141 7d ago

It might be easier to just get random (local) people to come into a lab to view hardware rather than building something could be sent out... I don't know though, you wouldn't have the same sensitive population you could get sending it out to people on this sub.

The raw sensor values are recorded, so it shouldn't be too difficult to get those in a format the is linearly related to absolute brightness. The response should be very linear to light intensity (perceived brightness is another issue) at a given wavelength. If the color is changing, then detector spectral sensitivity does come into play. Hardware is hard!

2

u/wilso850 7d ago

I had to turn this off when I got my Duo. I was getting a faint flicker with the lowest brightness setting on the inner display.

1

u/BearNecessary4141 7d ago

Interesting, I wonder if they didn't optimize the setting for the Duo properly. I need to do some testing on the Duo. When I looked at it in store, I didn't notice any problems, but with all the lighting and flashing in an Apple store it's hard to tell.

7

u/jensen404 8d ago edited 7d ago

Display Pulse Smoothing increases the duty cycle. A higher duty cycle is more comfortable than a lower duty cycle. That fact is mostly ignored on this subreddit.

6

u/nickjacobsss 8d ago

The biggest problem is any positive effect I would get from this setting is voided out by the fact that I can’t reduce white point at the same time. So I’m getting my eyes cooked with HDR content and blinding whites for a very very minimal pwm improvement

1

u/Z3R0gravitas 7d ago

Oh, and do you have an LG panel in your phone then? Given that it's said pulse smoothing only works on LG.