HDR color problems in Windows 10

euskalzabe

[H]ard|Gawd
Joined
May 9, 2009
Messages
1,155
I've been reporting this to MS on the feedback hub for 2 years now. For a long time, enabling HDR in Windows 10 (currently on 1809) destroys all color rendering.

SDR:
yGGHa9R_89aLquanYANqfuirYIUiHEMx-TyCyHViw_LIIqfG1m6K8dDtcvD-v4GbKtXJ4np5gR-fNdJ_8Q=w1186-h889-no.jpg

HDR:
fVa6XbopFV1m-tw4dSuRKTXYRp9UHyOY46Jhjgp1lRCE0zBNxO3RUUmFbMAWJ4TTeCU8nv24jrRU7lobzg=w1186-h889-no.jpg

I've heard excuses about gamma and blah, about how it's perception... well, what I perceive is hot pink garbage that makes using HDR10 on Windows impossible. I've owned two HDR10 displays now. I've had a GTX 970, RX 470, RX 480 and now a GTX 1060. They all exhibited the exact same issue on both displays.

What gives? Is Microsoft ever going to fix this? There's plenty of people reporting the issue in the feedback hub, Microsoft has marked their usual "we've got this" for more than a year, yet here we are.
 
Last edited:

Tawnos

2[H]4U
Joined
Sep 9, 2001
Messages
3,807
A few important questions that may help your issue:

Can you run dxdiag, save all information, and paste it here?

Are you using DisplayPort? HDMI 2.0 can work, but I've seen more issues with it vs DP.

Does it look weird when you are looking at HDR content?

It appears you are looking at content in the SDR color space (REC.709) which is being displayed in the HDR color space (REC.2020) and thus ends up mapped a bit differently. From your monitors specs: "The HDR setting of Windows defaults to "On" and should be set to "Off" when not viewing HDR content." Of course, that panel doesn't actually support full HDR10 (it's an 8bit panel), so that makes the mapping act even worse.
 

euskalzabe

[H]ard|Gawd
Joined
May 9, 2009
Messages
1,155
It's a complex situation:

1. HDR content looks great in Youtube videos, although I can still tell there's a bit of a hint of pink-ish color.
2. Games are clearly outputting HDR, but it's also a pinkish.
3. I'm using HDMI 2.0, I'm about to try a DP 1.2 cable tomorrow - but DP 1.2 doesn't support HDR AFAIK, so I'll be trading G-sync compatibility for pinkish HDR (a win in my book).

It seems like the issue is that Microsoft isn't mapping the desktop SDR colors into the HDR color space, like you suggested. The panel doesn't have the capability to fully display HDR10, of course, but in now way should it look worse. This is clearly a windows issue: when I plug in my PS4, HDR looks great - good colors, highlights and shadows, within the monitors capability. Only when using Windows is color/contrast destroyed. This issue has been widely reported online and in the feedback app. I just can't believe 2 years later we're still dealing with this same stuff. Shows that Microsoft doesn't really care about fixing stuff (but yes, by all means, bring me yet another tool to snip screenshots...).

Here's AC Origins in SDR:
a2a0nwpNEE_c-jTPwIYxuW9SDoK5fgguHen1Y47vMaCfv26JwDJxSpw9iGghPnVZswmRLkOtWkWLnb7zMg=w1251-h938-no.jpg

vs HDR:
NEhoExAmsfPsgmc08zB4enoPIe_VmkN0iztFVnKqjkZm_6jWB-YeP7eStpUdP6rFuXHocAGFdRc88MMywA=w1251-h938-no.jpg
 
Last edited:

Mazzspeed

2[H]4U
Joined
Dec 27, 2017
Messages
2,727
What color range is your graphics card set to? Full or limited?

I'd imagine this still has an effect on HDR.
 

euskalzabe

[H]ard|Gawd
Joined
May 9, 2009
Messages
1,155
What color range is your graphics card set to? Full or limited?

I'd imagine this still has an effect on HDR.

I'm always careful about setting it to Full. I've tried with 8bit, 12bit, RGB, YCBCR 422... doesn't matter. HDR comes out pinkish. Again, only on Windows. No such issue with the PS4.
 

AltTabbins

Fully [H]
Joined
Jul 29, 2005
Messages
20,097
More than likely the hdmi connection. Give that DisplayPort cable a shot and let us know if the tint goes away.
 

Mazzspeed

2[H]4U
Joined
Dec 27, 2017
Messages
2,727
I'm always careful about setting it to Full. I've tried with 8bit, 12bit, RGB, YCBCR 422... doesn't matter. HDR comes out pinkish. Again, only on Windows. No such issue with the PS4.

Technically speaking, even if the color space was set incorrectly, it shouldn't have anything to do with the tint of the picture. It's not some form of night time color temperature mode setting in Windows conflicting? Because it looks like the color temperature's changing.
 

euskalzabe

[H]ard|Gawd
Joined
May 9, 2009
Messages
1,155
Nope, the night time setting is yellow, this is very clearly pink. I realized that the color calibrated ICC profile I use may be emphasizing what's happening. If I set the monitor color to SRGB, it becomes grossly bluish - you know how non-pro monitors tend to come from factory. If I then turn on HDR, it looks a bit better, but still not correct (like my HDR TV on the PS4).

This still seems like a color mapping issue in Windows. It's exacerbated by the correct, warmer ICC I calibrated, and maybe that's why it looks so red/pinkish. None of this should happen, but at least I'm getting somewhere.
 

Domingo

Fully [H]
Joined
Jul 30, 2004
Messages
18,702
I'm on a TV, so things could be different, but enabling HDR requires a totally different monitor configuration for me.
Things like contrast, color, etc. are all way off and require another setting. That's what fixed the colors looking way off for me. Contrast and brightness especially.
Funny thing is, even with that extra configuration, the desktop implementation of HDR still looks off until legit HDR content is playing.
It looks better, but never quite the same as it should.
For instance, some games (Shadow of the Tomb Raider) require that HDR on the desktop be turned on. My desktop looks hazy and "off" but the instant the game kicks in things look fine. Ditto with Netflix and HDR videos.
 

euskalzabe

[H]ard|Gawd
Joined
May 9, 2009
Messages
1,155
Funny thing is, even with that extra configuration, the desktop implementation of HDR still looks off until legit HDR content is playing.

I think this pretty much confirm that the issue in Windows 10 is a color mapping one. The desktop is rendered in SDR, and so when outputting HDR it maps it all wrong, looking horrible.

The solution would be for Microsoft to render the desktop in HDR, but there's a giant problem: since HDR wasn't a thing until recently, color render values have just assumed that all whites where max value. If the desktop were automatically mapped to HDR, then a white window would be as strong as your monitor can provide: 300nits, 1000nits, 3000nits... which will burn your skin off your face :D

I don't see an easy solution to the desktop while in HDR mode other than disabling it in desktop use automatically even when it's toggled to ON for games/video. You can't just rewrite all x86 software ever to understand that regular day-to-day white windows are not just auto-max-value white.
 

Tawnos

2[H]4U
Joined
Sep 9, 2001
Messages
3,807
It's a complex situation:

1. HDR content looks great in Youtube videos, although I can still tell there's a bit of a hint of pink-ish color.
2. Games are clearly outputting HDR, but it's also a pinkish.
3. I'm using HDMI 2.0, I'm about to try a DP 1.2 cable tomorrow - but DP 1.2 doesn't support HDR AFAIK, so I'll be trading G-sync compatibility for pinkish HDR (a win in my book).

It seems like the issue is that Microsoft isn't mapping the desktop SDR colors into the HDR color space, like you suggested. The panel doesn't have the capability to fully display HDR10, of course, but in now way should it look worse. This is clearly a windows issue: when I plug in my PS4, HDR looks great - good colors, highlights and shadows, within the monitors capability. Only when using Windows is color/contrast destroyed. This issue has been widely reported online and in the feedback app. I just can't believe 2 years later we're still dealing with this same stuff. Shows that Microsoft doesn't really care about fixing stuff (but yes, by all means, bring me yet another tool to snip screenshots...).

Can you upload the dxdiag output? It will provide valuable insights into things like what your driver and monitors claim they can do, as well as the color space being applied.

Further, the "looks great but pinkish" may be an issue due to a number of things: the monitor may be more efficient at displaying red and require a different color calibration. Have you tried running the HDR color calibration in windows?
 

Mchart

2[H]4U
Joined
Aug 7, 2004
Messages
4,082
I have nothing much to input other then maybe try to find another HDR display and see if you have the same problem to confirm things and/or take your display to a different computer and see if it renders in pink.

I keep HDR enabled in Windows and everything is quite accurate from a color temperature perspective.
 

euskalzabe

[H]ard|Gawd
Joined
May 9, 2009
Messages
1,155
Can you upload the dxdiag output? It will provide valuable insights into things like what your driver and monitors claim they can do, as well as the color space being applied.

Here's all the GPU relevant data dump from DXdiag. I haven't tried the HDR color calibration - didn't even know there was one.

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 1060 3GB
Manufacturer: NVIDIA
Chip type: GeForce GTX 1060 3GB
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_1C02&SUBSYS_37221458&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 11151 MB
Dedicated Memory: 2988 MB
Shared Memory: 8163 MB
Current Mode: 2560 x 1080 (32 bit) (75Hz)
HDR Support: Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G2084_NONE_P2020
Color Primaries: Red(0.651367,0.332031), Green(0.306641,0.630859), Blue(0.150391,0.059570), White Point(0.313477,0.329102)
Display Luminance: Min Luminance = 0.010000, Max Luminance = 1499.000000, MaxFullFrameLuminance = 799.000000
Monitor Name: Generic PnP Monitor
Monitor Model: LG HDR WFHD
Monitor Id: GSM7715
Native Mode: 2560 x 1080(p) (59.978Hz)
Output Type: Displayport External
Monitor Capabilities: HDR Supported (BT2020RGB BT2020YCC Eotf2084Supported )
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_NONGDI
Advanced Color: AdvancedColorSupported AdvancedColorEnabled
Driver Name: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll
Driver File Version: 25.21.0014.1771 (English)
Driver Version: 25.21.14.1771
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.5
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:False
Driver Attributes: Final Retail
Driver Date/Size: 1/10/2019 6:00:00 PM, 957616 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71E3E-5F42-11CF-0371-2C171BC2D435}
Vendor ID: 0x10DE
Device ID: 0x1C02
SubSys ID: 0x37221458
Revision ID: 0x00A1
Driver Strong Name: oem20.inf:0f066de38c1dbfb9:Section108:25.21.14.1771:pci\ven_10de&dev_1c02
Rank Of Driver: 00D12001
Video Accel:
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC DXVA2_ModeVP9_VLD_Profile0
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 1
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported
 
Last edited:

euskalzabe

[H]ard|Gawd
Joined
May 9, 2009
Messages
1,155
If you haven't done so yet, can you install the LG monitor driver for its color profile? https://www.lg.com/us/support-product/lg-34WK650-W

Good thinking, I had already done that though. I have 2 ICMs available, LG's official one for the monitor, which is just SRGB that makes everything unnaturally bluish, and my own calibrated profile:

upload_2019-1-23_11-13-1.png

If I put LG's as default on HDR, things look "better" in that they're not obnoxiously pink/orange/warm. My calibrated ICM is much warmer than the factory default, providing correct colors. It seems that when you turn on HDR, Windows just doesn't map things right:
1) With my ICM, everything looks too pink/orange/warm, despite the correct colors in SDR:

MY ICM SDR
QO45ED41ZqA5t-hPs72iv9_y29DjFmTo13tB46xjvbpc8XkqgOfCCsjGhcD5cAjzb-83mZzp5vFtUqhwgA=w1238-h928-no.jpg

MY CIM HDR
mY12WllFoJuTERrCpTLTA0nsginZ4DlL7blFuDWMWrmrnk5d_PwNDJdeEF9dhIztoG3mH_qa0_A6O1LGmw=w1238-h928-no.jpg

2) With LG's official ICM, things look bluer, a bit more natural in HDR because it's not crazy pink, but it's still too bluish and contrast has also gone out the window:

LG ICM SDR
yoXeR7xBQtEQtZjjbxyzgT413EQGBsyt1pD5CX4RNOKc67RG9JQ85laFxXQsfMXscjMPA2NJXfHy8zIunA=w1238-h928-no.jpg

LG ICM HDR
5EA00Wxhqmx2W0hO_k8GSsadUQ6kv3D0nKLCM_hkbH7z9Ck7HyoIydC6gxlRC2iCjQ9emgs8hXcmV7g6Uw=w1238-h928-no.jpg

My calibrated ICM looks fantastic in SDR, miles better than LG's ICM which is too blue as is common in consumer monitors. I could just switch to LG's ICM when gaming in HDR for things not to look super pink, but a) that'd be a pain and b) color and contrast are still not correct in HDR with LG's ICM anyway. I'd be trading too pink for too blue. It's amazing that in 2019, we're still fighting getting correct colors out of displays. What's the point of going to DCI-P3 and REC2020 displays if we can't properly show their colors?

Bottom-line: seems like a Windows mapping issue that's also hardware related. My HDR Vizio P55-F1 TV looks fine on when I turn on HDR. But on this monitor (and my previous Samsung KU6290 that supported HDR10), contrast is clearly not properly set. I guess this just goes to show that HDR is still a major mess and needs much more software support. Of course I didn't buy this monitor for its HDR capabilities, but it wouldn't hurt to be able to use HDR every now and then. AC Origins did look better with it, once my eyes adjusted to the pinkish white balance. I'm glad I only spent $200 on this stopgap monitor, but this is making me wary of the eventual 34" 4K ultrawide I'll buy in a few years, not until there's proper FALD and color reproduction. I may be on this 29er for a while if the market's speed is anything to go by. I can be happy with correct SDR, but it's annoying that HDR is being so problematic.
 
Last edited:

gamerk2

[H]ard|Gawd
Joined
Jul 9, 2012
Messages
1,817
On my TV (LG B6P) I keep HDR off in Windows and only enable it games that support it; every time I've turned on Windows HDR things go wrong (usually Windows or games getting stuck in the incorrect mode). Outside of exclusive-fullscreen applications (where you can safely forget the desktop exists), the fact an application and desktop could be using two differing color spaces is always going to be a PITA to manage properly.
 
Top