Custom Resolution Utility (CRU)

[Svyatoslav]

(01-25-2020 01:24 AM)ToastyX Wrote:  

(01-23-2020 02:41 AM)Svyatoslav Wrote:  Got a problem. Using this monitor Samsung U32H850 4K 60Hz FreeSync ON with GTX 2080 Ti. If I put in CRU range limits something more than 30Hz to 61Hz "G-Sync Pendulum" see my G-Sync setup but doesn't work, doesn't show smooth picture. It works only if I put 29Hz to 61Hz. Don't know why so. My monitor is 60Hz and via DisplayPort it doesn't show anything except 60Hz under nVidia Control Panel and FreeSync supposed to work on 60Hz. I would not ask as I hadn't one problem with this setup. If I play the game, in the game itself, I mean, while I am playing everything works fine and smooth but when the game showes me some cut scenes or movies or sometimes in the menu I see some rubbish which divides my screen by two same squares. Pictures are attached. How to get rid of this? Who knows why so?

The maximum range is limited by the current refresh rate. 61 Hz does no good if the refresh rate is 59.996 Hz. If you put 30-61 Hz, that leaves a hole between 29.998-30 Hz that LFC can't cover. Are you sure the TV can handle an extended range?

For some reasons it does the same result at 59Hz, at 60Hz, even at 64Hz and 70Hz. I agree that 29Hz is out of 30-61Hz range, thats why i set up 29-61Hz. Some people say if you setup just 60 then freesync doesnt use value of 60, the higer value it use in such setup is 59, that's why you should put 61. Don't kbow if it's true or not, as i mentioned above, my monitor goes with both refresh rates at the same result.

By the way, i got rid of artifacts in games by setting up limits to 19-61 Hz. Don't know how it works and how it helped.. But Pendulum if i simulate 40-60 works smooth, if i simulate 50fps - works smooth as well, but if i simulate 60fps - sometomes i see tearing. So freesync doesn't work 100%.

Who knowes how to set it up in details?

[ToastyX]

(01-29-2020 12:10 PM)Svyatoslav Wrote:  For some reasons it does the same result at 59Hz, at 60Hz, even at 64Hz and 70Hz. I agree that 29Hz is out of 30-61Hz range, thats why i set up 29-61Hz. Some people say if you setup just 60 then freesync doesnt use value of 60, the higer value it use in such setup is 59, that's why you should put 61. Don't kbow if it's true or not, as i mentioned above, my monitor goes with both refresh rates at the same result.

By the way, i got rid of artifacts in games by setting up limits to 19-61 Hz. Don't know how it works and how it helped.. But Pendulum if i simulate 40-60 works smooth, if i simulate 50fps - works smooth as well, but if i simulate 60fps - sometomes i see tearing. So freesync doesn't work 100%.

Who knowes how to set it up in details?

If you put 29-61 Hz but the detailed resolution is 59.996 Hz, then the range is 29-59.996 Hz. You need to change the detailed resolution to match.

[jim_rainor]

(01-26-2020 07:53 PM)ToastyX Wrote:  

(01-26-2020 10:13 AM)jim_rainor Wrote:  Okay, thanks for the info. I'm goint to try this one:
https://www.club-3d.com/en/detail/2479/d...e_adapter/
Some spanish guy in the amazon reviews says he got 110Hz on that monitor running, so I'm hoping for the best.

I don't have this particular adapter, but my experience with a similar Accell adapter is AMD limits this type of adapter to 300 MHz pixel clock with 8 bpc color and 400 MHz with 6 bpc. That's enough to get 100 Hz with 6 bpc, and AMD dithers 6 bpc well enough. With NVIDIA, the adapter is capable of 357 MHz at 8 bpc and 476 MHz at 6 bpc.

Hi, Just wanted to let everyone know that I got 110 Hz with the linked adapter (club3d cac-1010) on a RX 5700xt paired with a QNIX 2710 without scaler.
Hopefully this will be helpful for someone.
I'm anyway happy to be able to use my monitor for a few more years. Thanks!

[Drasko]

Greetings,

I have the AOC 24G2U 144Hz monitor and an AMD gpu (RX 5700), so when I set the refresh rate to 144Hz the memory no longer down clock (it's fine for 120Hz though). Using DisplayPort cable that came with the monitor.

I tried all 3 settings for LCD monitors, but only the 'Automatic - LCD standard' seems to let the gpu memory down clock. The problem is that as soon as I start a 3D game the monitor goes black and says 'Input No Support'. I have to blindly alt+F4 out of the game and select the DisplayPort as input again in order to gain back picture.

Is there anything I can do to make 144Hz work?

[ToastyX]

(01-29-2020 08:11 PM)Drasko Wrote:  Greetings,

I have the AOC 24G2U 144Hz monitor and an AMD gpu (RX 5700), so when I set the refresh rate to 144Hz the memory no longer down clock (it's fine for 120Hz though). Using DisplayPort cable that came with the monitor.

I tried all 3 settings for LCD monitors, but only the 'Automatic - LCD standard' seems to let the gpu memory down clock. The problem is that as soon as I start a 3D game the monitor goes black and says 'Input No Support'. I have to blindly alt+F4 out of the game and select the DisplayPort as input again in order to gain back picture.

Is there anything I can do to make 144Hz work?

If the refresh rate works on the desktop, then the same refresh rate should work in games. The only thing I can think of is maybe the monitor can't handle those timing parameters with FreeSync enabled.

[Drasko]

(01-30-2020 09:40 PM)ToastyX Wrote:  If the refresh rate works on the desktop, then the same refresh rate should work in games. The only thing I can think of is maybe the monitor can't handle those timing parameters with FreeSync enabled.

You're right, I disabled the FreeSync and the game works fine now, kind of a bummer, thanks for the help though

[joevt]

I tried CRU to override an EDID for a display. It works great. The only major issue is that it supports only 3 extension blocks. The Apple Pro Display XDR has 6 extension blocks (7 blocks total). The E-EDID specification says there can be 255 extension blocks.

Some minor suggestions:
- for data blocks that CRU doesn't understand, it could show at least hex values and maybe allow editing them (the hex should not include the tag, extended tag, length, or OUI).
- For TV resolutions, there is a check box to make all resolution only 4:2:0 or only not 4:2:0 (RGB/4:4:4/4:2:2 depending on the bits in byte 3 of the CTA extension block). There exists a third option that allows a resolution to have both. This is done using a third CTA extension block called Y420CMDB which contains flags for each SVD in all the VDBs that also support 4:2:0. For the user, the simplest UI might be to have the VDB, Y420VDB, and Y420CMDB all be editable at the same time using the same dialog. Each SVD has two checkboxes (or a menu with three options) which indicate if it goes into the VDB, the Y420VDB, or both the VDB and the Y420CMDB. Extra blocks can be created automatically if the number of SVDs exceeds the max for each block type. Additional CTA extension blocks may need to be created automatically. For simplicity, the user should not be able to move a VDB above or below a different VDB, in order to maintain the order of the flags in the Y420CMDB block(s).

For reference: edid-decode has been updated recently to decode almost everything in an EDID (it's missing Apple, Nvidia, and AMD vendor specific data block decoding). Most or all the specs used by edid-decode are publicly available.
https://git.linuxtv.org/edid-decode.git/about/

edit: max number of extension blocks for Apple Pro Display XDR is 6

[Bryan Stephanov]

Hello friends, will there be any way to have support for HDMI 2.1 and have dynamic HDR metadata and be able to edit them? also support for SMPTE ST 2086? Maybe in a new version of CRU? Greetings!

[ToastyX]

(02-07-2020 07:13 PM)Bryan Stephanov Wrote:  Hello friends, will there be any way to have support for HDMI 2.1 and have dynamic HDR metadata and be able to edit them? also support for SMPTE ST 2086? Maybe in a new version of CRU? Greetings!

HDMI 2.1 uses the same data block as HDMI 2.0 but with additional features. I don't have access to the HDMI 2.1 specification, so I don't have enough information yet on what the additional features are, but I want to include them eventually.

The HDR dynamic metadata block isn't very interesting. It only lists metadata types and versions. I might add it later.

[ToastyX]

(02-07-2020 09:37 AM)joevt Wrote:  I tried CRU to override an EDID for a display. It works great. The only major issue is that it supports only 3 extension blocks. The Apple Pro Display XDR has 6 extension blocks (7 blocks total). The E-EDID specification says there can be 255 extension blocks.

That's because the last time I checked, both AMD and NVIDIA would not read more than 3 extension blocks. It's rare for a monitor to have more than 2 extension blocks.

(02-07-2020 09:37 AM)joevt Wrote:  - for data blocks that CRU doesn't understand, it could show at least hex values and maybe allow editing them (the hex should not include the tag, extended tag, length, or OUI).

I thought about that but haven't gotten around to it. My implementation would let you edit everything including the tag. The length would be automatically calculated.

(02-07-2020 09:37 AM)joevt Wrote:  - For TV resolutions, there is a check box to make all resolution only 4:2:0 or only not 4:2:0 (RGB/4:4:4/4:2:2 depending on the bits in byte 3 of the CTA extension block). There exists a third option that allows a resolution to have both. This is done using a third CTA extension block called Y420CMDB which contains flags for each SVD in all the VDBs that also support 4:2:0. For the user, the simplest UI might be to have the VDB, Y420VDB, and Y420CMDB all be editable at the same time using the same dialog. Each SVD has two checkboxes (or a menu with three options) which indicate if it goes into the VDB, the Y420VDB, or both the VDB and the Y420CMDB. Extra blocks can be created automatically if the number of SVDs exceeds the max for each block type. Additional CTA extension blocks may need to be created automatically. For simplicity, the user should not be able to move a VDB above or below a different VDB, in order to maintain the order of the flags in the Y420CMDB block(s).

I'm aware of the capability map, but implementing a dialog that manages multiple data blocks at once is complicated, so this is not a high priority for me. If I did implement it, I would probably put a "4:2:0" check box next to the "Native" check box when adding/editing a resolution, which would set the appropriate bit in the capability map. This would be grayed out and always selected if it's set to be a 4:2:0 data block. Right now the only 4:2:0 resolution that seems to be in common use is 3840x2160 @ 60 Hz, so it doesn't seem worth the effort to implement all that for one resolution.

(02-07-2020 09:37 AM)joevt Wrote:  For reference: edid-decode has been updated recently to decode almost everything in an EDID (it's missing Apple, Nvidia, and AMD vendor specific data block decoding). Most or all the specs used by edid-decode are publicly available.
https://git.linuxtv.org/edid-decode.git/about/

That's good to know.