Kodi DSPlayer – DirectShow Player for Windows
HDR to SDR: Mapping BT.709 and BT.2020 

If you are sharing a single SDR source input for both HDR and SDR content by selecting tone map HDR using pixel shaders under hdr, SDR and HDR will share the same display mode, which means a color conversion is required for one of these sources. SDR and HDR content use different color spaces: SDR is graded to BT.709 and HDR is graded to BT.2020 (DCI-P3).

Basic Rules

Display calibrated to BT.709: Choose BT.709 (BT.2020 is converted to BT.709);

Display calibrated to BT.2020: Choose BT.2020 or DCI-P3 (BT.709 is converted to BT.2020 or DCI-P3).

Notes:
  • When BT.709 is converted to BT.2020 or DCI-P3, it is simply placed in a larger container for the display, which shouldn’t lead to any oversaturation of BT.709 content. So it is safe to choose BT.2020 or DCI-P3 for both SDR and HDR content if your display color profile matches this setting;
  • Output in DCI-P3 may require report BT.2020 to display (Nvidia only) is checked under calibration due to the fact most displays will be expecting a BT.2020 input despite only covering all or part of the DCI-P3 color space.

HDR to SDR 3D LUTs

3D LUTs used with tone map HDR using pixel shaders selected should be created with an SDR 2.20 pure power gamma. madVR tone maps HDR content to 2.20 when a 3D LUT is available. Acceptable results have been achieved with a 2.40 gamma 3D LUT, but it is recommended to match the input gamma provided to the 3D LUT by madVR to retain the same input and output luminances. PQ HDR uses absolute luminance values, so lowering displayed luminance with a 2.40 3D LUT (2.20 input from madVR to 2.40 display 3D LUT) runs the risk of reducing the source brightness too much.

3D LUTs created in a wide color gamut are best profiled in DCI-P3 rather than BT.2020. 3D LUTs do not like undersaturated gamuts and no current displays make use of the larger BT.2020 color space. When using DCI-P3 3D LUTs with JVC projectors, it is advised to check report BT.2020 to display (Nvidia only) to ensure the projector selects the correct color profile to match the 3D LUT. Not doing so may result in oversaturation if the projector misinterprets the DCI-P3 color space.

Sending BT.709 & BT.2020 Without Color Space Conversions

Some displays have a setting to automatically switch to the correct color profile based on the input signal (usually labelled as Automatic or Auto). In this case, it may make the most sense to simply send the correct color gamut based on the content without any conversions. There are also some tools available to force a projector into the desired color profile (e.g. HDfury Vertex or HTPC Control mentioned at the end of this post). The display must automatically switch to match the input color gamut or either SDR or HDR content will end up over or undersaturated. If this is not the case, the display likely has a fixed color gamut and it is better to choose any of BT.709, BT.2020 or DCI-P3 to match the calibrated color space.

To avoid a color space conversion, create two profiles in madVR under calibration:

calibration -> this display is already calibrated

Click
on the active device and select create profile group.

Check calibration and click OK.

Name the new profile group calibration.

Select add profile to create a second profile folder under calibration.

Name the first profile: BT.709 and set primaries / gamut to BT.709.

Name the second profile: BT.2020 and set primaries / gamut to BT.2020.

Click on calibration and copy and paste the following profile rules into the blank textbox:

If (HDR) "BT.2020"
else "BT.709"

green check mark should appear above the box to indicate the profiles are correctly named and no code conflicts exist.

The first calibration profile should be selected when SDR BT.709 content is played, and the second calibration profile is selected when HDR BT.2020 content is played.
Reply


Messages In This Thread
Lockup on STOP issue resolved! - by MKANET - 2015-04-11, 21:59
RE: 4G aware patch - by MagikMark - 2015-09-08, 03:27
Alt-F4 no longer quits - by JeffA - 2015-10-31, 20:38
H265 playback - by rew88 - 2017-11-04, 00:41
RE: H265 playback - by ashlar - 2017-11-04, 16:21
RE: H265 playback - by rew88 - 2017-11-05, 01:34
RE: H265 playback - by ashlar - 2017-11-05, 16:48
RE: H265 playback - by rew88 - 2017-11-05, 23:08
RE: H265 playback - by ashlar - 2017-11-06, 12:00
Leia 18 - by terpsarlington - 2017-11-21, 03:51
RE: Leia 18 - by spencerjford - 2017-11-21, 06:24
RE: Kodi DSPlayer – DirectShow Player for Windows - by Warner306 - 2018-07-14, 02:52
Display Modes / Refresh Rates - by goofer69 - 2019-09-20, 00:19
RE: Display Modes / Refresh Rates - by ashlar - 2019-09-20, 00:39
RE: Display Modes / Refresh Rates - by ashlar - 2019-09-20, 19:35
DSPlayer 23.810 to 23.976 - by Runakanta - 2018-05-09, 03:24
RE: DSPlayer 23.810 to 23.976 - by Warner306 - 2018-05-10, 01:32
Logout Mark Read Team Forum Stats Members Help
Kodi DSPlayer – DirectShow Player for Windows47