Custom Resolution Utility (CRU)

[ToastyX]

(11-08-2023 05:44 PM)opa99 Wrote:  Thank you ToastyX for reminding me to also reflect or at least read what I wrote earlier.
After doing that, I realized that I also wrote that when adding a spatial filter (Dolby Atmos for home theater) in Windows settings, 5.1 audio is transmitted all the way to the receiver. Although compressed (Windows is encoding LPCM 5.1 to lossy Atmos 5.1). This leads me to think that maybe CRU did exactly what I asked it to do, but it is the limitation of the TV/ARC, since in all other cases (spatial filters disabled) I understand that PC is always transmitting LPCM, and ARC can only carry LPCM 2.0, so if the TV is not encoding it before sending, it will not be transmitted in 5.1/7.1 to the receiver over ARC.

Nevertheless, I did check the blanking, and I must say I do not understand what that means, but it reads:
3840x2160: 560 pixels, 90 lines
3840x1500: 160 pixels, 43 lines

I have also attached screenshots of all the parameters for these two resolutions in detailed resolutions window.

Yes, Windows normally sends LPCM, so testing that would probably be limited to 2.0 with ARC. HDMI audio is transmitted during the blanking periods, so the custom resolutions you added might need more blanking to transmit certain audio formats. Adding a detailed resolution should automatically fill in the parameters for 3840x2160 @ 60 Hz, so just use those parameters and change only the active resolution.

[ToastyX]

(11-08-2023 09:14 PM)wolik Wrote:  I am unhappy owner of 8K 65QN900B since one day. Problem: I cannot activate DLDSR.
How can I delete 7680 and 4096 resolutions? On my old monitor 4K KS9500 I could delete with CRU "4096" successfully.
Now three fields are empty.
I hope if I delete these two resolutions then DLDSR will be available again.
Or I am too "Sweet Summer Child?"

For certain TVs like the 65QN900B, NVIDIA's driver has a bug that affects how CRU reads the extension blocks and another bug that prevents EDID overrides from having any effect, so you can't use CRU currently.

Run this and post the test.txt file here so I can see the driver is reporting: https://www.monitortests.com/EDID-test.zip

[Yasho]

After I create a custom resolution and I restart it doesn't pop up in my resolution list.
I use a laptop with a native res of 1366x768 and goes down to as low as 1280x720, 1128 x 634, 1024 x 768, 800 x 600. I've watched countless videos and haven't found a solution.

[wolik]

(11-09-2023 04:10 AM)ToastyX Wrote:  

(11-08-2023 09:14 PM)wolik Wrote:  I am unhappy owner of 8K 65QN900B since one day. Problem: I cannot activate DLDSR.
How can I delete 7680 and 4096 resolutions? On my old monitor 4K KS9500 I could delete with CRU "4096" successfully.
Now three fields are empty.
I hope if I delete these two resolutions then DLDSR will be available again.
Or I am too "Sweet Summer Child?"

For certain TVs like the 65QN900B, NVIDIA's driver has a bug that affects how CRU reads the extension blocks and another bug that prevents EDID overrides from having any effect, so you can't use CRU currently.

Run this and post the test.txt file here so I can see the driver is reporting: https://www.monitortests.com/EDID-test.zip

Thank you so much!

---

(11-09-2023 04:10 AM)ToastyX Wrote:  

(11-08-2023 09:14 PM)wolik Wrote:  I am unhappy owner of 8K 65QN900B since one day. Problem: I cannot activate DLDSR.
How can I delete 7680 and 4096 resolutions? On my old monitor 4K KS9500 I could delete with CRU "4096" successfully.
Now three fields are empty.
I hope if I delete these two resolutions then DLDSR will be available again.
Or I am too "Sweet Summer Child?"

For certain TVs like the 65QN900B, NVIDIA's driver has a bug that affects how CRU reads the extension blocks and another bug that prevents EDID overrides from having any effect, so you can't use CRU currently.

Run this and post the test.txt file here so I can see the driver is reporting: https://www.monitortests.com/EDID-test.zip

Thank you so much!

---

(11-09-2023 04:10 AM)ToastyX Wrote:  

(11-08-2023 09:14 PM)wolik Wrote:  I am unhappy owner of 8K 65QN900B since one day. Problem: I cannot activate DLDSR.
How can I delete 7680 and 4096 resolutions? On my old monitor 4K KS9500 I could delete with CRU "4096" successfully.
Now three fields are empty.
I hope if I delete these two resolutions then DLDSR will be available again.
Or I am too "Sweet Summer Child?"

For certain TVs like the 65QN900B, NVIDIA's driver has a bug that affects how CRU reads the extension blocks and another bug that prevents EDID overrides from having any effect, so you can't use CRU currently.

Run this and post the test.txt file here so I can see the driver is reporting: https://www.monitortests.com/EDID-test.zip

Thank you so much!

[RonDamon]

(11-09-2023 04:10 AM)ToastyX Wrote:  

(11-08-2023 09:14 PM)wolik Wrote:  I am unhappy owner of 8K 65QN900B since one day. Problem: I cannot activate DLDSR.
How can I delete 7680 and 4096 resolutions? On my old monitor 4K KS9500 I could delete with CRU "4096" successfully.
Now three fields are empty.
I hope if I delete these two resolutions then DLDSR will be available again.
Or I am too "Sweet Summer Child?"

For certain TVs like the 65QN900B, NVIDIA's driver has a bug that affects how CRU reads the extension blocks and another bug that prevents EDID overrides from having any effect, so you can't use CRU currently.

Run this and post the test.txt file here so I can see the driver is reporting: https://www.monitortests.com/EDID-test.zip

I also have a Samsung TV, more precisely a 43" QN90B model and also it doesn't show those extension blocks. I wanted to edit the max luminance to use an ICC profile. There is no other way to edit the max luminance of HDR?

I'll put the test.txt here as well in the hope that this can help something lol

[opa99]

(11-09-2023 04:10 AM)ToastyX Wrote:  

(11-08-2023 05:44 PM)opa99 Wrote:  Thank you ToastyX for reminding me to also reflect or at least read what I wrote earlier.
After doing that, I realized that I also wrote that when adding a spatial filter (Dolby Atmos for home theater) in Windows settings, 5.1 audio is transmitted all the way to the receiver. Although compressed (Windows is encoding LPCM 5.1 to lossy Atmos 5.1). This leads me to think that maybe CRU did exactly what I asked it to do, but it is the limitation of the TV/ARC, since in all other cases (spatial filters disabled) I understand that PC is always transmitting LPCM, and ARC can only carry LPCM 2.0, so if the TV is not encoding it before sending, it will not be transmitted in 5.1/7.1 to the receiver over ARC.

Nevertheless, I did check the blanking, and I must say I do not understand what that means, but it reads:
3840x2160: 560 pixels, 90 lines
3840x1500: 160 pixels, 43 lines

I have also attached screenshots of all the parameters for these two resolutions in detailed resolutions window.

Yes, Windows normally sends LPCM, so testing that would probably be limited to 2.0 with ARC. HDMI audio is transmitted during the blanking periods, so the custom resolutions you added might need more blanking to transmit certain audio formats. Adding a detailed resolution should automatically fill in the parameters for 3840x2160 @ 60 Hz, so just use those parameters and change only the active resolution.

Thank you for all the replies!

My challenge has been that in CRU the maximum Hertz is always 60 for these high resolutions (at least what I have been able to achieve), and then I later change the Hertz in Nvidia settings. I have not put a lot of thought into these clock or blanking values, but instead used the "Automatic HDTV" presets, since I can see that those change with the refresh rate. Would there be a source where I could read and learn what these "do" and how I should change them?
Earlier I did check Monitortests main page for the explanations, but what I can understand from there is, that with modern displays (I understand this also includes TVs), I can reduce blanking, but what I do not understand is why I would like to reduce it? Thank you for bringing up the audio requirements for the blanking, this I had not understood earlier.

Also what is a bit puzzling is the max bandwidth settings in extension blocks, I do not fully understand how I should set them. I have HDMI 2.1 connectors (and cable) on both ends, so I would assume that the generic 600 MHz maximum is not the limit, but for some reason that seems to work for me, even though with the calculators it should not (for 3840x1500 @120hz, with HDR)... The bandwidth limit on my GPU is 48 Gbps and on the TV (receiving) the limit is 40 Gbps, but I have no idea what that would be in TMDS limit, or if that is even relevant for HDMI 2.1.

So any link where I could learn more on the pixel clocks / blanking / extension block details would be appreciated.

[Nodens]

Now sure if this has been asked before but I couldn't find anything on search.

Is it possible to somehow workaround DisplayPort Deep Sleep so that monitors without an OSD toggle don't disconnect on sleep?

Thanks

[Espionage724]

With Intel UHD 630 (31.0.101.2125), Windows 10 (10.0.19044), and Acer S271HL connected via HDMI, if I use CRU to do CVB-RB (v1 or v2) at 74Hz, sometimes after the monitor suspends my entire computer freezes and I need to hard-reboot.

On the same computer/monitor/cord with Linux, video=HDMI-A-1:1920x1080@74 works fine through suspends and wakes and without any issue both Xorg and Wayland.

Can I try or do anything to have 74Hz stable through monitor suspends/wakes on Windows?

[ToastyX]

(11-12-2023 04:13 PM)Espionage724 Wrote:  With Intel UHD 630 (31.0.101.2125), Windows 10 (10.0.19044), and Acer S271HL connected via HDMI, if I use CRU to do CVB-RB (v1 or v2) at 74Hz, sometimes after the monitor suspends my entire computer freezes and I need to hard-reboot.

On the same computer/monitor/cord with Linux, video=HDMI-A-1:1920x1080@74 works fine through suspends and wakes and without any issue both Xorg and Wayland.

Can I try or do anything to have 74Hz stable through monitor suspends/wakes on Windows?

You need to report that to Intel because there's no reason for that to happen.

[ToastyX]

(11-12-2023 02:52 PM)Nodens Wrote:  Is it possible to somehow workaround DisplayPort Deep Sleep so that monitors without an OSD toggle don't disconnect on sleep?

DisplayPort monitors aren't supposed to disconnect when they sleep, only when turned off. There isn't anything that can be done on the computer's end if the monitor disconnects unless the GPU supports EDID emulation, which is only offered on Quadro and FirePro GPUs. The only other option is an external EDID emulator, but I don't know any good DisplayPort ones.