- Edited
If you don't see the cpu overclock and other features in bios, then I don't know what is going on. Here is the test chart and instructions on how to use it from another forum member:
If you don't see the cpu overclock and other features in bios, then I don't know what is going on. Here is the test chart and instructions on how to use it from another forum member:
you have same laptop ( lenovo 7i ) as @photon78s ?
Is the experience still pleasant when you try gaming or anything that activates the dGPU while you MUX bios settings is still in "dynamic"?
With ditherig, did you use the "identify GPU by questions..." feature? You may have to do that to make sure ditherig is correctly working. From this post: https://ledstrain.org/d/665-ditherig-straw-poll/31
Hey there I wanted to reach out about the Intel Arc A770. I recently built a second computer in order to test out different GPUs and operating systems, so I don't mess with my current working safe PC.
Has anyone else looked into this Intel Arc A770 card to see if it can reduce symptoms by itself for different OS's? I am thinking of purchasing one to test out for Windows 11 and different versions of Linux. So far, my second PC that has an AMD 5700 XT still gives me the same eyestrain on different Linux distros, as well as Windows 11, even though I'm using the same monitor that I do with my safe Windows 10 PC.
I know that specific cards can impact the dithering as well.
Would this be the one to buy? https://www.neweggbusiness.com/product/product.aspx?item=9b-14-930-113
Here's another one on Amazon that might be easier to get a refund in the event that the eyestrain/dithering still persists even after the card is in use: https://www.amazon.com/Graphics-Phantom-256-bit-7680x4320-DisplayPort-Cooling/dp/B0CDM3QK7Q
Does anyone know if it matters which one? Slowly but surely trying to figure this out
whystrainwhy What os version is safe for your experience?
Aquila Windows 10 Pro 22H2
whystrainwhy That's great news. Can you share the message from them ?
Also is it also true for that the whole ARC line from intel doesn't do dithering ?
I am also interested in trying out the Intel Arc. However, I find the term 'by default' a bit confusing. In my experience, we often have more issues with drivers than with the hardware itself. Even if dithering is enabled/disabled on hardware by default, it might be possible to change this setting through the driver. This raises a question about Intel's response: are they considering the role of the driver in their answer, or are they only referring to the default settings of uninitialized hardware?
WhisperingWind from[1]: "For a normal case of SDR desktop (8bpc), dithering is enabled only when we know that the panel is of <8bpc. (i.e. 6bpc)"
[1]end of page: https://community.intel.com/t5/Graphics/how-to-disable-dithering-6bit-display/m-p/1572797
This is indeed the case for my pc: i5-12450H , Intel UHD Graphics Xe (driver v. 31.0.101.5537), Windows 11 23H2, 8-bit monitor.
Ditherig.exe does nothing for my graphics card. The writing to the register is not performed because there is no dithering. It seems that dithering is disabled by default, and the driver doesn't enable it in my case.
Out of curiosity, I added logging to ditherig app (https://ledstrain.org/d/1001-ditherig-is-open-source-on-github).
Here is an explanation of how to read the log:
RegisterValue - the value read from the register.
RegisterDataFromDB - bits that need to be set to 0 in the register to disable dithering. The writing is done using a mask to avoid overwriting bits that are not related to dithering.
NewRegisterValue - the new calculated value to be written to the register in order to disable dithering; If it is equal to the value that was read from the register, then no writing occurs.
The contents of the log file:
Address=603c000000 RegisterAddress=70030 Address+RegisterAddress=603c070030 RegisterValue=4000000 RegisterDataFromDB=0 RegisterMaskFromDB=1c NewRegisterValue=4000000
There is no need to update the register with the value 'NewRegisterValue' because it is already equal to 'RegisterValue'
Address=603c000000 RegisterAddress=71030 Address+RegisterAddress=603c071030 RegisterValue=0 RegisterDataFromDB=0 RegisterMaskFromDB=1c NewRegisterValue=0
There is no need to update the register with the value 'NewRegisterValue' because it is already equal to 'RegisterValue'
Address=603c000000 RegisterAddress=72030 Address+RegisterAddress=603c072030 RegisterValue=0 RegisterDataFromDB=0 RegisterMaskFromDB=1c NewRegisterValue=0
There is no need to update the register with the value 'NewRegisterValue' because it is already equal to 'RegisterValue'
Address=603c000000 RegisterAddress=73030 Address+RegisterAddress=603c073030 RegisterValue=0 RegisterDataFromDB=0 RegisterMaskFromDB=1c NewRegisterValue=0
There is no need to update the register with the value 'NewRegisterValue' because it is already equal to 'RegisterValue'
When I enabled Auto Color Management (by default, ACM was disabled), I got the following entry in the log:
Address = 603c000000 RegisterAddress = 70030 Address + RegisterAddress = 603c070030 RegisterValue = 4000110 RegisterDataFromDB = 0 RegisterMaskFromDB = 1c NewRegisterValue = 4000100
We should update the register with the value 'NewRegisterValue' because it is not equal to 'RegisterValue'. The updating was successful.
The register value 0x4000110 in binary representation is 0100000000000000000100010000. The fifth bit is set to 1. According to the ditherig database, this is Spatial dithering. Its value in the database is 0x00000010 (00000000000000000000000000010000), i.e., the very same fifth bit.
No good user reports about intel arc yet?
It might depend on the vendor, but my Asrock ARC A770 doesn't dither by default in Windows 11 (if ACM is turned off).
autobot does it solve/improve that
nope
Even safe win10 1809 build didn't solve that. tbh laptop's screen could be reason but I sold laptop half-year ago, only now I understood issue could be in:
1) screen (noticable pixel-inversion especially in all new screens I tested)
2) motherboard/CPU/GPU (some users noted swithing motherboard solve eye-strain, some users told only CPU (amd 5600g to 5700g) switch give extra eye-strain, and I myself got strain using rtx20 and newer series over gtx10 line keeping exact same PC components)
I dont think an OS will do dither at software level, I only know some monitors will do dither at hardware level which hurt eyes.