Temporal Dithering Sensitivity - My Solution

JTL And so are the majority of the illuminated keyboards, rgb or white, they use PWM dimming,too

Please let us know. A far as I know, the current Zbooks (G2, G3 and G4) all use PWM dimming on regular IPS-s

JTL I think you would need a DSLR or mirrorless for that, the high frequency PWM are hard to distinguish on smartphone cameras. I highly doubt a flicker free Dreamcolor exists

Alyosha2001 I have a Canon 80D that can do at least 1/4000 shutter speed.

Alyosha2001 Been there, done that.

Alyosha2001 Check my other thread on how to build homemade oscilloscope and you dont have to do any more of these stupid tests Ive done them too and wasted a lot of time. They rarely give any real proof and just confuse you more.

martin Very interesting DIY! I have access to an electronic osciloscope, but this seems very handy, except the part with overvoltage

ditherig 1.8 is out, it still enables default dithering back aftter the screen goes off and back on, using Intel HD Graphics 530

When I once talked in the nouveau* IRC channel with one of the devs, he said they enabled temporal dithering for notebook displays by default because notebook displays don't dither and so they need software dithering. He might be wrong or his knowledge might be outdated though. But if he's right, the color drop should be obvious and result in visible banding.

* (an alternative open source NVIDIA driver)

martin I've attatched 2 pictures on november the 17th, take a look at them, in my case the banding (when the dither is off) is obvious

martin Yes, the difference is worth it, I prefer the banding all the time.
As far as I know, iphones do not use PWM, but a very interesting similar matter I encounter with the mirrorless Sony NEX5 and a6000. If I use them even for very short period, like taking 2 or 3 pictures, a very sudden dizziness occurs. And as far as I could tell, their LCD's are PWM free. On Canon 550D (T2i) I did not encounter this. I suppose it's only the dithering, but it's like some are affecting more than others.
Unlike the PWM, I don't know how to measure or acknowledge the dithering.

martin Martin, my feeling here is that we are sensitive to some kind of ... "flicker". Flicker is a term that could cover - strobing, pixel marching, pulsing, or any of a variety of other ills. If I take two screens, one which hurts and one which does not, there tend to be two kinds of differences. Either the one that hurts seems, when you look closely, to "flicker" (i.e. static images are subtly moving) or else it is painfully sharp. In that case, I suspect blue light but can't rule out a third, unknown factor.

What I can say is that we've come closer to hitting the nail on the head in some cases here. We now know - in the vaguest terms - what android phones are doing wrong, and it's color spaces. We know what Windows 10 is doing wrong, and it's image compositing. We don't know WHAT in that layer is going wrong, but we know what the problem is. We're getting there.

quantumzipper Any updates? Did the S7 work out for you with the screen protector? What about the Dell XPS? Downgrading Intel driver?

hard to know the right "dithering" thread, but thought this was helpful from the displayCAL forum. (I havent seen much talk here of using monitor calibration software)

How do I know if a graphics card is capable of dithering?

Looking at a smooth grayscale gradient in an image viewer with color management turned off(!) is usually a reasonable test. I.e. first look at it with the videoLUT set to linear (no calibration) to make sure banding is not in the image itself or introduced by the display (some panels are less than 8 bit and use dither internally to generate intermediate steps). Then load your calibration. If it still looks smooth, the graphic card either dithers, or ouputs a higher bit depth (both should suffice to reduce or eliminate calibration-related banding artifacts).