Custom Resolution Utility (CRU)

[Stylook]

Toasty,

Would like to ask, I just bought monoprice cable DVI-Dual link, very thick, thinking it would perform better. Reading from many reviews recommend it. After I got it, it's worst than the DVI-D cable that came with the Qnix monitor. Now I got very, very thick cable that is useless maybe to hang myself, if it can even bend, lol. Any ideas why the thick supposedly better quality cable is not doing better than the factory cable? I felt very disappointed.

Thanks.

[ToastyX]

I've heard the Monoprice cables don't usually help with the QNIX/X-Star monitors, but they do help with the Catleap/Overlord monitors. When pushing the hardware to the limits, who knows what can affect them.

[Stylook]

(10-07-2013 03:39 PM)ToastyX Wrote:  I've heard the Monoprice cables don't usually help with the QNIX/X-Star monitors, but they do help with the Catleap/Overlord monitors. When pushing the hardware to the limits, who knows what can affect them.

Urgh, I should have read some of the overclocker.net reviewers, it's true that it's not really giving any better results with some of the Qnix/Xstar. Sigh.

[Foobar]

Hullo!

Thanks for a great utility. I've used it successfully on several monitors.

Now I'm trying to use it on a Samsung S27C750P. This has been confirmed by reviewer (NCX over at WeCraveGames forums) to do 75hz (Nvidia driver settings with standard timings).
However I cannot reproduce it on a ATI HD3650 with catalyst 12.6. The monitor input seems very sensitive to input timing. Whenever I go over 71hz and stay under 165mhz the screen image gets distorted in a way that is typical for timing issues.

Supposedly this monitor can do over 165mhz but all custom resolutions I make that have bandwidth over 165 wont show up in the refresh rate menus. I have tried the pixel clock patcher, but they still will not show up and I cannot select them.

Any ideas?

[ToastyX]

NCX used timing parameters that went over 165 MHz, which requires HDMI 1.3 support or the pixel clock patch. The patch has no effect on anything older than the 5000 series, and older cards don't fully support HDMI 1.3 either. There isn't a way to get past 165 MHz with your video card.

(10-09-2013 09:55 AM)Foobar Wrote:  Whenever I go over 71hz and stay under 165mhz the screen image gets distorted in a way that is typical for timing issues.

Does that happen with the "LCD reduced" timing option? There isn't much room for tweaking at 75 Hz, but you might be able to get 72 Hz working.

First, I would check if the horizontal parameters are causing the problem by leaving the horizontal at standard and adjusting the vertical so it looks like this:

H: 1920 48 32 80 160 2080
V: 1080 3 5 12 20 1100

If that doesn't work, I would leave the vertical at standard while adjusting the horizontal so it looks like this:

H: 1920 32 40 48 120 2040
V: 3 5 29 37 1117

Some monitors will only work with both horizontal and vertical reduced, which "LCD reduced" already does. You can also try reducing the horizontal a little more while adjusting the vertical like this:

H: 1920 24 32 32 88 2008
V: 1080 3 5 10 18 1098

If none of those combinations work, it might not be possible to get 72 Hz below 165 MHz with that monitor.

At 75 Hz, there isn't much you can change. If "LCD reduced" doesn't work, all you can do is try reducing the horizontal more while adjusting the vertical like this:

H: 1920 24 24 32 80 2000
V: 1080 3 5 12 20 1100

[Foobar]

(10-09-2013 12:56 PM)ToastyX Wrote:  NCX used timing parameters that went over 165 MHz, which requires HDMI 1.3 support or the pixel clock patch. The patch has no effect on anything older than the 5000 series, and older cards don't fully support HDMI 1.3 either. There isn't a way to get past 165 MHz with your video card.

I use a DVI to HDMI converter. And it is indeed detected as DVI. But I guess its a single link DVI converter or < HDMI 1.3 converter that is hardware limited to 165 or something?

Quote:Does that happen with the "LCD reduced" timing option? There isn't much room for tweaking at 75 Hz, but you might be able to get 72 Hz working.

Yes! Thank you! I managed to get 71.930hz (aiming for 71.928hz) working by leaving the vertical and tweaking the horizontal a bit:
H: 1920 40 40 48 128 2048
V: 3 5 29 37 1117

Going to try the 75hz values you suggested. Exactly 165mhz Although 75hz its not that important. I'm mainly using this old rig for video anyway and when I got that last 1hz its finally smooth. Thanks again!

[ToastyX]

(10-09-2013 07:18 PM)Foobar Wrote:  I use a DVI to HDMI converter. And it is indeed detected as DVI. But I guess its a single link DVI converter or < HDMI 1.3 converter that is hardware limited to 165 or something?

DVI/HDMI adapters are passive. The limit is in the driver, but older cards are handled differently. I wasn't able to find an easy way around the limit for older cards.

[ptol]

Hi

I'm thinking in buying a monitor ASUS VG248QE

Do you think that with CRU will I be able to put 1920x1080 in 75hz or say 120 hz (playing games in 2D mode), when connected to my XFX 7950 ?
The monitor has a dual DVI-D, and the XFX 7950 a dual DVI-I...

Tks

[MS-DOS]

Foobar
Try these for 75.000:
H: 32 32 32 96 2016
V: 3 4 4 11 1091

And these for 71.928:
H: 32 40 48 120 2040
V: 3 5 5 13 1093

Both worked on already two of my monitors. Thanks to Toasty for providing 75.000 timings.

ToastyX
What's the lowest vertical total, for 5000 Radeons, where clocks still go down in idle?

[ToastyX]

(10-10-2013 02:32 PM)ptol Wrote:  I'm thinking in buying a monitor ASUS VG248QE

Do you think that with CRU will I be able to put 1920x1080 in 75hz or say 120 hz (playing games in 2D mode), when connected to my XFX 7950 ?
The monitor has a dual DVI-D, and the XFX 7950 a dual DVI-I...

DVI-D vs. DVI-I doesn't matter. It just needs to be dual-link DVI.

120 Hz should work out of the box, and the ASUS includes 85 Hz as well. You can add 75 Hz with CRU if you need it.

(10-11-2013 12:44 AM)MS-DOS Wrote:  What's the lowest vertical total, for 5000 Radeons, where clocks still go down in idle?

That depends on the refresh rate. AMD/ATI GPUs seem to want the "LCD standard" vertical total. You might be able to go one or two lower than that. Horizontal can be reduced without affecting idle clocks.