AMD/ATI Pixel Clock Patcher

[ToastyX]

(07-17-2021 04:01 PM)myresolutionis Wrote:  I see, would you mind me asking then why the AMD driver and CRU doesn't accept that value when I can do the same thing with Nvidia (GTX 1080Ti) and it works just fine? I went even as far as trying identical settings

https://i.imgur.com/HJHtaQt.jpg

and NV accepted them just fine. Does NV automatically use that same extension block as you use in CRU when one enters these high values? Apologies if this question doesn't make any sense, I don't have much insight in this.

Also, one more...are there any implications to adding a resolution to an extension block?

CRU does accept the value if you use a DisplayID extension block. CRU is an EDID editor, and EDID detailed resolutions can't represent pixel clocks greater than 655.35 MHz, but DisplayID can. DisplayID detailed resolutions work the same way but allow higher values. NVIDIA and AMD custom resolutions are driver-specific functions and not related to the EDID at all. Also, don't use GTF because that increases the pixel clock and wastes bandwidth. Use CVT reduced blanking. If you're using DisplayPort 1.3/1.4, anything beyond 1080 MHz pixel clock will use 6 bpc color. AMD's driver might be rejecting anything beyond 1080 MHz. AMD's custom resolutions have also been known to reject resolutions that work fine with CRU.