Trying to get past the 500 nits limit of the MacBook Pro (and failing)
alinpanaitiu.com
alinpanaitiu.com
What’s nuts is that this also works on displays without the ability to control luminosity on individual parts of the screen. The link you posted works on my 2020 11” iPad Pro, which has an LCD with no local dimming.
However, it slowly ramps up over a second or two, whereas my OLED iPhone (which can of course set luminosity per pixel) enters retina-searing mode immediately.
Some other interesting observations:
- If I zoom in, the over-100%-bright text fades until it blends in with the background. This is expected (OLEDs have higher peak brightness for small areas), but what isn't expected is that it seems to do it in discontinuous steps.
- If I go outside into full sunlight, the contrast between the page and text is lower. This is again an iPhone feature in action where "maximum brightness" is actually further boosted in bright conditions.
- The text takes a few seconds to reach maximum brightness. I expected it to start at full brightness and fade, but it seems to do the opposite...
I can understand why the notion programmers have that "color" is an RGB triple of 8-bit integers from 0 to 255 is so attractive. It's a simple mental model with no complexity. But to get the most out of modern displays, we have to abandon such childishly simple models. Each color channel will need to be 10 bit minimum, 16 if using linear light. Peak brightness becomes this complex many-faceted thing with per channel maximums, all-channel maximums, and variations based on both time and area!
Same with the new MBP.
The text does fade in over a second or two, and while that happens, I can notice the entire screen flicker ever so slightly. There's clearly some very impressively calibrated interplay between the LCD panel and the backlight going on.
> I can understand why the notion programmers have that "color" is an RGB triple of 8-bit integers from 0 to 255 is so attractive.
Most of the time when dealing with color, it's colors of UI elements. And those are assumed to be sRGB anyway.
You mean the 16 EGA colors, right? /s
But more seriously, I was hugely disappointed to see Microsoft unwind their wide-gamut and HDR GUI capabilities that they introduced as far back as Vista while simultaneously Apple is making wide-gamut (Display P3) and HDR standard across all of their devices.
Someone at Microsoft was forward thinking, and now some idiot is undoing that good work just when displays are catching up to the software capabilities.
Sooner or later, Windows will cap framerates at 60 Hz to make sure 120 Hz monitors don't deliver any visible benefit either...
Now, of course you could circumvent this and add retina-burning-bright controls to your app. Your users would probably hate you for doing this.
And regarding wide gamut, I'm not sure what kinds of benefits this brings to UIs either. It does make photos and videos feel more lifelike, especially when combined with HDR. But I've seen an extension to CSS that allows specifying wide-gamut colors, and you can also use them in native UIs (I've managed to do that in my aforementioned experiments https://news.ycombinator.com/item?id=30219169).
> wide-gamut and HDR GUI capabilities that they introduced as far back as Vista
Wow. That was quite the future proofing at the time when everyone was transitioning from CRTs, and LCDs of the time were noticeably crappier than CRTs.
The thing with Windows though is that it's really hard to get so many companies involved in the chain to agree on something like this. Apple has complete end-to-end control of both the hardware and the software/APIs which allows them to casually pull off this kind of stuff.
I think it's pretty weird trying to get more than maximum brightness from an Apple device. I think it would be far more useful to get a spectrum of usable levels of lower than minimum brightness. Apple's maximum brightnesses have always been close or the brightest devices available, but Apple devices minimum brightnesses have always been way too bright with no reason for it.
Additionally, the site claims it works (worked?) on 2020 MBA M1.
There seems to be a strange bug in Safari. If I change the tab from/to that page, the mouse cursor jumps to the bottom left corner of the screen.
I'm not sure that this blog post author is trying to accomplish, possibly they are trying to use some other API besides Metal?
I’m testing Apple’s claim of 1000 nits sustained brightness which led many people to believe that they can finally use their laptop in direct sunlight without squinting at the screen.
I’m aware of thermal limitations and that even sustained might not mean “whole screen at 1000 nits for 8 hours”. But it would be nice to be able to use 1 hour of my work time to work in the park outside my apartment with a bright enough screen for that time.
The system has thermal capping implemented from what I saw in the CoreBrightness framework, so it should be safe as long as the system can detect that LEDs are starting to overheat and lower the brightness automatically.
"Vertically polarized light is preferentially refracted at the surface, so that the reflected light is left more horizontally polarized" and you use vertically polarised sunglasses to filter out the reflected horizontally polarised light.
This is a video I took last summer on this: https://files.alinpanaitiu.com/ff-polarized-macbook.mp4
How about increasing the brightness of just the text, and not the background, like https://kidi.ng/wanna-see-a-whiter-white?
No reason to crank up the brightness for the background as far as I can see.
But this can’t be done either. That website has the whiter-than-white text because it chose to do that. It’s known that every app has the possibility of rendering HDR content at more than 500 nits.
The problem I was trying to solve is how to do that from the outside, on apps that haven’t implemented HDR logic (which is about all of them)
Can you elaborate more on the Objective-C methods? Are you talking about the “not exported” ones?
You need iPhone 12 or better to support.
I take 5 minutes to ride from home/office to a table in a nearby park to work from there for 1-2 hours. It's so healthy and invigorating, and the change of scenery can inspire creativity.
But it's hard to justify when nuances on the screen become imperceptible under bright sun light. 1-200 more nits would change that. And the 2021 16" MBPs are technically capable of up to 1600 nits!
Apple building in this framework creates brand new business opportunities to take money from customers.
https://www.reddit.com/r/assholedesign/comments/r7n8cd/keuri...
Dolby Vision requires the whole chain to perfectly respect what the content says, both in color and brightness, so if you have a bright film, it'll blind you in the dark. But they now license (I assume for an additional fee) adaptive brightness for Dolby Vision!
The HDR white is actually a lot brighter than the SDR white (which means the LEDs behind those pixels are allowed to go to full brightness).
You can see that effect if you watch this video in Safari on a 2021 MacBook Pro: https://files.alinpanaitiu.com/hdr-test-pattern.webm
Here's an article where the nits value is measured using a calibration device: https://www.notebookcheck.net/The-new-MacBook-Pro-14-only-ma...
The measurement shows that SDR content goes up to 500 nits (which was the peak value of previous MacBook displays as well) while HDR content goes up to 1607 nits.
But people usually look at this, relative to previous displays, not relative to peak brightness (since the peak brightness is not achievable for prolonged periods of time because of overheating)
Edit: apparently at least on some laptops your screen may automatically adjust brightness downwards if you are in a hot climate and the cooling system fails to keep up: https://9to5mac.com/2022/02/04/macbook-pro-limited-brightnes...
SkyLight.framework:
SLSDisplayIsThermallyLimited
CoreBrightness.framework
-[CBDisplayModuleSKL hasThermalMitigation]
-[CBThermalBrightnessCap getCurrentCap]
-[CBThermalBrightnessCap setJetMode:]A lot of non-technical users might get used to that brightness and then start complaining about their display dimming by itself randomly.
If they can't sustain their sustained brightness, that might even be false advertising.
(Nevertheless, still super happy w/ the computer as a whole; it's an amazing machine.)
If it can sustain 1000 nits for HDR content, it can for SDR too. The display isn't going to say "hey it's SDR let me piss them off" and suddenly start dissipating more heat at 1000 nits at SDR compared to HDR after all.
Even if you watch 8 hours of HDR content, only some of the LEDs will get to peak brightness for small periods of time. That will allow the LEDs to cool down enough to sustain that brightness.
The macOS UI and webpages on the other hand are mostly bright white and that can cause trouble on extended periods of time.
As a dark mode user I'd love to see 1000 nits though, maybe something like iPhone thermal throttling the brightness when it gets too hot.
Perhaps "sustained" is some kind of jargon from the laptop industry but I consider myself to be more educated than the average Joe when it comes to computers and I would've expected a 1000 nits screen based on their advertisements. I don't see what Apple has to gain by either lying or deceptively using jargon like this.
- developers render UI to an HDR buffer
- developers standardize on a open-source brightness slider in the Menu Bar
- or, each app has an individual 'brightness' slider.
It's a lot of work and a shame that Apple is making us to do this, but if a handful of apps start to do it then perhaps they'll come to their senses and just let users control their own damn screen brightness.
This headline really threw me, trying to guess at what level of organization there was an information bandwidth issue with the MacBook Pro that would be measured as "500 nits".
I had sometimes problems with color management on mac on fullscreen videos and to prevent that I put a small window from Helium or Pennywise (always on top browsers) into some corner to fix it.
On an M1 you can run the following:
ioreg -r -c AppleCLCD2 | grep -i nits ioreg -l -f | grep nits
which should list properties of all objects, and the display I could find: ioreg -r -c AppleBacklightDisplayThus, I'm assuming indoors.
The current MacBook keyboards are quite nice, they have the same mechanism as the external Magic Keyboard sold by Apple, and they seem quite resilient. I had no stuck key in the last 2 years.
Note that I bought the 2018 or 2019 model with extra isolation under the keys. That didn't help at all.
The keyboard worked perfectly fine.
I haven’t had a chance to test the 2019 Intel MacBook too much, but the M1 2020 was heavily used outdoors. I believe the M1 2020 model was the first one to get the Magic Keyboard mechanism: https://support.apple.com/kb/SP824
The prior model of Magic Keyboards with the Fn key use older defective dust-vulnerable switches.
If you are a dark area 200 nits would even be high.
If you are in a well-lit area or outside in a sunny day, 200 nits would be super dark, and by that definition if it was unhealthy, looking at almost anything in a well lit day would be unhealthy.