I have been asking a lot of questions in this thread Yamakasi Catleap Q270 (100hz guaranteed).
From all the responses will still need confirmations to:
1. If the monitor is receiving DVI-DL signal from GPU DVI transmitter which is limited to 9.9 Gbit @330 MHz (with overhead 8b/10b) then the monitor refreshes it to 120Hz.
2. We simply tell the OS that the monitor is capable of 2560x1440 @120Hz by modifying the EDID or we overclock the GPU DVI transmitter to 2560x1440 @120Hz = 15.75 Gbit @ 442.37 MHz (with overhead).
Standard DVI-DL transmitter 9.9 Gbit @330 MHz http://store.nvidia.com/DRHM/store?Action=DisplayProductDetailsPage&SiteID=nvidia&Locale=en_US&Env=BASE&productID=227587600&resid=T5AIGgoHAtQAAAoFBWwAAAAI&rests=1334839321047
I don't think it's possible to overclock GPU DVI-DL transmitter (TMDS and clock generator) beyond 330MHz as much as we can not overclock the monitor processor (PCB) designed for 60Hz to 120Hz @2560x1440.
Originally Posted by HyperMatrix
Originally Posted by Ken1649
Do you happen to know if the monitor is receiving 133Hz or just the limit of the graphics card? And does it play well with the games at that refresh rate? And if you don't mind to upload the monitor .inf of this 133Hz?
The highest I actually use to "Play" is around 124hz because it's fully perfect without any issues even after extended periods. Why 124 and not just 120hz? Well..as we go up higher, it has trouble actually putting out the refresh rate it's supposed to. For example, a 120hz display will put out 119-121hz. But this monitor, set to 120hz, will put out 115-119hz. So by going up to 123-124hz, I end up with an active 119hz-121hz.
And yes, the refresh rate will act and behave properly, IF you follow the OC guide in my signature below. Otherwise half of your games will revert back to 60hz when you play them. The limitation, even at 537mhz pixel clock didn't come from the card. At that refresh rate, your horizontal refresh rate is at 199khz. It's the 200khz which is the limit (I'm assuming from the PCB...because even at 200khz...that's ridiculously high. lol). But realistically...running a 60hz panel at nearly 222% of its stated specifications is scary. It follows the standard rule of Overclocking. Find your maximum OC, then bring it down a bit for long-term stability.
As for the inf, I already mentioned going through my youtube guide linked in my sig! There is a downloadable package in the video description that contains all tools and drivers, along with video guidance on how to use them. So don't worry about anything. Just get your hands on a B series monitor and you'll be set.
Sorry if my questions were vague and I have been thinking how to make it easier to understand.
1. We all know that HD movies are mostly 24 FPS. Say, we watch it on 1920x1080 @120Hz monitor, it will refresh it to 120Hz = 120 FPS right? We also know that rendering movie can be done by GPU (hardware acceleration) or by software, is this correct? We don't have to do anything because the monitor EDID supports 1920x1080 @120 Hz. The display processor is also capable of 120Hz at that resolution. We can also choose the video quality is thru the display processor instead of graphics driver (GPU). From all the options we are still well within the DVI-DL bandwidth limit but it has nothing to do with GPU if we select software to render these movies, am I wrong?
2. The supported EDID of this Korean panel is 2560x1440 @60Hz right? So in order for the OS (Win 7) to recognize the panel capable of 2560x1440 @120Hz, we modified the EDID. Now, back to this HD 24 FPS movie, if we let the software to render then send the signal to monitor thru DVI-DL, the monitor will still refresh it to 24 x 5 = 120 FPS = 120 Hz. So is this all we are doing by telling the OS that the plugged in monitor is capable of 2560x1440 @120 Hz?
Let's leave gaming alone, because it's so confusing if we mix it with this DVI-DL bandwidth limitations, because while playing games @200 FPS on a 60 Hz capable monitor we are still seeing 200 FPS on the counter.
If what I am thinking is flaw, please kindly explain.
Edited by Ken1649 - 4/19/12 at 7:09am