| Forums | Search | Statistics | Polls | File Bank | 
 ∅ ?  
You must be logged in to post content on this forum.
PGenerator & DeviceControl Light Illusion Forums / PGenerator & DeviceControl /  
 

ColourSpace ZRO + PGenerator 1.6: HDR10 100-nit patch measuring ~70–80 nits on Hisense U7SG

 
Author apowers00
ZRO

#1 | Posted: 26 Oct 2026 14:28 
I'm hoping someone can help me troubleshoot an HDR10 calibration problem using ColourSpace ZRO and PGenerator 1.6. I've spent considerable time investigating it without identifying the cause, and I'm wondering whether I've misunderstood or incorrectly configured something in the HDR workflow.

**The main issue is that HDR10 grayscale patterns consistently measure approximately 20–30% below their expected PQ luminance, accompanied by unusually large chromaticity errors.** This occurs even though the TV correctly enters HDR Filmmaker mode and the meter readings are highly repeatable. And in comparison, Rtings found that the TV follows the PQ EOTF curve very well out of the box. https://www.rtings.com/tv/reviews/hisense/u7sg#test_29341

Interestingly, SDR calibration using the same equipment works extremely well.

## Equipment

**Display**
- Hisense U7SG, 55-inch, 2026 model
- Mini-LED LCD with quantum-dot color technology
- HDMI 2.1 input
- HDR10 supported
- HDR Filmmaker picture mode

**Pattern generator**
- Raspberry Pi 4 running official PGenerator 1.6
- Updated from an older PGenerator installation
- HDMI connected directly to the television
- Ethernet connected directly to my Windows laptop, using Windows Internet Connection Sharing
- Controlled through ColourSpace ZRO

**Measurement equipment**
- Calibrite ColorChecker Display Plus (i1Display Pro-family colorimeter)
- ColourSpace ZRO
- Spectral correction: Hisense U7Q QD-Mini LED correction from Ted's spectral correction collection, measured using a JETI 1501 HiRes spectroradiometer (2 nm)
- No U7SG-specific spectroradiometer profile is available to me

## Hisense HDR10 settings

I started from the HDR Filmmaker settings recommended by RTINGS:

- Picture Mode: HDR Filmmaker
- Color Temperature: Warm 1
- Peak Brightness: High
- Local Dimming: High
- Contrast: 50
- Black Level: 0
- Dynamic Tone Mapping: Off
- Dark Detail: Off
- RGB Gain: 0/0/0
- RGB Offset: 0/0/0
- HDMI Dynamic Range: Limited

I confirmed that the television actually switches into HDR Filmmaker when PGenerator enables HDR output.

No HDR white-balance or multipoint adjustments have been made.

## ColourSpace ZRO settings

- Target Gamut/EOTF: ST2084 Rec2020
- Patch Scale: Legal
- Bit Depth: 10-bit
- Limit Range: Disabled
- Patch Window: L20, approximately 20% of screen diagonal (4% screen area)
- Patch Position: Center (PosX 50, PosY 50)
- Background Color: Black
- Probe Extra Delay: Initially 2 seconds, subsequently tested at 4 seconds
- PGenerator Calibration Patches: Auto

I used a custom CSV of 10-bit Legal HDR10 grayscale and color patches, but also tested by entering the relevant RGB values directly in Manual Measure.

## PGenerator settings

Under PGenerator Hardware Options:

- TPG Mode: HDR
- Color Format: RGB (Full)
- Colorimetry: Rec2020
- Output Resolution: 3840 × 2160 at 60 Hz
- Scaling Type: Performance
- Patch Area: 100.00
- HDR EOTF: ST2084
- HDR Primaries/White Point metadata: P3/D65

HDR metadata:

- MinDML: 0.0005 nits
- MaxDML: 1,000 nits
- MaxCLL: 1,000 nits
- MaxFALL: 250 nits

I also tried manually clicking "Upload HDR Info Frame" without any improvement.

I understand that Rec2020 colorimetry with P3/D65 mastering-display metadata is a normal HDR10 configuration, but please let me know if any of these settings are inappropriate.

## Actual HDR measurements

Using 10-bit Legal grayscale patches, with the TV menu closed:

| Target PQ luminance | Actual luminance | Approximate error |
|---|---|---|
| 100 nits | 82.0 nits | -18% |
| 200 nits | 159.7 nits | -20% |
| 400 nits | 321.6 nits | -20% |

The errors are surprisingly consistent across these PQ levels.

For example, the nominal 100-nit patch uses RGB 509/509/509 and produces a ColourSpace target of 99.913 nits.

Its measured chromaticity was approximately:

- Target: x = 0.3127, y = 0.3290
- Actual: x = 0.3086, y = 0.3053
- ΔE2000: 6.61

Subsequent repeated measurements were typically around 70–82 nits, with similarly large chromaticity deviations. The exact results varied with pattern area and background configuration.

At the higher end, a maximum white HDR stimulus produced approximately 1,485 nits with a 20% diagonal window, so the display is clearly capable of substantial HDR peak brightness.

## Troubleshooting already performed

**1. Verified generator output and HDMI range**

I confirmed that PGenerator is configured for RGB Full output, ColourSpace for 10-bit Legal patches, and the Hisense for Limited HDMI range.

I also tried the TV's Auto HDMI range setting, which did not improve the measurements.

Changing PGenerator to YCbCr 4:4:4 likewise produced essentially the same 100-nit luminance and white-point errors.

**2. Checked patch values and bit depth**

ColourSpace showed the expected RGB 509/509/509 values for the nominal 100-nit patch.

I entered these values manually rather than selecting the CSV patch, with essentially identical results.

I also tried the approximately equivalent 8-bit Legal patch (RGB 127/127/127), which measured around 72 nits.

**3. Investigated local dimming and patch size**

With Local Dimming High and a centered L20 patch, the 100-nit measurement was approximately 82 nits.

Disabling local dimming produced approximately 64 nits, with a significant change in chromaticity.

Changing from L20 to L10 produced approximately 50 nits, with much larger chromaticity errors. The L10 patch also appeared quite small physically.

A full-field 100-nit patch produced approximately 29 nits.

These results suggest substantial dependence on pattern size and backlight behavior.

**4. Tested different patch backgrounds**

Changing the background from black to a neutral gray (RGB 64/64/64) reduced the 100-nit measurement to approximately 52 nits.

I subsequently restored the black background.

**5. Checked probe settling and repeatability**

Increasing Extra Delay from 2 to 4 seconds made no meaningful improvement.

Three consecutive measurements of the same stationary patch were nearly identical.

The patch appears visually uniform with well-defined rectangular edges, and the colorimeter is centered over it.

**6. Tested color-temperature and spectral-correction settings**

Warm 1 was closer to the D65 target than Warm 2.

Disabling the borrowed Hisense U7Q spectral correction had only a modest effect. The large luminance deficit and chromaticity errors persisted.

I restored the correction afterward.

**7. Attempted independent verification**

I also tried using the Windows laptop's USB-C-to-HDMI output with Windows HDR enabled. ColourSpace's floating patch window measured only approximately 28 nits for the nominal 100-nit patch. However, I recognize that the Windows HDR compositor may transform ordinary SDR-rendered patch values, so I don't consider this a reliable reference either.

## Why I suspect a configuration issue

Using exactly the same Raspberry Pi, colorimeter, and ColourSpace ZRO software, I was able to complete a very successful SDR calibration:

- Rec709 Gamma 2.2
- Average grayscale ΔE2000 approximately 1.09
- Average color ΔE2000 approximately 0.72
- Maximum measured color ΔE2000 approximately 2.59

Thus, SDR pattern generation and measurement appear to work properly.

Additionally, RTINGS reports very good HDR PQ tracking for the U7SG series, whereas my measurements show large, systematic deviations.

## Questions

1. Do the ColourSpace ZRO and PGenerator 1.6 HDR settings above look correct, particularly the combination of 10-bit Legal patches, RGB Full generator output, and Limited HDMI range at the television?

2. Is there anything special required to configure PGenerator 1.6 for accurate HDR10 grayscale measurements beyond selecting TPG Mode HDR, ST2084, Rec2020, and uploading the HDR InfoFrame?

3. Is the difference between P3/D65 HDR metadata primaries and Rec2020 colorimetry relevant here?

4. Does the L20 patch size correspond to the recommended pattern geometry for HDR calibration on Mini-LED displays, or would you recommend another patch size or background strategy?

5. Could the large chromaticity changes associated with patch size be related to a generator scaling, range, or rendering issue?

6. Is there a simple built-in test or known reference patch sequence in ColourSpace ZRO that would allow me to verify that PGenerator is generating the correct HDR10 luminance levels, without relying on my custom CSV?

7. Is there a way to inspect or verify the actual HDR output signal using ColourSpace, DeviceControl, or PGenerator's diagnostic tools?

8. Are there any known limitations or issues with PGenerator 1.6 HDR output when used with the current ColourSpace ZRO version?

I'm particularly interested in determining whether I've configured something incorrectly before attempting any HDR white-balance adjustments. I would prefer not to calibrate the TV against potentially incorrect HDR patterns.

I can provide screenshots of all the hardware and software settings, as well as the patch CSV and measurement logs if that would be helpful.

Thank you very much for any guidance.

Best regards

Author Steve Male
INF

#2 | Posted: 26 Oct 2026 18:51 
Did you make a ST2084 colour space target with the correct peak value?
(I see no mention of that in your treatise...)
The default is obviously 10,000 nits.

Steve
Steve Shaw
Mob Boss at Light Illusion

Author apowers00
ZRO

#3 | Posted: 27 Oct 2026 14:00 
Steve

I did not know about that step. I found the description in the Colourspace documentation just now, but not the Colourspace ZRO guide as far as I can tell.
I will try that and report back. Thanks!

Author apowers00
ZRO

#4 | Posted: 27 Oct 2026 14:26 
I'm going to try starting fresh with ST2084 target set in advance as a custom colourspace, as you suggest, but I think when I adjusted the Luma Target Max to 1450 nits in the settings menu, that should have accomplished the same thing. From my understanding, ST.2084 PQ defines absolute luminance, so the target max should not affect readings with 100, 200, and 400 nit stimuli. Would it be within the realm of possibility for this 55-inch TV to just be poorly tracking the EOTF, despite the rtings test of the 65 in version showing it very closely tracked EOTF out of the box. I have a Sony X950H that I did calibrate previously with Calman that I can compare with to ensure my settings in Colourspace are correct.

My Chatgpt assistant created my initial post based on all the adjustments we tried. Sorry it was long, but I wanted you to have as much information as possible.

Author Steve Male
INF

#5 | Posted: 27 Oct 2026 16:14 
If you set the value in the Settings menu, Target Max Luma, that is fine. It does the same thing.
You just didn't mention that in your list of things you did...

You can test all is set correctly in ColourSpace with the Virtual Probe, if you have made and saved a target colour space correctly.
(You have to have a colour space saved as you cannot edit the Max Luma value in the Virtual Probe with PQ colour spaces.)
You select as the Virtual probe OETF, making sure the Max Luma is correct.
The result of that test shows all is working as it should - and you TV is just not accurate.
(Assuming you have the Range set correctly, etc.)

Steve
Steve Shaw
Mob Boss at Light Illusion

Author apowers00
ZRO

#6 | Posted: 28 Oct 2026 15:24 
Hi again, I did the virtual probe, and everything tracked perfectly. So then I ran the ColourSpace HDR check on my Sony X950H on the Custom Picture setting used by Rtings. I set the max target in the Colourspace to 800 nits, which was the max I measured on the L20 window. And I made sure Luma Max was the same at 800.
The same issue recurred. HDR10 grayscale patterns in the mid-range consistently measure approximately 20–30% below their expected PQ luminance. At the lower range, the tracking is slightly above expected, and at the upper range, measured luminance matches the target. But the mid range is so far below expected it doesn't make sense.
I'm completely baffled by what could be wrong. I don't think both TVs could be that far off expected PQ EOTF tracking. And the Pgenerator is supposed to give perfect patches. And again, the SDR calibration I did on the Hisense worked great. The Hisense actually needed very little adjustment for that. Just a few clicks on the 2-point RGB gains, and then the EOTF tracking and RGB balance were nearly perfect across the whole range.

Author Ville Male
ZRO

#7 | Posted: 28 Oct 2026 18:27 
apowers00
Your display panel has backlight. It might be that luminance is near absolute PQ values only with some spesific i) patch size, ii) patch background colour and iii) local dimming setting. Outside this spesific situation manufacturer might prefer that there would be less blooming / halo effects for consumers to sacrifice absolute luminance values of calibration patches.

You might consider measuring other patch sizes and include at least L32 / 10%. Rtings don't tell what patch size (and some other settings) they use.

Author Steve Male
INF

#8 | Posted: 28 Oct 2026 19:19 
For HDR, L18 is the standard now.
It is tiny...
Shows just how messed-up HDR really is.

Steve
Steve Shaw
Mob Boss at Light Illusion

Author apowers00
ZRO

#9 | Posted: 29 Oct 2026 13:52 
I tried L32 last night and lo and behold, the PQ EOTF tracked nearly perfectly. Thanks for the insight. I had tried the L10 window instead of L20 and that didnt help so I thought patch size wasn't affecting results. I ended up just making slight adjustments to the 2 point RGB gain values, and that was good enough to give me excellent white balance on the Hisense. Then the colors overall had a delta E less than 2 so I left those alone. Trying to fine-tune calibration on this TV is difficult as when the calibration menu is open on the TV on the right of the screen, it changes the patch and how it measures. I don't understand why Rtings said the TV was easy to calibrate because to me, that is not easy when you have to exit the menu completely to make each measurement. Maybe that doesnt happen as much on the 65 in version of the TV.

But all of this raises another question. After you said Rtings doesnt share their patch size, I wanted to understand why that is and I found the answer below.

"The tricky part is the size of the white square. Almost all reviewers use a window that covers 10% of the screen. We don't. We've found that many display manufacturers look for that 10% window, and when they see it they optimize for it to make sure that window is displayed correctly. Now, I'm not at all suggesting that AOC is doing that here, merely providing some context for why we don't use a 10% window. That can sometimes explain why some reviewers have a nice EOTF cutoff while ours looks bad. We don't want to share the window size we're using, either, as we don't want brands to optimize for our test." https://www.reddit.com/r/Monitors/comments/1r498rc/how_do_reviewers_measure_eotf_and_its_rolloff/

So if I was getting poor PQ EOTF tracking with L10 and L20, but near-perfect tracking for L32, does that mean Hisense might have done something to purposely optimize for a 10% window?

This TV has some very interesting Dolby Vision 2 options (it received a firmware update recently enabling Dolby Vision 2) that allow for the content creator to control white point, motion, and sharpness. The 2-point is greyed out, and only 20-point is available. I did try running Dolby Vision Verify in Colourspace but it didnt seem to work on my TV. I read that the new PiTPG is going to have more options for Dolby Vision so hoping one of those might allow me to test. I'm also looking forward to the single USB cable from the PC to the Pi. I've been doing direct Ethernet between pc and the Pi, and it's finicky. I've had to reset Windows Internet Connection Sharing intermittently when I start a new calibration session.

Thanks for the help

Author Steve Male
INF

#10 | Posted: 29 Oct 2026 13:58 
If you check the various providers of HDR specifications you will find L18 is now the standard, as most TVs cannot even do L32 accurately any more.

Steve
Steve Shaw
Mob Boss at Light Illusion

Author Ville Male
ZRO

#11 | Posted: 29 Oct 2026 15:56 
apowers00:
So if I was getting poor PQ EOTF tracking with L10 and L20, but near-perfect tracking for L32, does that mean Hisense might have done something to purposely optimize for a 10% window?
Most (if not all) panels with backlights, the resolution of backlight / number of backlight areas is smaller than pixel resolution. Therefore light output of a single dimming area is always a compromise between different (high) contrast segments within.

My uneducated guess was based on assumption that the area of a single dimming zone would be so big that the backlight output of probe measurement areas would be mixed result of a small L10/L20 patch and dark background. In that case something larger patch like L32 might be enough big patch window that backgrond doesn't get dimmer because of background colour.

So the underlying problem is that accurate PQ tracking throughtout whole display resolution with real HDR content is something which cannot be done these home TVs as they aren't even close professional reference monitors.

It is hard tell, what was TV manufacturer optimisation goal:
1) Amount of local dimming areas or retail price point. (=manufacturing cost optimisation)
2) Real HDR content or calibration patches for TV reviewers. (=firmware optimisation)

PGenerator & DeviceControl Light Illusion Forums / PGenerator & DeviceControl /
 ColourSpace ZRO + PGenerator 1.6: HDR10 100-nit patch measuring ~70–80 nits on Hisense U7SG

 

 
Online now: Guests - 2
Members - 1 [ Vassily ]
Max. ever online: 380 [24 Mar 2026 21:54]
Guests - 380 / Members - 0