Home › Forums › Help and Support › “WideGamut” HDR TV always measuered as sRGB… why?
- This topic has 27 replies, 4 voices, and was last updated 2 years, 7 months ago by
Vincent.
-
AuthorPosts
-
2023-11-01 at 3:02 #139578
P.S. Actually, I do not think it is right calibrating in HDR even through the MADVR Overlay.
HDR is a dynamic feature. So the system should be calibrated first, then the extra compression/expansion is applied supposing the input is ideal 1886 brightness curve (which is just a scaled up sRGB gamma-curve, if I am not mistaken)
The caveeat is that it is dynamic for avoiding the burn-out, so everytime the readings are not the same.
2023-11-01 at 3:06 #139581P.S. does anyone have experience with LG’s service remote? I have one, but do not have a complete manual. Kind of dangerous stuff.
2023-11-01 at 5:54 #139583So why do you write an Iliad epic about HDR, when I asked about Gamut?
Because you said yourself that you display is showing that HDR is active.
P.S. when connecting the TV as a monitor to hdmi, HDR link logo is displayed.
And I already told you why having HDR on = sRGB colors from DisplayCAL in the very first sentence of my first response, but let me say it again.
When you have HDR turned on in Windows any applications that isn’t outputting in an HDR color format is going to have it’s output converted by Windows to the sRGB color space.
So besides preventing DisplayCAL from outputting it’s patches for measurement beyond the sRGB color space it’s also going to limit most applications (including what you are likely using to view/edit the photos from your camera) to the sRGB color space unless it specifically supports and is set up to output in an HDR color format.
That’s why I keep telling you to turn off HDR unless you are currently viewing HDR content.
Yes it’s a pain to switch HDR on and off depending on what you are viewing, but trying to create a usable profile and set up windows to do color management right when HDR is turned on just so you can leave it on all the time is a much bigger pain and not really worth the effort.
Have you even tried to run through a calibration with HDR turned off in Windows?
2023-11-01 at 8:39 #139584>Because you said yourself that you display is showing that HDR is active.
No. I did not say that. I said that it is a HDR display, and I managed to get HDR mode, which should be a WCG mode at the same time. But HDR mapping is a separate option, it is not active when calibrating.
I guess, we are lost in which switch is where. Now I got what you mean the HDR streaming in control panel.
Since I did not see a difference except the changing cotrast/saturation profiles in the TV, I am beginning to believe that there are two different 120Hz panels were sold under nano90 name. One with WCG, another without. I will do a few tests again, but it looks a failure, I was tricked buy LG’s marketologs.
2023-11-01 at 20:51 #139589Displaycal needs to be updated to support “Advanced Color” in windows. Your monitor is probably WCG
2023-11-02 at 11:58 #139595>Because you said yourself that you display is showing that HDR is active.
No. I did not say that. I said that it is a HDR display, and I managed to get HDR mode, which should be a WCG mode at the same time. But HDR mapping is a separate option, it is not active when calibrating.
I guess, we are lost in which switch is where. Now I got what you mean the HDR streaming in control panel.
Since I did not see a difference except the changing cotrast/saturation profiles in the TV, I am beginning to believe that there are two different 120Hz panels were sold under nano90 name. One with WCG, another without. I will do a few tests again, but it looks a failure, I was tricked buy LG’s marketologs.
Do as Patrick said:
Turn HDR off in windows, make sure that TV is in one of the non HDR widegamut modes, then measure native red for example in MS paint. Check if it is close rtings red. Green seems to be sRGB.-
This reply was modified 2 years, 7 months ago by
Vincent.
2023-11-05 at 15:22 #139616as I said, it is the same. There are “Auto” and “Native” gamut in the TV’s setup. Both, HDR and Non-HDR mode.
Measurements are almost equal, maybe just a little more red in “native”.
But in HDR mode without HDR mapping, the TV has different scale of white-point (Grays) calibration. the same number, 22 points, but distriburted differently. non-HDR scaled in %(LRGB).
HDR scaled in values from 15 to 1023, only RGB values.
And here is the interesting part. Whenever I calibrate, I can reach only the value 578. Meaning that higher values are not sent by the software. I use MADVr test pattern tool as the output of the HCFR.
2023-11-05 at 22:09 #139622Displaycal does not support advanced color in windows (HDR). This is the problem
2023-11-05 at 23:10 #139623Measurements are almost equal, maybe just a little more red in “native”.
That is what Rtings properly measured and the true native gamut of display. As explained before you must disable all HDR conbtrosl in TV and windows if you want to use it in color managed apps to the biggest posible colorspace.
2023-11-06 at 7:04 #139628Try reinstalling your graphics driver
2023-11-06 at 8:37 #139630Old Man, that was HCFR.
>Try reinstalling your graphics driver
That’s the first thing anyone tries.Btw, I discovered that HCFR’s Rec.1886 gamma curve is different from DisplayCal.
I took 20 hours tweaking RGB registers to match it to 7000K (LG’s LEDs produce 8500K+, so D65 results in too much distortion). Then I checked the same in DispCal, with the same whitepoint x&y, and it said I was wrong. Used the same lighting in the room.Vincent, that’s bad that they do not plot sRGB, or exact primary values. But theirs looks much wider than I got.
So, as I said, I have a strong suspicion that there are different matrices. And it is even possible that even this “nano” is a pure lie, and I am dealing with some shitthy AS-IPS kind of thing. They needed high luminance cheaply, so they owned everyone. And no-one had time to argue because the market changes too fast, and that is just some middle-class.
2023-11-06 at 8:42 #139634Well, I just installed the latest nvidia driver and it fixed it for me again and it’s definitely not the first thing I try
2023-11-06 at 15:58 #139638Btw, I discovered that HCFR’s Rec.1886 gamma curve is different from DisplayCal.
Unlikely, more likely that you configured reference in HCFR different that DIsplaycal. HCFR uses input offset instead of output.
-
This reply was modified 2 years, 7 months ago by
-
AuthorPosts