Overclock.net › Forums › Components › Monitors and Displays › Yamakasi Catleap Monitor Club
New Posts  All Forums:Forum Nav:

Yamakasi Catleap Monitor Club - Page 125

post #1241 of 11297
Just a question before I jump on a Catleap Q270 Multi for $490. Is the input lag noticeable? I want to use it for both my main computer monitor and my PS3.
post #1242 of 11297
HyperMatrix - you're a god amongst overclockers to FINALLY PROVE that you can OC RAMDAC (I believe subsequent posts of other forums found through google say that it's impossible).

Scribby - post his guide (the RAMDAC part) to the front page?

Hypermatrix - willing to go 'even further beyond' - by that I mean reach 120Hz?
post #1243 of 11297
Quote:
Originally Posted by xdemi View Post

HyperMatrix - you're a god amongst overclockers to FINALLY PROVE that you can OC RAMDAC (I believe subsequent posts of other forums found through google say that it's impossible).
Scribby - post his guide (the RAMDAC part) to the front page?
Hypermatrix - willing to go 'even further beyond' - by that I mean reach 120Hz?

Originally Posted by HyperMatrix

Did the method work for you?
And I've tried 120hz. Just upping the number in Powerstrip doesn't take it any higher than 101hz with a >408mhz ramdac. I tried forcing a change to 1920x1080 resolution with a 120hz refresh rate, which only requires a 368mhz ramdac, but for some reason it has trouble accepting the resolution change. Not sure what it's due to, specifically. Maybe it'd work on Nvidia cards? I won't know until I get my hands on a couple gtx 680's.

As for any references to ramdac oc'ing, honestly the highest I've seen anyone claim to do is about 420 on an nvidia card. I'm not as knowledgeable as ToastyX when it comes to stuff like this.
post #1244 of 11297
double post.
post #1245 of 11297
Quote:
Originally Posted by HyperMatrix View Post

I hope that works for you. Let me know if it does/doesn't and your experiences. And hey...if I got you 101hz on your Radeon card...feel free to rep me. tongue.gif
I mentioned PowerStrip before: http://www.overclock.net/t/1215866/reviewed-400-2560x1440-ips-no-ag-90hz-achieva-shimian-qh270-and-catleap-q270/1250#post_16639892

The problem is PowerStrip has no way of telling Windows or the video driver about the new refresh rate, so not everything works properly. For instance, moving windows around gets choppier because Aero runs at the wrong frame rate unless the multimedia timer resolution is set to a low value, which happens to be the case when Flash is running in a browser. Also, I found if anything tried to change the refresh rate, the video card would blank out and I had to reboot.

The pixel clock you set in PowerStrip might not be the actual value either. PowerStrip let me set up to 500 MHz, but I found the actual rate stopped changing at around 400 MHz. You can double-click the camera icon next to where it says "Custom" to calculate the actual refresh rate. You're probably running closer to 98 Hz. Also, I found PowerStrip can get confused if there are multiple monitors to the point where it won't even change the rate at all.

You don't have to do any of the steps you mentioned except adding 80-85 Hz first, then switching to it before running PowerStrip, otherwise the monitor might not display 100 Hz properly. The problem is PowerStrip adjusts the signal in real time, and the monitor can't seem to handle the signal changing from 60 Hz to 100 Hz, or maybe it's the video card, I don't know.

I was able to use the Refresh Rate Multitool to verify the refresh rate, but it also had the same problem of running at the wrong frame rate unless the multimedia timer resolution is set low enough. I was able to do that and verified that it really was running at 100 Hz using a camera.

Basically, the PowerStrip solution sort of works, but it's not an ideal solution. The ideal solution is to get AMD to remove the 330 MHz pixel clock limit in the driver when using dual-link DVI and the 288 MHz limit when using DisplayPort so people can use adapters.
Quote:
Originally Posted by xdemi View Post

HyperMatrix - you're a god amongst overclockers to FINALLY PROVE that you can OC RAMDAC (I believe subsequent posts of other forums found through google say that it's impossible).
It's not overclocking the RAMDAC. I still couldn't get past 400 MHz.
post #1246 of 11297
Quote:
Originally Posted by ToastyX View Post

I mentioned PowerStrip before: http://www.overclock.net/t/1215866/reviewed-400-2560x1440-ips-no-ag-90hz-achieva-shimian-qh270-and-catleap-q270/1250#post_16639892
The problem is PowerStrip has no way of telling Windows or the video driver about the new refresh rate, so not everything works properly. For instance, moving windows around gets choppier because Aero runs at the wrong frame rate unless the multimedia timer resolution is set to a low value, which happens to be the case when Flash is running in a browser. Also, I found if anything tried to change the refresh rate, the video card would blank out and I had to reboot.
The pixel clock you set in PowerStrip might not be the actual value either. PowerStrip let me set up to 500 MHz, but I found the actual rate stopped changing at around 400 MHz. You can double-click the camera icon next to where it says "Custom" to calculate the actual refresh rate. You're probably running closer to 98 Hz. Also, I found PowerStrip can get confused if there are multiple monitors to the point where it won't even change the rate at all.
You don't have to do any of the steps you mentioned except adding 80-85 Hz first, then switching to it before running PowerStrip, otherwise the monitor might not display 100 Hz properly. The problem is PowerStrip adjusts the signal in real time, and the monitor can't seem to handle the signal changing from 60 Hz to 100 Hz, or maybe it's the video card, I don't know.
I was able to use the Refresh Rate Multitool to verify the refresh rate, but it also had the same problem of running at the wrong frame rate unless the multimedia timer resolution is set low enough. I was able to do that and verified that it really was running at 100 Hz using a camera.
Basically, the PowerStrip solution sort of works, but it's not an ideal solution. The ideal solution is to get AMD to remove the 330 MHz pixel clock limit in the driver when using dual-link DVI and the 288 MHz limit when using DisplayPort so people can use adapters.
It's not overclocking the RAMDAC. I still couldn't get past 400 MHz.

Works fine for me mate. Up to the 408mhz. After that I noticed it made no change. That's why I left it at 408.

416
post #1247 of 11297
Quote:
Originally Posted by ToastyX View Post

Basically, the PowerStrip solution sort of works, but it's not an ideal solution. The ideal solution is to get AMD to remove the 330 MHz pixel clock limit in the driver when using dual-link DVI and the 288 MHz limit when using DisplayPort so people can use adapters.
It's not overclocking the RAMDAC. I still couldn't get past 400 MHz.

Ah k - what about driver modding? Weren't there groups in the past that modded drivers (I believe they modified inf files mainly)? Or is it much more lower-level than that?

And why would AMD place such limits in the first place anyways? Would having 400MHz as nvidia do be beneficial to them?
post #1248 of 11297
Quote:
Originally Posted by HyperMatrix View Post

Works fine for me mate. Up to the 408mhz. After that I noticed it made no change. That's why I left it at 408.
Interesting. I guess your video card can do a little more. I also hit a limit of around 101 Hz but with different timing parameters. Wonder what NVIDIA users can get.
Edited by ToastyX - 3/22/12 at 1:34am
post #1249 of 11297
Quote:
Originally Posted by xdemi View Post

Ah k - what about driver modding? Weren't there groups in the past that modded drivers (I believe they modified inf files mainly)? Or is it much more lower-level than that?
And why would AMD place such limits in the first place anyways? Would having 400MHz as nvidia do be beneficial to them?
Unless there's an option already built into the driver (which I haven't found), someone would have to modify the driver on a lower level using a debugger, and that would also break code signing.

They probably put in limits when parsing the EDID so the driver doesn't add invalid resolutions or resolutions that the video card can't handle. The problem is they assumed dual-link DVI is 330 MHz (2x165 MHz) since single-link DVI is 165 MHz, and no other monitor has ever pushed that limit. I'm not sure where they got 288 MHz for DisplayPort, but that happens to be just enough to do 1920x1080 @ 120 Hz with CVT-RB timing parameters.
post #1250 of 11297
Hi ive ordered a CATLEAP Q270 SE + tempered glass.
Ive read that some are receiving matte screens?
The only reason i bought this was becouse it was glossy.
How big is the risk for getting a matte?
I ordered on 20th march from green-sum
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Monitors and Displays
Overclock.net › Forums › Components › Monitors and Displays › Yamakasi Catleap Monitor Club