Custom Resolution Utility (CRU)

[ToastyX]

(02-14-2020 04:08 PM)Seneral Wrote:  Tried that using CRU properly (deleted all the detailed resolutions) and hit ok, then restart64.exe. Crashed the driver and apparently broke it, radeon software was telling me to reinstall the driver, so I did.

You shouldn't have to reinstall the driver. If the driver crashes while restarting, sometimes it's still disabled after rebooting. Just run restart64.exe again to enable it.

[ToastyX]

(02-14-2020 04:08 PM)Seneral Wrote:  Sure, sorry didn't think of it, here's the full output of xrandr --verbose on the linux rig where it works.
It's this exact LCD with the standard HDMI to MIPI bridge, no audio. It says LS055R1SX03 there, even though CRU says LS055R1SX01, so maybe they silently switched versions in the one year I had it (edit: no, definitely LS055R1SX03, LS055R1SX01 is 6"... guess it makes not much difference but already tells alot about how the board is set up. Might want to try to edit the firmware on the board).
Here's the export of CRU, not sure how this is related to proper EDID. Have failed to parse either of them using an online edid parser, will try offline.

I don't know what "export of CRU" is because CRU doesn't output that format and it's missing the extension block that is shown in your screen shot.

I see the problem now. The HDMI data block is missing the maximum TMDS clock. This causes AMD's driver to limit HDMI to 165 MHz pixel clock, which causes it to ignore all the resolutions. Just import this file: https://www.monitortests.com/download/dat/hdmi.dat

[ToastyX]

(02-14-2020 05:43 PM)joevt Wrote:  I used my script at https://gist.github.com/joevt/32e5efffe3...02579b9529 and edid-decode at https://git.linuxtv.org/edid-decode.git/about/ to examine the EDIDs and make modifications which you can import into CRU (from the modified.bin file). Do you need YCbCr mode? 4:2:2? or 4:2:0?

That will not work. You removed HDMI support, which will make HDMI act like single-link DVI, which is limited to 165 MHz pixel clock.

[benoe]

Hi, I have an AOC C24G1 (AOC2401 - 24G1WG4) monitor and an RX 5700 card and I'm trying to make the RAM clock frequency lower when idle. I have learnt, that at default settings with hdmi, I can set the refresh to 100Hz to achieve this, with displayport 120Hz also works. CRU Display Properties reports 300MHz as Max pixel clock with hdmi and 330 with displayport.

I'm trying to adjust settings with CRU, but I have issues:
I cannot find the fullhd 120Hz settings to edit (to make 120Hz work with hdmi as well) Detailed resolutions list only 60 and 144hz modes.
I cannot set up 144Hz to get the needed result, LCD standard setting provides black screen, adjusting the blanking lines manually sometimes works, but screen seems to be blurry even when the system reports 1080p resolution.

The 144hz resolution has 325Mhz pixel clock, standard sets this to 346.55Mhz. Is it possible that this monitor cannot go this high, and that's why I cannot set the standard setting? Or should I try with better cables maybe?

[ToastyX]

(02-14-2020 08:32 PM)benoe Wrote:  Hi, I have an AOC C24G1 (AOC2401 - 24G1WG4) monitor and an RX 5700 card and I'm trying to make the RAM clock frequency lower when idle. I have learnt, that at default settings with hdmi, I can set the refresh to 100Hz to achieve this, with displayport 120Hz also works. CRU Display Properties reports 300MHz as Max pixel clock with hdmi and 330 with displayport.

I'm trying to adjust settings with CRU, but I have issues:
I cannot find the fullhd 120Hz settings to edit (to make 120Hz work with hdmi as well) Detailed resolutions list only 60 and 144hz modes.
I cannot set up 144Hz to get the needed result, LCD standard setting provides black screen, adjusting the blanking lines manually sometimes works, but screen seems to be blurry even when the system reports 1080p resolution.

The 144hz resolution has 325Mhz pixel clock, standard sets this to 346.55Mhz. Is it possible that this monitor cannot go this high, and that's why I cannot set the standard setting? Or should I try with better cables maybe?

DisplayPort should be able to handle at least 360 MHz, but the monitor might not. You can keep the horizontal reduced and increase only the vertical blanking until it clocks down. If it won't display that correctly, then that's a monitor limitation.

[joevt]

(02-14-2020 08:32 PM)benoe Wrote:  I cannot find the fullhd 120Hz settings to edit (to make 120Hz work with hdmi as well) Detailed resolutions list only 60 and 144hz modes.

HDMI and DisplayPort connections have different EDIDs. Are you looking at the DisplayPort EDID or the HDMI EDID (they might have different product IDs)?

CRU only shows 3 extension blocks. If the detailed timing was on a fourth then it could be missing (usually 3 is enough so I doubt this is the problem). Double-check the EDIDs in Monitor Asset Manager (moninfo.exe).

(02-14-2020 08:32 PM)benoe Wrote:  The 144hz resolution has 325Mhz pixel clock, standard sets this to 346.55Mhz. Is it possible that this monitor cannot go this high, and that's why I cannot set the standard setting? Or should I try with better cables maybe?

The display is not using a standard timing because it won't fit in the allowed range 330 MHz max (CRU should probably rename the timings to GTF, CVT, CVT-RB, CVT-RB2 so we know what standard is being used - 1920x1080 144Hz 346 MHz is CVT-RB).

If the EDID comes with a 144 Hz timing using 325 MHz, then why are you creating another timing using 346 MHz?

[RonBurgundy]

Hi guys . Why Im seeing deep color only in YCbCr 444 and not in other color formats . Is this means that if I want to play a game or watch a movie in HDR i have to choose YCbCr 444 for correct HDR ?

[ToastyX]

(02-15-2020 10:51 AM)RonBurgundy Wrote:  Hi guys . Why Im seeing deep color only in YCbCr 444 and not in other color formats . Is this means that if I want to play a game or watch a movie in HDR i have to choose YCbCr 444 for correct HDR ?

That's just what the HDMI standard defines. Deep color always includes RGB, and 36-bit (12 bpc) always includes YCbCr 4:2:2. YCbCr 4:2:0 deep color support is defined in the HDMI 2.0 data block.

[joevt]

(02-15-2020 10:51 AM)RonBurgundy Wrote:  Hi guys . Why Im seeing deep color only in YCbCr 444 and not in other color formats . Is this means that if I want to play a game or watch a movie in HDR i have to choose YCbCr 444 for correct HDR ?

You should be seeing deep color for RGB and YCbCr 4:4:4. According to the HDMI 1.4b spec, in the section describing the HDMI VSDB, it says the deep color modes (16, 12, 10 bpc) refer to RGB. Normally YCbCr 4:4:4 only supports 8 bpc. Setting the YCbCr 4:4:4 deep color flag means that the deep color flags for RGB also apply to YCbCr 4:4:4.

It looks like CRU is including the YCbCr 4:2:2 and YCbCr 4:4:4 flags from the CTA extension block in the HDMI VSDB. There should be a separate place to edit the CTA extension block?

HDR is not deep color. It's part of HDMI 2.0a and 2.0b. I don't have those specs, but I think edid-decode knows how to interpret those parts.

[ToastyX]

(02-15-2020 02:54 PM)joevt Wrote:  It looks like CRU is including the YCbCr 4:2:2 and YCbCr 4:4:4 flags from the CTA extension block in the HDMI VSDB. There should be a separate place to edit the CTA extension block?

I did that because the YCbCr flags do nothing without HDMI support, so it will also unset them if HDMI support is deleted.