Hi there, as my kids got an xbox series S as christmas present I handed over my "old" HP 27xq monitor to them.
I had two of them running on my gaming PC and they did run with WQHD (2.560 x 1.440) and 120H (connected via HDMI)
Little surprise as the XBOX (HDMI as well) doesn't support running 1440dpi and 120Hz (1080dpi works). I learned this is due to HP not sticking to the VESA standard and reporting 119,xxHz instead of 120Hz to the xbox.
So i tried changing the EDID information with CUR (changed the 119Hz to 120Hz, removed TV resolutions and added second and flashed the HP firmware with the new bin file.
This is what I get when reading the EDID from the monitor after flashing:
***
Detailed Timing Descriptors:
DTD 1: 2560x1440 59.951 Hz 16:9 88.787 kHz 241.500 MHz (640 mm x 360 mm)
Hfront 48 Hsync 32 Hback 80 Hpol P
Vfront 3 Vsync 5 Vback 33 Vpol N
DTD 2: 2560x1440 120.000 Hz 16:9 177.721 kHz 483.400 MHz (640 mm x 360 mm)
Hfront 48 Hsync 32 Hback 80 Hpol P
Vfront 3 Vsync 5 Vback 33 Vpol N
Dummy Descriptor:
Dummy Descriptor:
Extension blocks: 1
Checksum: 0x8f
----------------
Block 1, CTA-861 Extension Block:
Revision: 3
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
Native detailed modes: 0
Video Data Block:
Audio Data Block:
Linear PCM:
Max channels: 2
Supported sample rates (kHz): 48 44.1 32
Supported sample sizes (bits): 24 20 16
Speaker Allocation Data Block:
FL/FR - Front Left/Right
Vendor-Specific Data Block (HDMI), OUI 00-0C-03:
Source physical address: 1.0.0.0
Maximum TMDS clock: 340 MHz
Vendor-Specific Data Block (HDMI Forum), OUI C4-5D-D8:
Version: 1
Maximum TMDS Character Rate: 600 MHz
SCDC Present
Vendor-Specific Data Block (AMD), OUI 00-00-1A:
01 01 30 90 ed '..0..'
Video Capability Data Block:
YCbCr quantization: No Data
RGB quantization: No Data
PT scan behavior: Supports both over- and underscan
IT scan behavior: Supports both over- and underscan
CE scan behavior: Supports both over- and underscan
Detailed Timing Descriptors:
DTD 3: 1920x1080 60.000 Hz 16:9 67.500 kHz 148.500 MHz (480 mm x 270 mm)
Hfront 88 Hsync 44 Hback 148 Hpol P
Vfront 4 Vsync 5 Vback 36 Vpol P
DTD 4: 1920x1080 50.000 Hz 16:9 56.250 kHz 148.500 MHz (480 mm x 270 mm)
Hfront 528 Hsync 44 Hback 148 Hpol P
Vfront 4 Vsync 5 Vback 36 Vpol P
DTD 5: 2560x1440 144.006 Hz 16:9 222.201 kHz 595.500 MHz (640 mm x 360 mm)
Hfront 8 Hsync 32 Hback 80 Hpol P
Vfront 25 Vsync 8 Vback 70 Vpol N
DTD 6: 2560x1440 120.000 Hz 16:9 183.000 kHz 490.440 MHz (640 mm x 360 mm)
Hfront 8 Hsync 32 Hback 80 Hpol P
Vfront 25 Vsync 8 Vback 52 Vpol N
'****
But the XBOX still says 1440 /120Hz is not supported by the monitor.
What do I miss here? Where is the XBOX getting the information from?
(01-17-2024 06:26 PM)Goddi8 Wrote: [ -> ]Hi there, as my kids got an xbox series S as christmas present I handed over my "old" HP 27xq monitor to them.
I had two of them running on my gaming PC and they did run with WQHD (2.560 x 1.440) and 120H (connected via HDMI)
Little surprise as the XBOX (HDMI as well) doesn't support running 1440dpi and 120Hz (1080dpi works). I learned this is due to HP not sticking to the VESA standard and reporting 119,xxHz instead of 120Hz to the xbox.
So i tried changing the EDID information with CUR (changed the 119Hz to 120Hz, removed TV resolutions and added second and flashed the HP firmware with the new bin file.
You have that backwards. I can't find any information about what specific timing the Xbox requires, but assuming VESA CVT-RB, that would be "Automatic PC" or "CVT-RB" with the pixel clock manually rounded down to the nearest 0.25 MHz, so 497.75 MHz, which is around 119.997 Hz. You have 2560x1440 @ 120 Hz in there twice, neither of which match that timing. What are you using to flash the monitor?
[
attachment=1314]
(01-16-2024 11:49 PM)D45p00k13 Wrote: [ -> ]I am running windows 11 with an RTX 4090 which is connected through a HDMI 2.1 cable to a Denon AVR X4800H. From there the video is forwarded to an LG G2.
My aim is to get VRR running through the denon. I activated 8K signaling which gives me 4k@120 Hz. The G2 the corresponding mode enabled. When i connect the windows machine directly to the tv VRR work fine. Using the Denon (which supports VRR) it fails.
The Denon is supposed to support VRR, so something is wrong. Run reset-all.exe and reboot if you made any changes. Then export the EDID with and without the Denon, and post them here.
(01-16-2024 11:09 PM)Adrianos Wrote: [ -> ]It's strange because I have the monitor for 2 months and I noticed the issue 2 weeks ago. I also tried with a driver from October 2023, but the issue was still there. I'm thinking that if I noticed the problem 2 weeks ago and it was from the driver, why the October 2023 one is having the same issues?
Someone mentioned the last driver without the issue is 537.58, but Windows might automatically update the driver to a newer version.
(01-16-2024 11:09 PM)Adrianos Wrote: [ -> ]If i reinstall the nvidia driver it will be required to delete the resolutions again from SRE, but not from CRU, correct?
That depends on how you reinstall the driver. If you use DDU, then it will wipe out any CRU changes as well. If you just upgrade the driver, usually CRU changes will stick but not SRE with NVIDIA.
(01-17-2024 07:22 PM)ToastyX Wrote: [ -> ] (01-17-2024 06:26 PM)Goddi8 Wrote: [ -> ]Hi
You have that backwards. I can't find any information about what specific timing the Xbox requires, but assuming VESA CVT-RB, that would be "Automatic PC" or "CVT-RB" with the pixel clock manually rounded down to the nearest 0.25 MHz, so 497.75 MHz, which is around 119.997 Hz. You have 2560x1440 @ 120 Hz in there twice, neither of which match that timing. What are you using to flash the monitor?
I am using
https://github.com/bulletmark/edid-rw on ubuntu to flash the firmware.
Changing the values to the one you suggested did the trick.
I cannot set HDMI manually and set 1440/120 in the xbox - for what ever reason it still says not supported.
I have to use the auto detect feature at the xbox but I can set 1440 and 120Hz now!
Awesome tool btw and even better support.
These are the default settings from the HP.
[
attachment=1315][
attachment=1316]
Question to dev, perhaps you are aware of whether there are ways to enable microsoft caso (software mux switch) in intel graphics 6-10 gen? This is purely a software lock, they are forcing us to switch to new hardware. I saw on some forum that someone added keys to the registry in the graphics path (0000) and caso seemed to work, I lost this resource. Toasty please pay attention, I’ve been digging into this question for half a year now. This is a huge boost for laptops, and you, as a display guru, probably know something...
Hi
I've been fighting with my new monitors for awhile now and the more I research things the more I'm getting confused. I was told about this CRU tool in the Monitor Enthusiasts Discord. This tool seems very feature rich and possibly able to fix my issue, but a lot of the terminology in the UI is going over my head. I'm hoping someone can help me fix the issue I'm having.
Setup:
I'm running an RTX 4090 FE currently with 3x Cooler Master Tempest GP27U monitors on Win11 Pro.
Problem:
My understanding about how the RTX 4090 FE works is that it basically turns off ports when it detects DSC so it has more processing power to perform DSC. The RTX 4090 FE comes with 3x DP 1.4a + 1x HDMI 2.1a ports. Therefore, if I have 2x monitors claiming they can use DSC then that's technically all 4 ports "in use". This makes the 3rd monitor "inactive" but, still detected by Windows. In order to get the 3rd monitor to work I'd need 2x or 3x of the GP27U's to not use DSC and 1x or 0x of the GP27U's to use DSC. I've read that some monitors have a method to basically turn off DSC by changing their DisplayPort "version" from 1.4 to 1.2 or something, but this kind of configuration option does not appear to exist in the GP27U's OSD menu nor in any Windows settings screen nor the NVIDIA Control Panel screen from what I can tell. I've even tried buying different DisplayPort "version" cables before I learned that DisplayPort "versions" are kind of misleading and not intended to be used to identify capabilities of cables/ports etc as per the DisplayPort wiki (which is a totally separate thing breaking my brain).
What I've done:
In my ignorance I've contacted NVIDIA who claim they aren't responsible for providing an option to control DSC, apparently, and that Cooler Master would need provide a firmware update to enable this option in the OSD. So, I contacted Cooler Master and frankly they've completely ignored me in all avenues of communication (Discord, Support Tickets, and phone). As a last ditch effort I reached out on the aforementioned Discord server which lead me here. I've tried doing some research on how to use CRU, but I'm pretty lost because I've not kept up on the monitor market in a long time.
I understand some of the nuance surrounding DSC's automatic behavior enough to at least mildly understand why there isn't just an explicit option in CRU labeled "DSC: On/Off", but since I don't understand the rest of the settings by their given names too well I'm incapable of easily figuring out what settings need to change to get this configuration to work. Sadly, I have until the end of this month to get this figured out basically due when I bought these monitors and if I'm going to need to return the monitors or not.
Goal:
Max out the specs of one monitor (4K @ 160Hz w/HDR etc) and have 2x 4K @ 60Hz monitors.
Any help would be super appreciated!
Hi dev! Amazing that you're still supporting this!
I was trying to upscale my T470 thinkpade which has a native 1366x768 to a 1920x1080, merely because I find the size of everything in the native res really big.
I tried to use the standard 1920x1080 res and restart but everytime an Igfxem module notification popped up and ovveride the resolution.
Thanks a lot in advance <3
(01-23-2024 05:51 PM)alessandro Wrote: [ -> ]I was trying to upscale my T470 thinkpade which has a native 1366x768 to a 1920x1080, merely because I find the size of everything in the native res really big.
That's downscaling. You can't use CRU to scale down on a laptop display.
ToastyX Wrote:
- CRU adds monitor resolutions, not scaled resolutions. Lower resolutions can be scaled up to the native resolution by enabling GPU scaling in the graphics driver's control panel, but higher resolutions won't be scaled down by the GPU. Higher resolutions will only work if the monitor can handle them.
- Laptop displays usually don't have scalers and can't display non-native resolutions without GPU scaling.
Intel doesn't officially offer a way to scale down higher resolutions.
(01-23-2024 01:44 PM)DragonRulerX Wrote: [ -> ]Hi
I've been fighting with my new monitors for awhile now and the more I research things the more I'm getting confused. I was told about this CRU tool in the Monitor Enthusiasts Discord. This tool seems very feature rich and possibly able to fix my issue, but a lot of the terminology in the UI is going over my head. I'm hoping someone can help me fix the issue I'm having.
Setup:
I'm running an RTX 4090 FE currently with 3x Cooler Master Tempest GP27U monitors on Win11 Pro.
Problem:
My understanding about how the RTX 4090 FE works is that it basically turns off ports when it detects DSC so it has more processing power to perform DSC. The RTX 4090 FE comes with 3x DP 1.4a + 1x HDMI 2.1a ports. Therefore, if I have 2x monitors claiming they can use DSC then that's technically all 4 ports "in use". This makes the 3rd monitor "inactive" but, still detected by Windows. In order to get the 3rd monitor to work I'd need 2x or 3x of the GP27U's to not use DSC and 1x or 0x of the GP27U's to use DSC. I've read that some monitors have a method to basically turn off DSC by changing their DisplayPort "version" from 1.4 to 1.2 or something, but this kind of configuration option does not appear to exist in the GP27U's OSD menu nor in any Windows settings screen nor the NVIDIA Control Panel screen from what I can tell. I've even tried buying different DisplayPort "version" cables before I learned that DisplayPort "versions" are kind of misleading and not intended to be used to identify capabilities of cables/ports etc as per the DisplayPort wiki (which is a totally separate thing breaking my brain).
What I've done:
In my ignorance I've contacted NVIDIA who claim they aren't responsible for providing an option to control DSC, apparently, and that Cooler Master would need provide a firmware update to enable this option in the OSD. So, I contacted Cooler Master and frankly they've completely ignored me in all avenues of communication (Discord, Support Tickets, and phone). As a last ditch effort I reached out on the aforementioned Discord server which lead me here. I've tried doing some research on how to use CRU, but I'm pretty lost because I've not kept up on the monitor market in a long time.
I understand some of the nuance surrounding DSC's automatic behavior enough to at least mildly understand why there isn't just an explicit option in CRU labeled "DSC: On/Off", but since I don't understand the rest of the settings by their given names too well I'm incapable of easily figuring out what settings need to change to get this configuration to work. Sadly, I have until the end of this month to get this figured out basically due when I bought these monitors and if I'm going to need to return the monitors or not.
Goal:
Max out the specs of one monitor (4K @ 160Hz w/HDR etc) and have 2x 4K @ 60Hz monitors.
Any help would be super appreciated!
DSC should only be active for resolutions that require it, so if you set the other two monitors to 3840x2160 @ 60 Hz, then DSC shouldn't be active on those monitors.