deepflame Enabling 10-bit color support tells the driver that I use a 10-bit display and turns off dithering. Interestingly this also works without a 10-bit screen.

So if tricking the app into thinking you have a 10-bit display keeps it from dithering within the app, I wonder if we could do this system wide? @JTL is this something you could use or alraedy are? Is there a way to trick the entire system/gpu/whatever does that request for system wide dithering into believing we have a 10-bit or greater display and this avoiding it needing to turn on dithering for our actual 6 or 8 bit panels? Using a "quality" greater than its request would be better if it would work because you could tell it something wild like "this is a 128bit display" etc it would cover us long term rather than chasing 10-bits then the next thing on and on.

KM I have an idea about this: Pixel 2 is AMOLED.

I think I follow what you have written but am missing how that explains that the night mode tinting causes strain on the Amoled.

deepflame Someone on the Nvidia forums claimed that the Quadro cards of the same chipset generation as the 10xx (Pascal) had dithering enabled forcefully.

  • Link replied to this.

    deepflame the thing is in the past screens were 6 bit and dithered to get up to 8 bit. Dithering isn’t a new technique so I’m reallly not sure if we are looking in the wrong place. Also dithering is such a faint flicker especially compared to say harsh led PWM flicker so things don’t add up when someone is sensitive to dither but completely fine with PWM.

    Also very few games up to this point are 10 bit. Maybe a handful. And if content like video games or movies are encoded in 10 bit I’m not sure they can request a panel or gpu to dither.

      JTL there are people on forums complaining about 10xx series nvidia cards not having dithering enabled and them having problems with banding due to it. So a lot of mixed info out there not sure how to test.

      If running Linux you can turn off dither in nvidia 10xx series cards right?

      Link Also dithering is such a faint flicker especially compared to say harsh led PWM flicker so things don’t add up when someone is sensitive to dither but completely fine with PWM.

      I don't agree with this because PWM is the entire displays backlight turning on and off regularly...dithering is each pixel flickering on its own and creates a lot more overall movement as you can see from the Dasung videos @degen took. Even a static screen is "moving" and wiggling and always in motion. I would say seeing every background, object, letter etc moving constantly and independently via dithering would be more difficult for focusing and strain than strobing of a lightsource. Even incandescent bulbs flicker and nobody is bothered by that. Now I am not saying PWM or strobing lights don't bother anyone...I hate visibly strobing lights...but I do disagree that it's obviously much worse than wiggly dithering.

      I also don't think the 6/8/10 bit progression disqualifies this theory since we don't know if something similar to @deepflame's experience was happening before where apps/OS's were requesting certain performance or panels were just not recognizing or capable. That's my theory as to ancient CCFL laptops don't tend to bother us...they simply aren't capable of responding to the requests for dithering up to fancier graphics...of course it could also be that the older software people tend to use on those older devices aren't 'asking' either.

      This will be easy to test once someone can comfirm a way to swtich dithering on and off. It's either going to be a clear relief or not. For me removing PWM was not a clear relief and while I wanted to believe it and tried to push through it, PWM free panels hurt just as much for me.

      • Link replied to this.

        hpst but the overall brightness difference is very small. The pixels are shifting between 2 very close colors.

        • hpst replied to this.

          Link In my mind it's not about brightness wrt to dithering..its about movement. Watch @degen's videos. You can see movement everywhere because the E-ink panel makes it visible unlike an LCD. If you were reading a book where the white backround and black letters were always moving a little bit and changing shades even a little etc it would be tiring and hard to focus on. I think this is what dithering is like for us but on a much larger scale since even what looks like a solid white background is really a bunch of wiggly points rather than a solid area. Compound that with fonts, images, video etc its constant movement and that's exhausting for the eyes. All that wiggling, movement, changing of colors etc are not obvious to the naked eye but are straining the visual system nonetheless. It's like "seeing" a solid white paper and when zooming in realizing its thousands of maggots crawling all over each other. We may not recognize that movement when zoomed out, but the eye muscles and brain do and are filtering it. We are already filtering out so much when looking at LCDs on a macro scale that this might just be the straw breaking the camel's back.

          Obviously this is entirely speculation, the dithering IS there but it might not bother us at all...or it might be the root cause and all the other stuff like PWM/eye accomodation etc are just additive factors or triggered by it. People were positive PWM was the root cause as well. But we need to rule this out if nothing else and there isn't any other obvious theory that at present doens't have a definitive way to test.

          Link Currently I work with this around 9 year old CCFL backlit laptop running Windows 7 and I am pretty sure dithering is a big thing for me. My eyes can tell after some seconds (or even right away) if it is comfy or not.
          I do not have proof like color banding screenshots or such but I can surely tell that setting the graphics driver to "enable 10bit color" made me able to work with Opera and Capture One Pro again.
          Otherwise I got a bad eye strain after some minutes like most of us do.

          Running the current version of Manjaro Linux gives me strain again. So I am pretty sure it is software based in my case. That tells me that it is possible to turn it off in Linux as well. Good thing here is that it is open source and it is possible to modify the source...

          PWM is its own beast and I found a laptop with CCFL and PWM bad as well. I also own a PixelQi 10,1'' panel that uses PWM and it is not as good as I hoped it would be.

          Also @Gurm stated in a different thread that Destiny 1 is fine on his Xbox One whereas Destiny 2 is not.
          ( https://ledstrain.org/d/358-xbox-one/11 ). I am no expert here but as he also thought the graphics card changes its graphics mode and enables dithering. I would suspect it is the color depth...

          • hpst replied to this.

            deepflame I am no expert here but as he also thought the graphics card changes its graphics mode and enables dithering. I would suspect it is the color depth...

            From another non-experts point of view it DOES seem a logical theory. And since we are never going to get every manufacturer and software maker to agree to turn dithering off or give us a switch...it seems tricking things into believing the needs can be met without dithering is the onloy sweeping approach possible. You have a reproducable relief within those apps...now we need to figure out how to get the OS to react like the apps and make this a system wide trick. I don't know if this is a plausible idea or not...tricking things into believing they don't need dithering, vs somehow blocking it.

              hpst Yeah, I think it makes sense as every manufacturer is about HDR, high contrast, sharpness bla bla... And I think the hardware cannot deliver this completely yet so they need to help with software voodoo like dithering.
              (yes, blue light and PWM are their own things but I think that we are in the HDR aera now where dithering/FRC plays a big role).

              • JTL replied to this.
              • hpst likes this.

                deepflame I was hoping with all these modern HDR monitors it would finally knock some sense into these companies into producing better panels, but nothings that simple... 🙁

                • hpst replied to this.

                  JTL So is this in line with how you were working to stop dithering? Or if not a workable approach? Tricking the system into believing a higher quality panel is used so it doesn't think it needs to turn dithering on?

                  • JTL replied to this.

                    hpst I didn't even know that forcing 10-bit color could stop dithering. I was assuming that by forcing 10-bit color it would try and dither a 6-bit panel to 10-bits and fail. Or in the case of an 8-bit panel it might work using dithering to make a 10-bit image, but that's not what we want.

                    It's kind of complicated but my approach was just reverse engineering and editing the driver code to stop dithering altogether. Harder then it sounds.

                    • hpst replied to this.

                      JTL So do you think @deepflame's experience is a one off specific to his/her hardware and apps? Or logically reproducable in general with the idea that the system is requesting a certain level of color and that lying to the system (as his setup seems to be doing by saying its a 10-bit panel in a setting even if the hardware really isn't) would work on a macro scale? How would we proceed to determine this and then how would we extrapolate this to a larger solution like telling the whole system the panel is high bit to hope for the same response the apps are giving and not asking for dithering?

                      • JTL replied to this.

                        hpst I don't know at the moment. I do have some ideas to test this theory in more detail though.

                        • hpst replied to this.

                          JTL If you know any way I could check it on a 6 bit panel running a linux distro please let me know. If there is some way to trick the OS into thinking the panel is 8-bit/10-bit etc etc to see if this stops the 6+2 dithering crap. This could be a real breakthrough tactic wise. I just don't know where linux makes this request..like is it in the various drivers? In @deepflame's case it sounds like the individual apps are requesting 10-bit and are accepting being told the panel is 10-bit by that software setting JUST for those app windows, thus not needing to dither (which I am not sure if its a Windows graphics setting or what). It's probably a lot harder than I am imagining...but it would be amazing if this was a viable way to get around dithering for now.

                          • KM replied to this.

                            deepflame If you are not a gamer

                            But I am - and a keen flight simulation / simracing fan as well so not being able to upgrade my trusty 970 to something much more powerful is extremely maddening.

                            • JTL replied to this.

                              Adding my experiences to the wider discussion here. I'm A-OK with my Plasma TV and I'm OK with my Dell 2407/2410 or similar CCFL screens on a Nvidia 970 (and AMD 6950), as well as my 2013 MacBook Pro's IPS screen.

                              Otherwise several new LCD TVs, most iPads and iPhones (haven't tried OLED), various laptops, and several new computer monitors (high refresh, low blue, AMVA, IPS), Xbox One, and 980, 980Ti, 1070, 1080 cards all give me eye strain. At this point I'm thinking wow - it's both the screens AND the hardware that's driving them. Realising it was also the video cards was really a sad moment. But then you add the new version of Chrome, Firefox and Prepar3D Flight Sim V4 that ALSO give me the same eye strain and the whole situation gets twice as convoluted, and frustrating.

                              Now, I really don't know what to make of it. Screens do it. Video cards do it. And now windows (part or full screen) can do it too. For the life of me I cannot decide if it's blue light, PWM, dithering or something else. Right now, my money's on dithering or maybe something else. And you know it's damned expensive buying gear to TRY only to have to on-sell it at a loss. Where I live we don't have easy try-before-you-buy or money back returns (except Apple - which I've taken up on a couple of iPad tests).

                              And yes I've had my eyes tested, blah blah blah, and I counter that by saying - "I can watch/use my older hardware for hours with no problems at all - so it's not my eyes!"

                              Personally, all I really want right now is to be able to go out and buy a more powerful GPU for my flight sims - I can live with 24" screen(s). But then if I ever change job... I guess I'll need to buy this MacBook Pro 2013 that I'm happily using - from my current employers.

                                AgentX20 But then you add the new version of Chrome, Firefox and Prepar3D Flight Sim V4 that ALSO give me the same eye strain

                                Even on your otherwise safe setups? Just those apps specifically strain you but the rest is ok?

                                  hpst Even on your otherwise safe setups? Just those apps specifically strain you but the rest is ok?

                                  Yes, exactly.

                                    dev