Hi All

ZRO + PGenerator 1.6 on Pi4, managed SDR cal fine but can't figure it out how to do HDR. Found a few guides exclusive to LG, while I have a TCL TV.
Tried everything set to Full 8, Legal 8 bit, Full 10 and Legal 10...
Do I need specific patches? Found some for 203 nits...?
Tried having a custom colourspace UHD BT2020 with my TV's maximum luminance but delta e goes crazy.
Interestingly in one of my tests all colours and greyscale points had reasonable delta e numbers, except for white which was over 20 - likely related to max brightness?
Thanks

You didn't mention if you'd looked at this:
https://lightillusion.com/hdr_calibration.html
The same limitations apply in HDR for both ZRO and the "full fat" versions of ColourSpace.
Ted is directly handling support for ZRO. You can email him at his website, displaycalibrations.com

RollsRoyce
thanks mate
done some reading and I think I may be in the right direction.... but unlike with SDR where I could get all graphs under control, in HDR10 Dif EOTF and clip look odd
can you see anything obviously wrong in my screenshots please? my TV does about 860 nits in a 20% window

You appear to be overtracking the luminance targets from 10-90%, and your white balance is poor at 100%. I have no experience at all with TCLs, so I can't advise you what to do specifically. Steve and/or Ted could tell you more, but I'm pretty sure they would need to see any file ZRO created at the end of the calibration (if you commanded it to do so). They can glean much more from that than from just the graphs, including if you have invalid readings from your meter.
You may also want to switch to 10% windows.

RollsRoyce
thanks, yeah perhaps I can log it and that will tell more

for some reason TCL's peak brightness happen at around 20% window size

Hi,

Your TPG/Colorimeter settings are not good.

Set 2160p24 YCbCr 4:2:2 10-bit REC.2020 output with the following settings for the HDR10 metadata parameters: Primaries P3/D65 MinDML 0.0005 MaxDML 1000 MaxCLL 1000 MaxFALL 400, LEGAL 8bit.

10% area window patch with 0.5 sec extra delay.

For your colorimeter, AIO 0.75 sec with 1 sec intelligent integrator works best for most of the displays.

Start with two-point RGB balance using a regular 21-Point grayscale patchlist and since your readings are higher in nits compared to the target Y, reduce only 2 channels from the 2-point RGB balance controls to fix the RGB balance.

The regular 21-Point grayscale patchlist will not map to your monitor because 16-235 has 0-10000 nits range and your TV has enabled HDR processing, tone mapping and clips the higher end.

Ideally you have to find out the 'correct' code level per each control point, like the method another user has used for his Sony TV (example).

You can use 8-bit values for that test, because 10-bit will require a lot of more time, but ideally 10-bit is better.

When you have a custom 21-point grayscale patchlist for your particular TV, you will start with RGB balance and then try to fix the luma error using a custom colorspace based on REC.2020 with your calibrated peak output.

ConnecTED
thanks Ted

Reasoning behind 1080@120Hz is because, for some reason, my TV is brighter at 120Hz and that's how I watch it on my HTPC (pgen cant do 4k@120 so 1080 was chosen). Same for the 20% window, TCL is brighter at that than 10%.
As for the custom patch file for HDR, in my last screenshot you'll see I managed to create one based on yours 858 nits example from a few years ago.

The other settings could be the reason here, I will try those. Thanks again.

120Hz really isn't used normally for consumer video content. Your TV is probably shifting into a gaming or PC mode expecting 0-255 signal range and 4:4:4 color depth based on that framerate, while you should be sending 60Hz HDR video level patterns as Ted described...