Custom Resolution Utility (CRU)
|
08-02-2015, 02:38 AM
Post: #1533
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-02-2015 12:30 AM)Haemato Wrote: According to the Enhanced EDID VESA spec it is required. Specifically states that "A Monitor Range Limits Descriptor must be provided" under section 3.10. A Monitor name descriptor is required as well. Earlier versions of the spec didn't require this (prior to 1.3) so hosts can expect to run into this scenario. It's possible that nvidia is doing a strict interpretation of the spec and thus failing to parse the EDID.EDID version 1.4 does not require a range limits descriptor. Older versions of CRU upgraded the EDID to version 1.4, but this caused problems with the way AMD's driver handled HDMI audio with older GPUs, so I removed the upgrade. EDID version 1.3 says it's required, but not including it doesn't invalidate any of the information in the EDID. I have a monitor that doesn't have a range limits descriptor. Neither AMD nor NVIDIA require a range limits descriptor as far as I have seen. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 65 Guest(s)