Custom Resolution Utility (CRU)
|
12-24-2015, 03:58 PM
(Last edited: 12-25-2015, 05:07 AM by zamar19)
Post: #1890
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
@ToastyX
Quote:AMD cards are normally limited to 297 MHz, which is just enough for 3840x2160 @ 30 Hz. That's assuming 4:4:4 output and 8-bit color. So why 4:4:4 test images show 4:2:2 on this monitor at 4K resolution, despite included in its EDID? Can it be DP-to-HDMI1.4 4K adapter chipset limitation? Actually, most current Radeon and FirePro cards support one or multiple 4K@60Hz out via DP1.2, of course older cards only support 4K@30Hz via DP1.0 or HDMI1.4. To my understanding, Nvidia Quadro cards and drivers also have 10-bit pixel out support option, but other Nvidia models don't, despite offering several color depth options in Nvidia CC DFP Properties. I tried adding in CRU Custom Extension Block - HDMI Profile, but it only offers YCbCr 4:4:4, but no FullRGB 4:4:4. For this monitor, YCbCr 4:4:4 option is not available at 4K@30Hz in FirePro CC for my GPU, only FullRGB 4:4:4 out, which is default color space for the monitor. Why no FullRGB 4:4:4 option in Extension? 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? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 100 Guest(s)