Low-Latency Dolby Vision (Player-Led) Low-Latency Dolby Vision (LLDV), player-led Dolby Vision

What LLDV is

Dolby Vision can cross an HDMI cable in two ways. In the original, TV-led form (also called standard or display-led), the player sends the picture plus dynamic metadata and the display's Dolby Vision engine does the tone mapping. In Low-Latency Dolby Vision, the player does that work. HDfury, which builds HDMI processors that handle both, defines LLDV as Dolby Vision that is tone mapped by the player, scene by scene, with the output being a standard 12-bit YCbCr 4:2:2 stream with a PQ (ST.2084) transfer function that an HDR10 display can show. The player reads the display's EDID to learn how bright the panel is, then fits the picture to that figure.

The name comes from where the delay goes. Light Illusion describes the low-latency signal as a plain 12-bit YCbCr 4:2:2, PQ, Rec.2020 signal with a low-latency flag, and says low-latency support is now required for new Dolby Vision devices while the TV-led mode is optional. That is why Dolby Vision gaming runs this way: a console cannot wait for a TV's dynamic mapping on every frame.

How the two transports differ on the wire

TV-led Dolby Vision looks like an ordinary 8-bit RGB signal on the cable, but it is a wrapper. A Dolby patent on transmitting display management metadata over HDMI (US 9,906,765, granted February 27, 2018) describes the scheme: a 12-bit YCbCr 4:2:2 frame is repacked into an 8-bit RGB 4:4:4 signal so it can cross a legacy 8-bit link, with each 12-bit sample split into a lower 4-bit part and an upper 8-bit part, and the metadata placed in the least significant bits of the picture. Light Illusion adds the consequence: the metadata lives in the pixels, so the signal must be bit-perfect, and any change to pixel values breaks it. An analyzer showing 8-bit RGB is reading the wrapper, not the picture.

LLDV carries no such hidden payload. The InfoFrames carry a Dolby Vision flag with the low-latency bit set, and there is no HDR10 InfoFrame. Both transports have the same bandwidth at 4K 60Hz: a 594 MHz clock, which fits HDMI 2.0. HDfury notes that LLDV at 4K60 in 12-bit 4:2:2 is a full 18 Gbps signal, so a long run needs certified 18 Gbps copper up to about 3 to 4 m, or fiber, and most film content at 4K24 fits a 10 Gbps projector.

Player-led vs TV-led: which maps better

HDfury's glossary says TV-led is usually more accurate on a real Dolby Vision TV, because the display knows its own panel, and that player-led is mainly useful for displays without Dolby Vision. The player-led path has limits spelled out on HDfury's LLDV page. The player knows only what the EDID says, and a declared Tmax of 10,000 nits effectively hands tone mapping back to the display, so HDfury recommends starting at 1,000 nits. The display's own dynamic tone mapping should be off or highlights flatten from double mapping (see source versus display tone mapping). HDfury also reports one reviewer measuring worse color accuracy from an Apple TV in LLDV than from native HDR10, and says the benefit shrinks on TVs with strong built-in tone mapping.

How a TV advertises support is visible in its EDID Dolby Vision block. Light Illusion's examples show the LG CX declaring TV-led up to 4K 60Hz plus Low-Latency in 12-bit YCbCr 4:2:2, and the TCL 65C855X1 declaring the same. A monitor such as the ASUS ProArt PA32DC declares Low-Latency only. A source that sees a TV-led capable block can choose either mode; one that sees only low-latency sends LLDV.

Which devices output LLDV

HDfury's official list of LLDV sources is long: Apple TV 4K (all generations), NVIDIA Shield TV Pro (2019 and later, firmware 9.1.1 or newer), Xbox One X/S and Series X/S, Sony UBP-X700, UBP-X800M2, and UBP-X1100ES, Panasonic UB820 and UB9000, Oppo UDP-203 and UDP-205, Fire TV Stick 4K, 4K Max, and Cube, Chromecast with Google TV, and Zidoo players. Only some of them convert non-Dolby content to LLDV: the Apple TV 4K, Sony X700 and X800M2, Oppo on disc playback, Fire TV in its Always HDR mode, Roku 4K, and Zidoo can, while the Shield, Panasonic players, and Xbox output LLDV only for native Dolby Vision content. On Xbox, HDfury notes that HDR10-only games cannot get dynamic tone mapping through metadata injection. Microsoft launched Dolby Vision gaming on Xbox Series X|S on September 28, 2021, with more than 100 optimized titles.

On the Apple side, Apple's support page says the Apple TV 4K needs the TV to display HDR10, HDR10+, or Dolby Vision at 60Hz (50Hz in Europe) for automatic setup, and offers Match Dynamic Range to switch formats per title. Which wrapper it sends depends on the format the TV's EDID accepts. See Apple TV 4K for the box itself.

Dolby Vision on HDR10 displays

The reason LLDV matters for buyers is Samsung. Samsung TVs do not support Dolby Vision natively, and HDfury says any display that accepts HDR10 PQ can take LLDV, including all Samsung sets, when an HDMI processor presents a Dolby Vision EDID block to the source. The display then runs in its normal HDR10 mode. Samsung sets need Input Signal Plus or HDMI UHD Color enabled on that port, or the port stays limited to 8-bit and rejects the HDR flag. Some AV receivers and soundbars strip or rewrite the Dolby Vision block, so the box should sit directly at the display. A DCI-P3 primaries entry in the EDID can produce a red or magenta tint, so BT.2020 is the usual default. Anyone with a real Dolby Vision TV should leave the source in standard TV-led mode where the device offers a choice. For the profile side of the format, see Dolby Vision profile 8.1, and for display-side picks see best TV for gaming.