Custom Resolution Utility (CRU)

[Haemato]

(08-02-2015 02:38 AM)ToastyX Wrote:  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.

Ok, good to know. I was just looking for differences between the stock EDID in the projector and the one I created. In the new one I:
1) removed all established timings that weren't 60Hz
2) removed all standard timings except 800x600@120Hz, 1024x768@120Hz, 720p60, 720p120, 800p60 and 800p120
3) swapped out the 1280x800@60Hz detailed timing for the 1280x800@120Hz reduced blanking VESA timing
4) changed monitor name
5) serial number was set to 1, 2, 3 (each board respectively)
6) new EDID had no plain text serial number descriptor
7) new EDID had no Monitor Limits Descriptor
8) just noticed that the old projector had zero extension blocks whereas my new one had 1 that was left blank (all 0x00)

Perhaps #8 is the issue and not the missing Monitor Limits Descriptor. Or maybe the driver didn't like the established timings section being so restrictive. Will be able to experiment more once I get a "write-edid" program written.