DisplaysShouldNotBeTVs

@aiaf is it maybe an idea to add an option to StillColor to disable IOMFBContrastEnhancerStrength ?

It looks like IOMFBContrastEnhancerStrength is also messing with the screen

Rikl

So far none of these options seem to remove the pixel flicker under the microscope. I don't use this laptop as my daily driver so it is not urgent but strange to see this change in panel behavior.

    photon78s Maybe try DFU restore to earlier macOS version? Not just a reinstall but a full DFU restore - requires connecting to another Mac (or unofficially a Linux device) with USB-C - which is how you downgrade not only the OS but also the bootloader/firmware version

      DisplaysShouldNotBeTVs

      Too bad I returned the other mac mini. Will look into this. In the meantime, if I'm going to use it for long periods of time, I would remote in or the lossy capture card approach from a PC.

        DisplaysShouldNotBeTVs

        Yes, that's one. I would not say 100% not usable thought I've had more eyestrain lately but out of precaution I will not try finding out even more.

        async

        Thanks so much for all your work.

        Tired to copy and paste this into terminal to try, am I missing something? Thanks in advance (On MBA M2)

        Has anyone figured out why dithering autoenables itself even while Stillcolor is on? It happened again this morning as I felt something weird in my eyes.

        • aiaf replied to this.

          async how can I apply those parameters? Could you please provide some guidelines? Thanks

          @madmozg Can you elaborate on your issues with the mba? I just got an m3 air and it still seems to make me a bit nauseous. It's just the white balance that has that slight yellow glow that sort of bugs me. I keep fussing with the brightness but can't find a setting that I settle on. I've got stillcolour and font smoothing disabled and sRGB.

            Ruoma I tried two M2 airs and one definitely had less yellow glow than the other, they had different panels so probably M3 has panel lottery too. Unfortunately though, if one of them is already giving you that feeling, I'm pretty sure that modern MacBook in general won't work for you as for example I still get the same feeling to a wide extent (mostly while using it indoors) on the M1 Air.

            What laptop are you upgrading from?

            Another thing to try is disabling brightness compensation (needs BetterDisplay installed and running). This made my M1 Air screen noticeably less yellow:

            /Applications/BetterDisplay.app/Contents/MacOS/BetterDisplay set -namelike=built -framebufferBoolProperty=off -specifier=IOMFBBrightnessCompensationEnable

            Weirdly enough, I've noticed that a lot of the yellow glow feeling is gone on my M1 Air while booted into Asahi Linux (even though I can still see temporal dithering), but of course can't really transfer that into macOS.

            If you can't get things working for you within the return period I'd highly suggest you return, as in my case I've only ever had issues like this (in the case of laptops) on MacBooks, a lot of the problems come from the screen and not my eyes.

            I've definitely seen some bad Windows laptops I also wouldn't want to use daily (mostly newer ones) but still nothing has that extreme disorientation and "your field of vision is continuously becoming more crushed down and constrained" feeling that is present within all new Mac internal displays/iPhones/iPads and can even slightly be felt in older Apple devices too.

            Maybe try another M2 or M3 Air after that, since many ship with entirely different LCD panels from the last as I experienced.

            Another one to try is the M2 Touch Bar Pro (but only units that have "000000" in their display EDID are good. If you end up getting one with "FMX" in the EDID or no zeroes, it's one of the really bad ones as confirmed by multiple people here. Definitely try one more if you end up with an FMX Touch Bar Pro panel.)

            if still doesn't work after that, modern MacBooks are probably not for you and you should look for a different laptop.

              DisplaysShouldNotBeTVs @aiaf I can definitely still vouch for the fact that there's something weird going on with macOS (or, specifically newer macOS DCP firmware, still haven't tried a DFU restore yet) aside from dithering, both in terms of backlight control and flicker

              Installed a matte screen protector to get glare out of the equation entirely and I can notice this switching between macOS Ventura 13.6.6 (but on top of Sonoma 14.4.1 firmware) vs. Asahi Linux 40 (but on top of "temporarily loaded in" Ventura 13.2 DCP firmware)

              -

              Let's split flicker into two separate beasts, the classic type of "FRC" temporal dithering that is definitely distracting and a big source of strain but doesn't really "mess with the position of things" - text and colors are obviously flickering, but every pixel despite this flicker still stays within it's correct place and it doesn't feel like the entire UI is twitching erratically in all four directions like you're trying to look at it on a moving boat.

              Then, there's the really weird stuff going on inside macOS which I can only describe as a "disorientation pattern". This is the type of flicker that actually makes it feel like everything is moving around, no pixel ever feels "locked" to one location to my brain, your attention randomly jumps to small items on the screen, edges seem to "glow", and seems to be responsible for the really weird "false 3D depth" effect many people such as @async have discussed here. "When moving one item around it also feels like something on the entire other side of the screen is slightly changing too."

              -

              On macOS, it feels like I can successfully disable "typical FRC" flickering with Stillcolor, but the weird "disorientation pattern" flicker remains. On the M1 Air it's tolerable enough to use outdoors, but indoors even with the matte screen protector on I get tired so fast looking at macOS even with Stillcolor and disabling as many IOMFB properties as possible.

              The yellow glow that @Ruoma mentioned is here and even feels like it's shining through my matte screen protector. here are obvious shenanigans going on that are either coming from macOS or the newer Sonoma firmware.

              -

              Meanwhile, while booted on Asahi, the "typical FRC" is currently unsolvable since there is no Stillcolor equivalent in Linux to interact with the IOMFB registry. I can notice flicker that feels similar to the type of FRC used on external monitors. The same "subtype" of flicker that is also present in macOS but can be disabled with Stillcolor.

              However, the "disorientation pattern" flicker is not here at all. Even though I can still notice FRC which is definitely still a big issue… on the other hand, everything feels "locked into one location", images feel much flatter, the "false 3D depth effect" is significantly minimized. And very interestingly, the feeling of "backlight glowing" essentially stops.

              When scrolling within one small scroll area, unlike macOS, it doesn't feel like "the rest of the screen is moving as well". Only the small scroll area feels like it's moving.

              With the matte screen protector, I can actually use Asahi Linux indoors without the instant "tiredness and nausea symptoms" I get from my macOS install. I still get external monitor-esque FRC strain symptoms (which probably could be fixed if Stillcolor was ported to Asahi Linux 👀👀) causing the screen to still feel harsher than a FRC-free display, but it's so much better than macOS.

              Web browsing on Asahi vs macOS feels like using two entirely different computers, and this is true even if I only focus on the solid colors and not the text rendering.

              "FRC" flickering is still present in Asahi because I can't use Stillcolor, but the really weird "instantly recognizable Apple disorientation effect" type of flickering that Stillcolor can't disable, for lack of a better phrase, is temporarily gone while using Asahi until booting back into macOS.

              -

              There is definitely a lot more to investigate aside from enableDither. If Asahi can still have "totally recognizable FRC flickering going on" to me while so many other symptoms are gone, there are definitely other types of flicker that macOS is adding in that make it much worse than just regular FRC.

                DisplaysShouldNotBeTVs I’m upgrading from a 2008 Mac Pro with a Cinema Display 🙂 Was hoping to connect the air to a studio display but maybe I should revert to a Mac Studio as I assume with an external display, I’ll have more options to get a doable solution.

                I’ll try the betterdisplay setting. This has nothing to do with a dummy mirror right? Cause I’m confused on how to do that. Just a setting on the internal display right?

                thanks

                  DisplaysShouldNotBeTVs

                  When Asahi Linux was in early stage people were reporting reduced eye strain compared to MacOS. BUT earlier versions had no GPU drivers included (Asahi team had to reverse engineer them). Possible explanation is that dithering functions do not work without proper GPU drivers.

                  The Apple Silicon gpu drivers were added to Asahi in 2022-december (see here)

                  Maybe you can try Asahi versions before 2022-december to check in difference for eye comfort.

                    Ruoma I guess nowadays you need to pay a bribe at apple store in order to get not rotten apple 🙂

                    Hunter20 Maybe you can try Asahi versions before 2022-december to check in difference for eye comfort

                    How do you do that? I was trying to search how to install earlier versions and there was literally no results, like no one has ever wanted to do that so far and I couldn't find any way to force the installer to download an earlier version etc

                    Also, the main point of what I've already been saying in my previous post is even though FRC is present in the newer GPU accelerated versions of Asahi, it still feels sooooo much better than macOS. Asahi only has regular FRC temporal dithering (which is still a big problem of course, but far less bad that whatever macOS is doing) BUT seems to totally not have the weird disorienting types of additional twitching false 3D effect flicker that on the other hand macOS still has at all times (even after using Stillcolor)

                    Asahi on "temporarily loaded in" 13.2 DCP firmware: FRC flicker cannot be disabled, but the "Weird Flicker" (AKA any additional disorienting false 3D type of flicker) is NOT here at all!

                    Ventura 13.6.6 on 14.4.1 DCP firmware: FRC flicker CAN be disabled with Stillcolor, but the "Weird Flicker" still happens no matter what, even after using Stillcolor

                    Just to clarify, my brain is actually able to tell these two types of flicker apart which is why I feel comfortable saying this, lol

                    The main thing I haven't tried yet is running Ventura with real Ventura DCP firmware instead (instead of the weird "Ventura OS on Sonoma firmware" limbo state I'm currently in) which I need to DFU downgrade and wipe to do. Which means that as of now I'm not sure if the Weird Flicker is a macOS thing in general or more specifically a Sonoma DCP firmware thing.

                      Regarding my issue with the yellowish white, I don’t understand why a white background with black text would need to flicker or dither or frc or whatever is going on? I mean it’s just white no? Why do I get slightly nauseous with just white? Or is it a magic Apple white that only true 10 bit panels can properly display??

                        Hunter20 It's not actually white, notice how if you mess with turning off the brightness compensation property it will switch from a yellow white to a reddish white implying that the yellowish white you were just seeing was not actually true white. Who knows if the reddish one is true either…

                        One of the reasons why they do this is probably relating to something that I observed on an earlier 2016 Intel MacBook Pro: in Boot Camp Windows, where there is much less color calibration going on, I noticed that when turning the brightness up and down the screen will alternate around every 10% between a bluish white and a yellowish white. Probably as a side effect of however the hardware backlight works. I've also noticed a similar thing to a milder amount on Asahi Linux on M1 Air. Yet while booted into macOS on either Mac, this "doesn't happen".

                        So, to "compensate" for this variance in color accuracy, I've noticed while booted into macOS, even on (some) Intel Macs in addition to M1 ones, the white is changing very slightly (which essentially needs flicker to achieve in such a subtle amount) to prevent it from "becoming inaccurate" and looking more similar at all brightness levels… and then causing tons of strain from doing so

                        In addition to this brightness compensation there's probably tons of other post processing layers we don't know about that are ALSO affecting the white even further

                        (to be clear, this is in regards to the internal display, most of this doesn't happen with external monitors. Stillcolor seems to actually fix external monitor issues for me entirely, the remaining problem in my case though is that all of the external monitors I own have their own internal FRC when provided an 8 bit signal even with a totally clean source like an old PC, and that's still a big issue for me.)

                        So yes, you're actually semi correct in that "it's a special white that only Apple displays can provide".

                        Also, to make matters worse, Apple will still dither even if they switch to true 10 bit internal displays in the future, because they actually made any Mac that supports Display P3 use a 16 bit color space on the GPU. I'll make another post soon about this. They mentioned / confirmed this detail in the WWDC 2017 talk about introducing Display P3.

                        Finally, about the "black text" part - remember that (unless you're using a retro pixelated style font that is perfectly aligned to the grid) all the edges and curves of black text are actually made up of shades of gray and will thus flicker on any temporally dithered display.

                        P.S. a quote from a blog post when Apple introduced EDR:

                        https://prolost.com/blog/edr

                        Apple has remapped “white” to something less than 255-255-255, leaving headroom for HDR values, should they be called for. The operating system is complicit in this trickery, so the Digital Color Meter eyedropper shows “white” as 255, as do screenshots.

                        With Catalina, Apple quietly changed what “white” means for millions of Macs, and none of us noticed.

                        Between high-bit-depth P3 displays, display color management, software calibration, and True Tone, it’s probably been a very long time since “white” in a Mac UI was truly 255-255-255.

                        So yes, you're actually semi correct in that "it's a special white that only Apple displays can provide".

                        Also, to make matters worse, Apple will still dither even if they switch to true 10 bit internal displays in the future, because they actually made any Mac that supports Display P3 use a 16 bit color space on the GPU. I'll make another post soon about this. They mentioned / confirmed this detail in the WWDC 2017 talk about introducing Display P3.

                        Finally, about the "black text" part - remember that (unless you're using a retro pixelated style font that is perfectly aligned to the grid) all the edges and curves of black text are actually made up of shades of gray and will thus flicker on any temporally dithered display.

                        P.S. a quote from a blog post when Apple introduced EDR:

                        https://prolost.com/blog/edr

                        Apple has remapped “white” to something less than 255-255-255, leaving headroom for HDR values, should they be called for. The operating system is complicit in this trickery, so the Digital Color Meter eyedropper shows “white” as 255, as do screenshots.

                        With Catalina, Apple quietly changed what “white” means for millions of Macs, and none of us noticed.

                        Between high-bit-depth P3 displays, display color management, software calibration, and True Tone, it’s probably been a very long time since “white” in a Mac UI was truly 255-255-255.

                        Due to all of this I have given up on "strain-free MacBooks / iMacs / iPads / iPhones / Apple Watches" at this point.

                        Using a Mac as a desktop with Stillcolor and a safe true 8-bit zero FRC external monitor is the only way to fully salvage Apple technology

                        (aside from hacks like streaming macOS through remote desktop to an old Windows laptop, which is my main and only strain-free setup at the moment. If you're wondering why I'm not using an external monitor myself it's because personally I don't want to spend time getting external monitors working as I have ergonomic issues using desktops anyway, I strongly prefer laptops and the ability to not have to sit in one place all day.)

                        My goal is to fully switch my portable workflow over to Windows and Android this year, because, even though there are still many bad devices there, at least I have options such as different brands to choose from and easier ways to fully swap the LCD inside of a laptop

                          dev