I contacted AMD to ask them if the Pro w6600 card had temporal dithering disabled. They emailed back saying it can be disabled via the editing the registry and creating a key in the correct amd section with DP_DisableDither=1 .

Reading here, it looks like it has not worked?: https://ledstrain.org/d/750-amd-displayport-no-dithering -> https://help.teradici.com/s/article/1569

Has anyone tried this and had success with it?

I can't comment on that exact card or the registry setting, but I'm beginning to believe certain cards may have temporal dithering enabled by default but embedded in the VBIOS.

For what it's worth I have a Radeon Pro W5500 in my workstation, and either in BIOS setup or running under Linux with the amdgpu driver, there is absolutely no temporal dithering or similar motion artifacts.

If I had a spare collection of desktops and GPUs handy I would be willing to test more scenarios.

    JTL

    I think I read your comment in another post about that. Which is what prompted me to call AMD about the w6600.

      caboy Fair enough.

      At another guess, it could be its also disabled by default with the newer cards but perhaps the registry key is more an "insurance" thing, as in, it should be disabled by default but maybe the registry key enforces it in the driver. Just an educated guess.

        JTL

        I was hoping it was disabled by default on the Pro series of cards. I would think most professional graphics editors would not want dithering to hide banding effects.

        I heard back from AMD. This is what they said:

        The Radeon Pro W6600 has temporal dithering disabled in driver by default.  Al Radeon RX 6xxx series and Radeon Pro W6xxx series would have temporal dithering disabled in driver by default

        I thought I remembered other people saying they had trouble with the RX6xxx?

        I ordered a Pro W6600 card and will report back with my results.

          caboy I thought I remembered other people saying they had trouble with the RX6xxx?

          Someone said that about the 5700 XT at least.

          There is this really old tool for RadeonMod(from 2017). It shows you the registry values that worked 2017, not sure they still work now. You can download it on the guru3d page.

            caboy

            To follow up on this. I have the AMD Pro W6600 installed. Still get eye strain / pain from it. Got a clean copy of Windows 10 and the AMD driver installed last night. Turned it on tonight and I could tell right away my eyes were starting to hurt.

            I was going to try the registry thing "DP_DisableDither". When I went to the place in the registry to set the key, it was already set. I'm not sure what conclusion to draw from that.

            Also got Linux installed. Still got eye strain / pain while using linux (with the gnu driver).

            I am going to email AMD and ask them what they think.

            • JTL replied to this.

              Sorry about that. Maybe I got lucky with my W5500?

              What are the other specs in the equation (Motherboard, CPU (somewhat believe in red herrings here but for the sake of completeness), type of display output (any adapters used) and monitor)?

              If you had an identical capture card setup to me it would be possible to tell if it was dithering in hardware or not.

              caboy Also got Linux installed. Still got eye strain / pain while using linux (with the gnu driver).

              You mean the amdgpu driver right?

                Are you using dp Cable? Or an Adapter to dvi? Try setting all 3 entries to 1.

                JTL

                Going to try to reply to you both.

                Motherboard is an old ASRock x79 with 6 core xeon (both are 10+ years old). This system was fine with Windows 7 and a Radeon HD 7950. It was also good with CentOS 6. The "good" setup was a different monitor. I think I had the HDMI going to a DVI.

                As soon as I put Win 10 on it, the eye pain started. Trying fedora and centos 7 also give eye pain. The monitor has changed at the same time i upgraded to Windows 10. I don't remember any eye pain with Win 7 and the new monitor. (Though this machine with Win 7 only ran on the new monitor for a few hours before I upgraded it.)

                With this new monitor and old card I tried:
                HDMI (computer) to HDMI (monitor).
                DVI (computer) to VGA (monitor). also (I don't remember that helping, but will probably give it another attempt.)

                The new card is DP->HDMI (adaptor on the computer) to HDMI (monitor).

                In Linux I was trying the amdgpu driver yes. I could not get the AMD Radeon PRO driver to work with Fedora.

                The new monitor seems fine with other devices. My laptop plugged in via usb-c -> hdmi does not have any eye pain. I have also tried a mac mini which was okay. A mac studio was not okay.

                I think my next tests will be:

                new card:
                DP->VGA (adapter on computer) to VGA (monitor).

                old card:
                CentOS 6 To see if the monitor itsself might be suspect. (Though I suspect the issue is not the monitor.)
                I will try both new and old cards hdmi and vga with the amdgpu driver.

                • JTL replied to this.

                  caboy new card:
                  DP->VGA (adapter on computer) to VGA (monitor).

                  FWIW: I do know that for both AMD and Nvidia cards, they haven't had the circuitry to perform the conversion from digital->analog in the card for several generations, which means that you're at the mercy of the quality of your adapter among other issues.

                  I tried using a adapter DP-DVI but i get very mild nausea from my old TN, my new monitor via HDMI didnt create that nausea. Didnt try VGA adapter though.

                    I ordered an old refurbished LCD. Will see if that makes any difference.

                    The old refurb LCD did not make a difference. My eyes hurt bad using it. Even during the Windows 10 reinstall.

                    I was not able to find a driver or icc profile for that monitor. I remember reading in a different thread someone said the icc profile made a difference for them.

                    Not sure what to do now.

                      caboy Try win11. You can activate it with a win7 oder win 10 key before installing it. It helped me a lot. But make a clean install.

                      hayder1983 I tried using a adapter DP-DVI but i get very mild nausea from my old TN, my new monitor via HDMI didnt create that nausea. Didnt try VGA adapter though.

                      If you feel like it, get a dvi-hdmi cable, or a dvi-hdmi connector adapter to test with. The dvi and hdmi signals are the same and are not converted, what might be different is the pixel clock and/or the chip on the monitor's board.. whether it is processing the dvi input on a different chip than the hdmi port. You can use the same dp to ? adapter on both ports.

                      On my monitor, using HDMI with my PC lets the pixel clock go up to 225 instead of 165 that it is on the DVI port. I don't know if it's using the same chip for both ports. It's an old monitor.

                        Sunspark I am happy with my new one monitor hdmi setup. I dont like the white of my white LED monitor, but i think it will be normal in a few months, my brain/eyes will learn to accept it. My old monitor goes back to my friend to whom i gifted it.

                        dev