In plain language
Dolby Vision supports up to 12-bit colour and, more importantly, dynamic metadata. Each scene comes with its own guidance about how to map the content onto whatever brightness the display can actually reach. On a screen that cannot hit the mastering brightness — which is most screens — that guidance is what keeps highlights from clipping and shadows from crushing.
It is a licensed format, so both source and display need Dolby Vision support, and the capability is communicated through a specific Dolby Vision data block inside the EDID.
Why it matters in your setup
That data block is where Dolby Vision goes wrong in real systems. Put an AV receiver or a switch between player and television and the block may not survive the trip. The player then never learns the display supports DV, and quietly falls back to HDR10 — with nothing on screen to say so.
Sources also remember. A device that has already tested a given EDID will not retest it, which is why changing EDID can trigger a fresh Dolby Vision check.
What the DR HDMI 8K does with it
The DR HDMI 8K has a dedicated Dolby Vision section. It sniffs and stores the DV data block from the connected display automatically, deciphers it into readable form, and can carry that stored block into an AutoMix EDID — so DV keeps working even with other equipment in between. You can also construct a custom DV data block by hand: interface type, primaries, YUV422 12-bit, global dimming, backlight control and minimum luminance, with fully custom primaries and luminance values if needed.
Need the hardware?
Open the DR HDMI 8K product page on HDfury.uk.