|
Custom Resolution Utility (CRU)
|
|
12-26-2015, 03:14 AM
Post: #1895
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-24-2015 03:58 PM)zamar19 Wrote: I exported EDID override inf in CRU and installed to Win 10 64-bit with Driver Sig Enf. Off, then rebooted. I can see in Reg: SEK0030/key_name/Device Parameters (EDID)/EDID_OVERRIDE (0,1). But it looks like Win 10 only reads main EDID section, and doesn't read 0 and 1 overrides. If I replace EDID key with 0 and 1 keys, OS recreates it on reboot. I was trying the Override to get 4:4:4 chromo at 4K@30Hz, since its not listed in main EDID, but the pic test still shows 4:2:2. So it looks like either Win 10, or latest FirePro driver, or both can't handle EDID Overrides. The driver just reads and saves to Registry main EDID from EEPROM without the extension, despite its part of the factory EDID. Why this happens, and how to fix?The EDID in the registry is always the base block only. This is why I will need to use driver-specific methods to read the default extension block. This doesn't mean the extension block override isn't working. "EDID" = currently active base block "0" = base block override "1" = extension block override "EDID" should match "0" if the override is working. |
|||
|
|
« Next Oldest | Next Newest »
|