Custom Resolution Utility (CRU)

[ToastyX]

(03-27-2023 04:42 PM)sebastian.f Wrote:  M32U was with DP cable and the TV has only HDMI 2.1

I dont have the M32U anymore but i have make some screenshots from cru before.

4k 144hz 8bit were great for me with DSR. But when iam set this DSR is not showing directly. I can try to restart or using cru reset64.exe.

edit: i have test 100hz, 4.2.0, 8bit but DSR is not showing :-(

I need you to export a file for the TV using CRU and post it here. 4:2:0 probably won't work with DSR either. Try RGB and YCbCr 4:4:4.

[ToastyX]

(03-27-2023 05:07 PM)Just_Chert Wrote:  The thing is I try to add or edit a hertz frequency higher than 75 hertz, but the hertz profiles display in Windows 10 just does not change, just static display 4 profiles and it is 50/59/60/75 hertz, CRU settings are just ignored

What GPU? You said NVIDIA AMD. You should read the part about pixel clock limits in the first post.

[Just_Chert]

(03-28-2023 01:02 AM)ToastyX Wrote:  

(03-27-2023 05:07 PM)Just_Chert Wrote:  The thing is I try to add or edit a hertz frequency higher than 75 hertz, but the hertz profiles display in Windows 10 just does not change, just static display 4 profiles and it is 50/59/60/75 hertz, CRU settings are just ignored

What GPU? You said NVIDIA AMD. You should read the part about pixel clock limits in the first post.

I have an RX 470 GPU and the latest amd driver at the time of writing this post, also the monitor and GPU are connected via HDMI 1.4, hence I need to add an extension unit for hdmi manually which would increase the frequency limit from 165mhz I understand correctly?

[sebastian.f]

(03-28-2023 01:02 AM)ToastyX Wrote:  

(03-27-2023 04:42 PM)sebastian.f Wrote:  M32U was with DP cable and the TV has only HDMI 2.1

I dont have the M32U anymore but i have make some screenshots from cru before.

4k 144hz 8bit were great for me with DSR. But when iam set this DSR is not showing directly. I can try to restart or using cru reset64.exe.

edit: i have test 100hz, 4.2.0, 8bit but DSR is not showing :-(

I need you to export a file for the TV using CRU and post it here. 4:2:0 probably won't work with DSR either. Try RGB and YCbCr 4:4:4.

i have upload the file here: https://drive.google.com/file/d/1Rswxx0p...sp=sharing

I have also test Rgb and 4:4:4 before i set 4:2:0
Thanks for your help.

[ToastyX]

(03-28-2023 09:02 AM)sebastian.f Wrote:  i have upload the file here: https://drive.google.com/file/d/1Rswxx0p...sp=sharing

I have also test Rgb and 4:4:4 before i set 4:2:0
Thanks for your help.

That's not the full EDID. The extension blocks are missing. Does CRU not show the extension blocks?

[ToastyX]

(03-28-2023 08:56 AM)Just_Chert Wrote:  I have an RX 470 GPU and the latest amd driver at the time of writing this post, also the monitor and GPU are connected via HDMI 1.4, hence I need to add an extension unit for hdmi manually which would increase the frequency limit from 165mhz I understand correctly?

No, it already has an HDMI data block. "AMD/ATI's driver also listens to the maximum TMDS clock in the "HDMI support" data block. Make sure it's enabled and set to 340 MHz."

[Just_Chert]

(03-28-2023 09:55 AM)ToastyX Wrote:  

(03-28-2023 08:56 AM)Just_Chert Wrote:  I have an RX 470 GPU and the latest amd driver at the time of writing this post, also the monitor and GPU are connected via HDMI 1.4, hence I need to add an extension unit for hdmi manually which would increase the frequency limit from 165mhz I understand correctly?

No, it already has an HDMI data block. "AMD/ATI's driver also listens to the maximum TMDS clock in the "HDMI support" data block. Make sure it's enabled and set to 340 MHz."

Thank you very much, I have increased the TMDS clock to 340 mhz and now I can raise the hertz frequency above 75 hertz on my monitor

P.S My monitor can hold frequency 80 hertz

[sebastian.f]

(03-28-2023 09:53 AM)ToastyX Wrote:  

(03-28-2023 09:02 AM)sebastian.f Wrote:  i have upload the file here: https://drive.google.com/file/d/1Rswxx0p...sp=sharing

I have also test Rgb and 4:4:4 before i set 4:2:0
Thanks for your help.

That's not the full EDID. The extension blocks are missing. Does CRU not show the extension blocks?

no the field is empty :-(

[izy]

(03-20-2023 04:21 AM)ToastyX Wrote:  

(03-17-2023 10:19 PM)izy Wrote:  Thanks for the reply , that is what i thought too but i had to be sure, i see no reason for DL on the monitor but in the manual says its DL (in the specs only says DVI-D) and I was wondering if indeed its DL if i could get an higher OC because of the higher bandwidth.
I was not sure about the tearing as i am not having tearing at 60hz but i am having it at 75hz and more noticeable if i cap the fps at 75fps, using like 72hz , 73hz without altering CRU timings has less tearing and thats why i was confused.

Edit: pic with the back of the board , seems that it has the pins for DVI-D DL soldered if i am not wrong:
https://i.ebayimg.com/images/g/1OoAAOSwE...-l1600.jpg
https://i.ebayimg.com/images/g/p5MAAOSwb...-l1600.jpg

You shouldn't cap the frame rate to the refresh rate. That's the worst thing you can do for tearing because you'll get a jiggling line. Tearing looks bad when the frame rate is close to the refresh rate. You want the frame rate to be as high as possible away from the refresh rate. If that's not achievable, then at least cap it to something a few frames below the refresh rate. Capping the frame rate to 70 FPS at 75 Hz will look better because the tearing won't be in one spot. The only way to avoid tearing completely is to use vsync, but that will add lag.

Most 60 Hz monitors are hard-coded to reject anything beyond 75-85 Hz. Using a dual-link DVI cable won't change what refresh rates the monitor will accept. The monitor and GPU have no way of knowing if you're using a single-link or dual-link cable. The GPU always sends a single-link signal up to 165 MHz pixel clock and a dual-link signal beyond 165 MHz no matter what cable is being used. The patcher raises that to 230 MHz. If the monitor actually supports dual-link DVI, then you won't need the patcher beyond 165 MHz. If the monitor only supports single-link DVI and the GPU sends a dual-link signal, the monitor will ignore the other link and the resolution will have a blocky look with half the pixels missing unless you use the patcher to send a single-link signal. That 165 MHz switchover is exact by the way, so anything beyond that is a monitor limitation.

Thanks for explanation.

[PLU]

(03-26-2023 09:43 PM)ToastyX Wrote:  That's all you need to do to add the resolution. Make sure to delete the old resolution in the other extension block so that doesn't take effect.

Ok so that was the issue and now it's applying, however if I edit the vertical blanking until it downclocks or use CVT-RB(2) it can go down to 200 Hz but the monitor starts to perform really poorly. There's a noticeable input delay and the refresh rate definitely isn't 165 Hz even if it's reported as such. I can't say for sure but it feels and looks like it's just 60 Hz. Even the UFO test says it's 165 Hz but maybe it's just reading what Windows is reporting.
I tried copypasting my default 165 Hz timings (that trigger max VRAM clock) to make sure what I'm editing actually works and yes, it does perform as it should.

This is how CRU looks by default, I copy the top resolution timings, delete the extension block and add a new DisplayID 2.0 one with the pasted timings and then edit them. If I apply that and restard I only have two selectable refresh rates in Windows: 60 Hz (I'm assuming this is the detailed resolution in the main window of CRU at the top) and the 165 Hz one I created.