(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.
(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?
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 ?
(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.
(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.
(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.
(02-15-2020 07:31 AM)joevt Wrote: [ -> ]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
The problem is "LCD standard" uses different standards depending on the resolution, and "LCD native" and "LCD reduced" are not standard, so I can't name them after standards. The original point was to organize them by purpose because most people won't know what standard to choose. I've been wanting to change the timing options for a while, but I've been hesitant because of all the tutorials out there that have the old options. I had already started working on changing the timing options, but I haven't finalized anything yet.
The next version of CRU will probably have these options:
Automatic (PC) - For PC monitors (CEA-861-B/DMT [16:9]/CVT-RB)
Automatic (HDTV) - For HDTVs (CTA-861-G/DMT [16:9]/CVT-RB)
Automatic (CRT) - For CRT monitors (DMT [4:3/5:4]/CVT)
Native (PC) - Uses 60 Hz "PC" timing parameters for all refresh rates
Native (HDTV) - Uses 60 Hz "HDTV" timing parameters for all refresh rates
Exact - Produces exact integer refresh rates
Exact reduced - Same as above with reduced pixel clock for some resolutions
CVT standard
CVT-RB standard
CVT-RB2 standard
GTF standard
(02-15-2020 03:24 PM)ToastyX Wrote: [ -> ]I did that because the YCbCr flags do nothing without HDMI support, so it will also unset them if HDMI support is deleted.
Doesn't that depend on the drivers? DisplayPort also supports YCbCr.
(02-15-2020 03:37 PM)joevt Wrote: [ -> ]Doesn't that depend on the drivers? DisplayPort also supports YCbCr.
No, because DVI and VGA don't support YCbCr, and DisplayPort YCbCr is defined in the base block with EDID 1.4. The next version of CRU will provide a way to edit the DisplayPort YCbCr flags in the display properties.
(02-15-2020 07:31 AM)joevt Wrote: [ -> ]HDMI and DisplayPort connections have different EDIDs. Are you looking at the DisplayPort EDID or the HDMI EDID (they might have different product IDs)?
Double-check the EDIDs in Monitor Asset Manager (moninfo.exe).
I have attached the moninfo output with displayport connected.
(02-15-2020 07:31 AM)joevt Wrote: [ -> ]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?
My goal is to make my radeon card lower it's memory clock rate when idle by increasing the vertical blanking lines. This increases pixel clock.