NVIDIA Pixel Clock Patcher

[ToastyX]

(11-01-2015 11:08 PM)niciuffo Wrote:  I cannot, in any way, go over the 165MHz limit.

What happens when you try to go over 165 MHz? Is the driver not allowing it ("test failed" message) or is the TV not displaying it?

(11-01-2015 11:08 PM)niciuffo Wrote:  I am wondering if this is the TV's fault, since it's running HDMI 1.2 it can't physically accept an input with a pixel clock higher than 165MHz.

Hardware limits are not exact like that. It's usually possible to go higher than 165 MHz unless there's a new driver limit that I don't know about. If it's a driver limit, 165.00 MHz will work but 165.01 MHz will not. If the TV has a pixel clock limit, it won't be exact like that.

(11-01-2015 11:08 PM)niciuffo Wrote:  I managed to get the TV to 75Hz using these settings:
[img]

Those values are impossible because the total includes the active + front porch + sync width. It's probably reducing the sync width without telling you.

(11-01-2015 11:08 PM)niciuffo Wrote:  Setting the front porch to 0 on both Horizontal and Vertical fields, I can successfully test a resolution with a higher pixel clock, although I can't apply it. I'm not even sure it's displaying more than 60Hz. Maybe, since it's an invalid value, the driver just defaults it to 60Hz.

Technically, 0 front porch values are possible, but the driver might not be handling it correctly. The TV should tell you what refresh rate it's actually receiving in the OSD.

(11-01-2015 11:08 PM)niciuffo Wrote:  Is there any setting I can tweak to lover the pixel clock (if that's the issue), or should the TV just work with an higher pixel clock?

The only way to reduce the pixel clock without reducing the refresh rate is to reduce the totals. The totals include the front porch and sync width, so reducing those might allow you to reduce the totals further.