DeviceControl WIBNI

Hi Ted!

I was wondering if you've ever considered adding predefined presets to the PGenerator DeviceControl interface.
I think this would be a really useful feature, especially for users who aren't completely familiar with all the HDMI output parameters and their implications for different calibration workflows.
For example, when calibrating a modern OLED TV connected to a gaming console capable of 4K/120Hz, HDR and VRR, it's not always obvious which output settings should be used for manual HDR Game Mode calibration versus SDR 3D LUT calibration in Filmmaker Mode.
Currently, figuring out the appropriate combination of output resolution, refresh rate, RGB/YCbCr format, bit depth, quantization range, colorimetry, AVI InfoFrames, etc., often means searching through multiple AVS Forum discussions and piecing together the relevant information.

What if DeviceControl offered a few predefined calibration presets?
For example:
- SDR Manual Calibration
- SDR 3D LUT Calibration
- HDR10 Manual Calibration
- HDR10 Game Mode Calibration (4K/120Hz, VRR-capable displays)
- etc...

Each preset could automatically configure the relevant HDMI output parameters according to the intended calibration workflow.
And if the user manually changes any of those parameters, the preset selection could simply switch to **Custom**.
Of course, I understand that not every setup is identical and some settings depend on the display, signal chain and calibration software. The presets wouldn't need to cover every possible scenario, just provide sensible, well-documented starting points.

I think this could make PGenerator considerably more accessible while also helping users avoid incorrect signal configurations.

Just an idea! I'd be interested to hear your thoughts.

Archttila
I agree you that information is scattered.

I think that DeviceControl template present would be useful for beginners only if the template would somehow automatically adjust settings based on i) calibration software to be used and ii) display capabilities that PGenerator receives from HDMI. Both PGenerator and DeviceControl hasn't seen development since Oct 2023 and PGenerator has been said to be final version. I would be surprised to see if their development would be more than template upgrades and updates.

Below is my current understanding of algorithm for PGenerator / eTPG output based on reading too many forums posts and guides. Algorithms are sorted in order of relevance. Some might find it helpful for beginners instead of scattered information.

It might also help to understand PGenerator limitations compared to PiTPG, if I've understood everything correctly. PiTPG also adds all Dolby Vision modes and therefore has better Dolby Vision compatibility with various displays compared to PGenerator. Like all home users I haven't had chances to test PiTPG.

===

Incomplete TPG output algorithm

1. Gamut:
Rec. 2020: All HDR types + some devices that map HDR content into SDR Rec.2020
Rec. 709: SDR

PGenerator limitation (RPi3 only): Rec. 709 only

2. Bit-depth:
10 bit prefered over 8 bit

PGenerator limitation (RPi3 only): 8 bit only
PGenerator limitation: Dolby Vision only 8 bit

3. RGB / YCbCr:
Verification and manual calibration: Match target HDMI device (Blu-ray, OTT, PC or Game Device) native output
LUT profiling: RGB

PGenerator limitation (RPi3 only): Only RGB possible

Reason for matching:
RGB <=> YCrCr isn't bijection on equal bit depth. This can be visualised by comparing RGB triangle and YCbCr cylinder on the CIE chart.

Reason for not matching while LUT profiling:
LUT container pipeline/format is RGB.

4. RGB legal / extended / full:
Verification and manual calibration: Match target HDMI device native output
LUT profiling: (variable on based on LUT device and SDR/HDR)

PGenerator limitation: RGB full mode is always used as container

Note for LG OLED LUT profiling: SDR RGB extended and HDR RGB legal.

5. Resolution:
Native resolution

PGenerator limitation (RPi3 only): 1080p or lower
PGenerator limitation: Dolby Vision requires 1080p

6. Refresh rate:
Match target HDMI device native output (movie usually: 23.976 Hz, other content varies)

If HDMI bandwidth of TPG is restricted compared target HDMI device native format:
half frequency (25/29.97/30/59.94/60 Hz) or quarter frequency (29.97/30 Hz)