Custom Resolution Utility (CRU)

[ToastyX]

(01-18-2019 10:29 PM)rayw_cru Wrote:  Would like to report a potential bug: I recently got an LG 34GK950F and noticed that CRU doesn't show any of the higher refresh rates, nor a FreeSync range entry in the extended block.

What video card do you have? CRU asks the driver for the full EDID, but if the driver can't provide it for some reason, then CRU can't read the extension blocks. Try running reset-all.exe and reboot, and then check if CRU can read them.

(01-18-2019 10:29 PM)rayw_cru Wrote:  It also doesn't let me add a custom entry with the native 3440x1440@144Hz resolution (attached screenshot of CRU 1.4.1).

Detailed resolutions with pixel clocks greater than 655.35 MHz have to be added using a DisplayID extension block, which is probably what the second default extension block would be if CRU could read it.

[ToastyX]

(01-18-2019 01:04 PM)TnF Wrote:  Can you explain why this is? This laptop can be configured with a 4K screen @ 60hz, and even 10 bit (8+2 dithering) depth. This approximately required 4x the bandwidth as there are as 4x as many pixels in my understanding. So theoretically the interface should be able to do 4x60=240hz (i know i don't calculate the timings here but it's to get my point through). If i were to guess the interface is the latest eDP v1.4b which has more than enough bandwidth to do 1080p@120hz for example. Isn't the pixel clock rate related to the bandwidth of the interface? Why there is a 240mhz limit? If it was different how come normal DP (which eDP is based of) can run past that limit and clock patcher is available? :/

The panel is not going to have the interface to support the bandwidth required for a higher resolution that it doesn't support. DisplayPort runs at fixed clock speeds with 1, 2, or 4 lanes. 2 lanes @ 270 MHz (HBR) or 1 lane @ 540 MHz (HBR2) would allow up to 240 MHz pixel clock with 6-bit color and 180 MHz with 8-bit color, which is enough for 1920x1080 @ 60 Hz. The patchers cannot change the clock speeds for DisplayPort.

[ToastyX]

(01-17-2019 11:06 PM)carsar Wrote:  Hello, I have a problem with my tv and windows hdr. Windows can't detect color primaries information from TV and works with own Color Primaries: Red(0.659180,0.339844), Green(0.244141,0.669922), Blue(0.129883,0.040039), White Point(0.312500,0.329102)
That default color space doesn't match DCI-p3 and doesn't match real color space of my TV. SO red color doesn't look saturated as intended because 0.659180,0.339844 is worse than 0.68, 0.32.
Is there any way to everwrite these values for windows HDR(can be checked by VESA test program)?

Normally you would need to install a color profile to set the primaries, but I don't know how Windows handles color with HDR. There's a DCI-P3 option in the colorimetry data block, but I haven't seen Windows do anything with that information.

[rayw_cru]

(01-19-2019 02:34 AM)ToastyX Wrote:  What video card do you have? CRU asks the driver for the full EDID, but if the driver can't provide it for some reason, then CRU can't read the extension blocks. Try running reset-all.exe and reboot, and then check if CRU can read them.

RTX 2080 Ti Founders Edition. Reset-all and reboot didn't change anything unfortunately. I've attached the extracted EDID BIN for your analysis

(01-19-2019 02:34 AM)ToastyX Wrote:  Detailed resolutions with pixel clocks greater than 655.35 MHz have to be added using a DisplayID extension block, which is probably what the second default extension block would be if CRU could read it.

I see, but they're both only showing blank "Default extension blocks" for me

[Soulreaver]

(01-19-2019 02:33 AM)ToastyX Wrote:  The FreeSync has to be at least 10 Hz apart, and the maximum refresh rate has to include the currently set refresh rate. Honestly, I would just return the monitor and get something that works. You shouldn't have to mess with anything to get FreeSync to work correctly.

Thank you for the quick response.
I tried different values but looks like it does not change anything for me.

I am trying to use a FreeSync monitor as GSync (because i am cheap )
Looks like something is not working correctly with this combination.
I don't mind tearing when it is out of range of FreeSync (below 40). I just don't want it to flicker. But it flickers no matter what.

I have a GSync monitor that works perfectly fine no matter what FPS is.

I like my FreeSync monitor and do not want to return it because of it.
And it says in menu when you activate FreeSync that it may flicker in some situations - so seems to be that it is as expected for it and it can not be returned because of it. Will try to find some other solution for this. If i will not find a solution i will have to chose between tearing with no sync at all, stuttering with VSync, or flickering with Gsync on FreeSync, or playing on a smaller GSync screen .

[ToastyX]

(01-19-2019 03:31 AM)rayw_cru Wrote:  RTX 2080 Ti Founders Edition. Reset-all and reboot didn't change anything unfortunately. I've attached the extracted EDID BIN for your analysis

I need more information to investigate. If you made any changes, run reset-all.exe and reboot again. Then run the attached file once and upload the log file here.

[rayw_cru]

(01-19-2019 06:18 PM)ToastyX Wrote:  

(01-19-2019 03:31 AM)rayw_cru Wrote:  RTX 2080 Ti Founders Edition. Reset-all and reboot didn't change anything unfortunately. I've attached the extracted EDID BIN for your analysis

I need more information to investigate. If you made any changes, run reset-all.exe and reboot again. Then run the attached file once and upload the log file here.

Logs attached.

---

(01-19-2019 03:57 AM)Soulreaver Wrote:  I don't mind tearing when it is out of range of FreeSync (below 40). I just don't want it to flicker. But it flickers no matter what.

I have a GSync monitor that works perfectly fine no matter what FPS is.

I like my FreeSync monitor and do not want to return it because of it

Yeah, that would be a monitor problem, due to its narrow VRR range. I guess one workaround is to force Vsync OFF in the NVIDIA Control Panel, as well as in-game, so that when it drops out of VRR range either direction, Adaptive-Sync is disengaged fully

[ToastyX]

(01-19-2019 06:30 PM)rayw_cru Wrote:  Logs attached.

The driver is not providing the full EDID for some reason. The driver only reports a strange virtual monitor with no resolutions, so CRU has no way of getting the full EDID. Try disabling G-SYNC and see if that makes any difference.

[rayw_cru]

(01-19-2019 07:03 PM)ToastyX Wrote:  The driver is not providing the full EDID for some reason. The driver only reports a strange virtual monitor with no resolutions, so CRU has no way of getting the full EDID. Try disabling G-SYNC and see if that makes any difference.

Disabled G-SYNC and did a reset-all, restart. Still showing the same thing in CRU

Logs attached

[a2b]

Good evening Rayw_cru

First of all thank you for this great piece of software.

Then i was trying to understand whether i could use this to fool my PC into thinking my TV has more than 2 audio channels.

Currently my PC is connected via HDMI to my TV which in turn is connected to a Sonos system ( still in HDMI). The issue is the PC won't send 5.1 sound to the TV because it can't detect the sonos system and its support for 5.1.

While i understand there are no specific features that address this issue i was thinking adding support for hdmi bittstreaming could do the trick ?

Could you please confirm ?

Thanks again,

a2b