Start with HDR10.
Prove a normal HDR10 path first. This establishes HDMI bandwidth, HDCP, EDID, color format and the display's HDR presentation before adding Dolby Vision variables.
HDR10, NATIVE DV
OR LLDV?
These are different workflows. The correct starting point depends on the display and source. Vertex controls the HDMI environment; it does not make every display a native Dolby Vision display.
Prefer native DV.
On a native-DV television such as an applicable LG, Sony or Philips model, native TV Dolby Vision is the reference path. Vertex can still manage EDID, routing, legacy AVR integration and mixed displays.
Test player-led DV.
Vertex can present an LLDV EDID that you upload into a custom slot (there is no built-in LLDV table) — see Vertex part B. A compatible source performs player-led Dolby Vision processing. The HDR projector still needs an appropriate HDR presentation.
CONTENT → SOURCE PROCESSING → VERTEX EDID / SIGNAL CONTROL → DISPLAY HDR PRESENTATION
Do not confuse the roles.
In an LLDV workflow, Vertex is not the Dolby Vision dynamic tone-mapping engine. It facilitates the HDMI/EDID/DV-capability workflow. The compatible source performs player-led Dolby Vision processing.
In an LLDV workflow, Vertex is not the Dolby Vision dynamic tone-mapping engine. It facilitates the HDMI/EDID/DV-capability workflow. The compatible source performs player-led Dolby Vision processing.