General information: Whitepaper | Beyond resolution – HDR, WCG and HFR
From the SSU report in the first post:
| Current Mode: 3840 x 2160 (32 bit) (120Hz) | Video files are rarely available with a refresh rate of 120 Hz. Actually only if you have recorded videos yourself this way. In all other cases this refresh rate is not necessary. This could affect automatic HDR detection. However, the latter primarily depends on the software player and the used DirectShow Rendering Filters. |
| HDR Support: Supported | System has recognized the suitability of the signal chain for HDR |
| Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 | This is the color space defined in ITU-R BT.709 for HDTV (1080p/i). If HDR is enabled this should read "DXGI_COLOR_SPACE_RGB_FULL_G2084_NONE_P2020" ITU-R BT.2020 is the color space defined for Ultra-High-Definition Television (4K UHDTV) |
| Monitor Capabilities: HDR Supported (BT2020RGB BT2020YCC Eotf2084Supported ) | SMPTE ST 2084 is the industry's reference for High Dynamic Range Video Imaging. SMPTE = Society of Motion Picture and Television Engineers. The 2084 standard defines an electro-optical transfer function (EOTF) with a high luminance range capability. |
Dolby Vision typically includes additional (dynamic) metadata streams defined in SMPTE ST.2094-10. This is not supported on Windows Platforms for video playback as Dolby Vision is a largely closed licensed system from Dolby Laboratories for HDR videos and covers the creation, distribution and playback of content.
On Windows platforms only HDR10 with static metadata can be used for HDR video playback. Please check these settings. Set "Auto HDR" to ON as well:
Link Copied
General information: Whitepaper | Beyond resolution – HDR, WCG and HFR
From the SSU report in the first post:
| Current Mode: 3840 x 2160 (32 bit) (120Hz) | Video files are rarely available with a refresh rate of 120 Hz. Actually only if you have recorded videos yourself this way. In all other cases this refresh rate is not necessary. This could affect automatic HDR detection. However, the latter primarily depends on the software player and the used DirectShow Rendering Filters. |
| HDR Support: Supported | System has recognized the suitability of the signal chain for HDR |
| Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 | This is the color space defined in ITU-R BT.709 for HDTV (1080p/i). If HDR is enabled this should read "DXGI_COLOR_SPACE_RGB_FULL_G2084_NONE_P2020" ITU-R BT.2020 is the color space defined for Ultra-High-Definition Television (4K UHDTV) |
| Monitor Capabilities: HDR Supported (BT2020RGB BT2020YCC Eotf2084Supported ) | SMPTE ST 2084 is the industry's reference for High Dynamic Range Video Imaging. SMPTE = Society of Motion Picture and Television Engineers. The 2084 standard defines an electro-optical transfer function (EOTF) with a high luminance range capability. |
Dolby Vision typically includes additional (dynamic) metadata streams defined in SMPTE ST.2094-10. This is not supported on Windows Platforms for video playback as Dolby Vision is a largely closed licensed system from Dolby Laboratories for HDR videos and covers the creation, distribution and playback of content.
On Windows platforms only HDR10 with static metadata can be used for HDR video playback. Please check these settings. Set "Auto HDR" to ON as well:
Full Dolby Vision video processing is only supported on systems that feature a hardware decoder. Futhermore the Operating System must provide a protected video path to a Dolby certified playback hardware (display device). Android is the only platform to be capable of the protected part so far. Windows processes media via the DirectX graphics infrastructure. The associated application programming interfaces (API) do not offer the requirements mentioned.
The partial support of Dolby Vision in MPC Video Renderer is such that particular profiles are supported in processing. The prerequisite is a data source with High Efficiency Video Coding (HEVC/H.265), 10-bit color depth. The contained Base Layer is translated via an Dolby defined cross-compatibility matrix so that the output is as HDR10 or Hybrid Log Gamma (HLG). The latter is an HDR transfer function that provides BT.2020 colorimetry without metadata but is primarily suited and used for Digital Video Broadcasting (DVB).
In summary, the MPC Video Renderer can output Dolby Vision source material as HDR10. And only this is output by graphics cards under Windows via the physical layer (PHY) corresponding to SMPTE ST.2084. So one's display device will not display "Dolby Vision" but "only" HDR10.
Hello Andres,
Is glad to hear form you
The specific apps used are described in the following image
Thank you for your help.
Thank you for the overview. This represents your situation well. I would like to continue to help you see through all this. Do I understand correctly that the first scenario shows the "Dolby Vision" logo on your LG TV in the right upper corner like this:
That would be surprising, because as I said, full Dolby Vision is only possible if you're using an Android source device. The following situation for me:
Device description:
HDfury VRROOM is an HDMI 2.1 Fixed Rate Link (FRL) signal processor and switch.
Denon AVR-X4800H is an Audio-Video-Receiver like your Yamaha RX-A6A. Both equipped with Nuvoton KM864807.
Amazon FireTV Stick 4K Max is an Android based Media Player (streaming device).
LG OLED G3 is a TV used as Display Device here.
If I use FireTV to play the Netflix movie "Don’t Look Up" then I also can see the Dolby Vision logo like shown above. The HDfury VRROOM features an On Screen Display that can show the signal properties:
| 4K23.975 | resolution and refresh rate |
| DV | Dolby Vision (Standard, Low-Latency would be displayed as LLDV) |
| 297 MHz | TMDS clock frequency (max. HDMI 2.0 = 600 MHz) |
| 2.2 | High-bandwidth Digital Content Protection (HDCP) version |
There is also an HDMI Diagnostics mode on LG TVs you can access yourself:
- Open the settings of the TV by pressing on the gear icon on the remote
- Highlight or move the pointer over the All Settings option and open all settings
- Select the Channels option
- Move the pointer or highlight Channel Tuning
- Press the „1“ key on the remote five times quickly
- Select "More" at the very bottom right
You should then see something like this on your screen:
This is the info for the mentioned Netflix movie and indicates FULL Dolby Vision end-to-end signaling.
The video file you uploaded to Google Drive has the following properties:
Format: HEVC
Format/Info: High Efficiency Video Coding
Format profile: Main 10@L5.1@High
HDR format: SMPTE ST 2086, HDR10 compatible
Codec ID: 36
Duration: 43s 376 ms
Width: 3,840 pixels
Height: 2,160 pixels
Image aspect ratio: 16:9
Refresh rate: 23.976 (24000/1001) FPS
Color space: YUV
Chroma subsampling: 4:2:0 (Type 2)
Bit depth: 10 bits
Color range: Limited
Color primaries: BT.2020
Transfer characteristics: PQ
Matrix coefficients: BT.2020 non-constant
Mastering display color primaries: Display P3
Mastering display luminance: min: 0.0050 cd/m², max: 4000 cd/m²
Maximum Content Light Level: 1000 cd/m²
Maximum Frame Average Light Level: 49 cd/m²
If we look again at my system overview above:
It shows that the display device uses the Extended Display Identification Data (EDID) to tell the source devices what capabilities it has. My computer with the GeForce RTX 3050 has the Media Player Classic - Black Edition (MPC-BE) and the Madshi Video Renderer (madVR) installed. In madVR the EDID data can be checked that arrive there:
If the raw EDID data is parsed in an appropriate tool, we see the following:
Vendor-Specific Video Data Block (Dolby), OUI 00-D0-46:
Version: 2 (12 bytes)
DM Version: 4.x
Backlt Min Luma: 75 cd/m²
Interface: Standard + Low-Latency
Supports 10b 12b 444: Not supported
Target Min PQ v2: 80 (0.00827830 cd/m²)
Target Max PQ v2: 3290 (1604 cd/m²)
Unique Rx, Ry: 0.67187500, 0.32031250
Unique Gx, Gy: 0.24609375, 0.69140625
Unique Bx, By: 0.14453125, 0.05859375
This is the data that the LG G3 television sends out. It can therefore display a maximum of 1600 nits (= candela per square meter, cd/m²) via the Perceptual Quantizer. And these capabilities obviously also reach the computer with the GeForce RTX 3050 and madVR.
But madVR doesn't show Dolby Vision capability in the "identification" tab right next to "raw edid data" tab:
Accordingly, the output is HDR10 when I play your video file in MPC-BE:
The green is the signal diagnosis of the HDfury VRROOM.
For comparison, the properties of the video file again:
- Mastering display color primaries: Display P3
- Mastering display luminance: min: 0.0050 cd/m², max: 4000 cd/m²
- Maximum Content Light Level: 1000 cd/m²
- Maximum Frame Average Light Level: 49 cd/m²
| 4K23.976 | resolution and refresh rate |
| FRL5 | HDMI Fixed Rate Link 5 (40 Gbps) |
| 444 | color model (YCbCr 4:4:4) |
| BT2020 | color space (Rec. 2020) |
| 10b | 10 bits per component (bpc / "bit") |
| HDR | High Dynamic Range |
| SMPTE | Society of Motion Picture and Television Engineers |
| ST 2084 | standard for transfer function used by HDR content |
| LUM | luminance; peak luminance 4000 [nits], black level: 0.005 [nits] |
| maxCLL | Maximum Content Light Level 1000 [nits] |
| maxFALL | Maximum Frame Average Light Level 49 [nits] |
| AUD | Audio signal coming through HDMI cable. HBR bitstream 192 kHz is the maximum possible. HBR = high bit rate, 192 kHz is the sampling frequency. This is the result of using "Dolby Atmos for Home Theater" within the Windows sound settings. This can be done after download and installation of "Dolby Access" app which can be found in the Microsoft Store |
| MTR | Mastering Display Color Primaries (DCI-P3 D65) |
In my opinion, that's fine. However, you have to be careful that the Quantization Range is set appropriately everywhere. In the DirectShow filter, in the renderer, in the graphics card driver and in the processing display. If there is a mismatch, the quickest way to notice is that black isn't quite black.
