Post Reply
 
Thread Rating:
  • 7 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Custom Resolution Utility (CRU)
12-27-2018, 05:00 PM
Post: #3711
RE: Custom Resolution Utility (CRU)
(12-25-2018 02:56 AM)ReaverG Wrote:  I'm starting to read about using this CRU, I have overclocked my monitor in the past to 75hz but I think it was a lower res. But now I am on 1920x1080 native res, I just used nvidia custom res before. I have a Asus VS248H and I was just wondering about the timings? I see so many videos out there about standard or reduced which do you think is best for this monitor? I also have a amd card now and when I tried to overclock it at 1080p it got to 66hz with manual timings I didn't know which setting to try it had cvt, cvt reduced blanking, gtf and dtm. I also got to 74hz but it was a blurry pix elated picture. I would like to use this CRU correctly I assume with proper settings I could get to 75hz or maybe higher just want the safest easiest way. I'll try reading some more but a recommendation for it be awesome.
If you're using DVI, pixelation beyond 66 Hz sounds like a single-link DVI monitor receiving a dual-link DVI signal. Read the part about pixel clock limits. You can either use "LCD reduced" to keep the pixel clock under 165 MHz, or use the pixel clock patch. Other than that, the timing parameters don't matter much as long as it works.
Find all posts by this user
Quote this message in a reply
12-27-2018, 05:39 PM
Post: #3712
RE: Custom Resolution Utility (CRU)
(12-27-2018 05:00 PM)ToastyX Wrote:  
(12-25-2018 02:56 AM)ReaverG Wrote:  I'm starting to read about using this CRU, I have overclocked my monitor in the past to 75hz but I think it was a lower res. But now I am on 1920x1080 native res, I just used nvidia custom res before. I have a Asus VS248H and I was just wondering about the timings? I see so many videos out there about standard or reduced which do you think is best for this monitor? I also have a amd card now and when I tried to overclock it at 1080p it got to 66hz with manual timings I didn't know which setting to try it had cvt, cvt reduced blanking, gtf and dtm. I also got to 74hz but it was a blurry pix elated picture. I would like to use this CRU correctly I assume with proper settings I could get to 75hz or maybe higher just want the safest easiest way. I'll try reading some more but a recommendation for it be awesome.
If you're using DVI, pixelation beyond 66 Hz sounds like a single-link DVI monitor receiving a dual-link DVI signal. Read the part about pixel clock limits. You can either use "LCD reduced" to keep the pixel clock under 165 MHz, or use the pixel clock patch. Other than that, the timing parameters don't matter much as long as it works.
Thanks for the reply, I looked at the monitor it does have a dual link dvi port and so does the gpu but the monitor came with a single link dvi cable and that is what I am using. I will read those parts you told me to read. If I just get a dual link cable would that be better, could I achieve higher Hz than the single link on top of using the lcd reduced?
Find all posts by this user
Quote this message in a reply
12-27-2018, 10:10 PM
Post: #3713
RE: Custom Resolution Utility (CRU)
(12-27-2018 05:39 PM)ReaverG Wrote:  Thanks for the reply, I looked at the monitor it does have a dual link dvi port and so does the gpu but the monitor came with a single link dvi cable and that is what I am using. I will read those parts you told me to read. If I just get a dual link cable would that be better, could I achieve higher Hz than the single link on top of using the lcd reduced?
No, the monitor has single-link DVI. You can't tell by looking at the port. The GPU will always send a dual-link signal beyond 165 MHz, so you have to either keep the pixel clock under 165 MHz or patch the driver to go higher with DVI. The other option is to use HDMI to avoid those limitations. Chances are the monitor has a limit somewhere between 74-85 Hz no matter what the cable.
Find all posts by this user
Quote this message in a reply
12-28-2018, 02:35 AM (This post was last modified: 12-28-2018 08:34 PM by ReaverG.)
Post: #3714
RE: Custom Resolution Utility (CRU)
(12-28-2018 02:35 AM)ReaverG Wrote:  No, the monitor has single-link DVI. You can't tell by looking at the port. The GPU will always send a dual-link signal beyond 165 MHz, so you have to either keep the pixel clock under 165 MHz or patch the driver to go higher with DVI. The other option is to use HDMI to avoid those limitations. Chances are the monitor has a limit somewhere between 74-85 Hz no matter what the cable.

Alright I changed to hdmi and on lcd standard I got to 70hz, lcd native I believe I got to 66hz and on reduced I got to 75hz. If I use the extension block can I achieve higher yet? I only ask cause if I use it and nothing changes I have to find out how to reverse the extension patch. I have a amd rx580. If not I will just stay at reduced 75hz. I always thought dvi was better than hdmi maybe that was old hdmi cables I don't know guess I learned something from this.
Find all posts by this user
Quote this message in a reply
12-29-2018, 01:07 AM
Post: #3715
RE: Custom Resolution Utility (CRU)
So I'm attempting to overclock my macbook pro 2017 display using CRU but I'm coming up against some hurdles, basically I need to keep the pixel clock constant or it rapidly gets black screened. This means the best I can get is 61Hz (up from 60hz) by lowering the padding but as you can understand this is a pretty useless overclock. Is there anything else I can do to increase the pixel clock?
Find all posts by this user
Quote this message in a reply
12-29-2018, 07:40 PM
Post: #3716
RE: Custom Resolution Utility (CRU)
Could I use 120 hz in 800x600 in 60 HZ native? This have less bandwidth than 1080p. is it true?
Find all posts by this user
Quote this message in a reply
01-03-2019, 07:17 PM
Post: #3717
RE: Custom Resolution Utility (CRU)
(12-28-2018 02:35 AM)ReaverG Wrote:  Alright I changed to hdmi and on lcd standard I got to 70hz, lcd native I believe I got to 66hz and on reduced I got to 75hz. If I use the extension block can I achieve higher yet? I only ask cause if I use it and nothing changes I have to find out how to reverse the extension patch. I have a amd rx580. If not I will just stay at reduced 75hz. I always thought dvi was better than hdmi maybe that was old hdmi cables I don't know guess I learned something from this.
Those are the same refresh rates you would get with single-link DVI with the 165 MHz pixel clock limit. You shouldn't have to add an extension block if the monitor supports HDMI because it should already have one. If not, you can add one manually, and that might help you go beyond the 165 MHz pixel clock limit. The extension block is not a patch, and everything is easily reversible by following the instructions.
Find all posts by this user
Quote this message in a reply
01-03-2019, 07:18 PM
Post: #3718
RE: Custom Resolution Utility (CRU)
(12-29-2018 01:07 AM)lcass Wrote:  So I'm attempting to overclock my macbook pro 2017 display using CRU but I'm coming up against some hurdles, basically I need to keep the pixel clock constant or it rapidly gets black screened. This means the best I can get is 61Hz (up from 60hz) by lowering the padding but as you can understand this is a pretty useless overclock. Is there anything else I can do to increase the pixel clock?
Sounds like it's not overclockable.
Find all posts by this user
Quote this message in a reply
01-03-2019, 07:19 PM
Post: #3719
RE: Custom Resolution Utility (CRU)
(12-29-2018 07:40 PM)Dannypa Wrote:  Could I use 120 hz in 800x600 in 60 HZ native? This have less bandwidth than 1080p. is it true?
That depends on the monitor. The monitor would have to support 120 Hz regardless of the bandwidth.
Find all posts by this user
Quote this message in a reply
01-08-2019, 06:02 AM
Post: #3720
RE: Custom Resolution Utility (CRU)
Those are the same refresh rates you would get with single-link DVI with the 165 MHz pixel clock limit. You shouldn't have to add an extension block if the monitor supports HDMI because it should already have one. If not, you can add one manually, and that might help you go beyond the 165 MHz pixel clock limit. The extension block is not a patch, and everything is easily reversible by following the instructions.
[/quote]
Sounds good I will give it a shot.
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 28 Guest(s)