Reference
HDfury Diva pro tips: Dolby Vision, EDID, ARC cables and frame rates
A collection of hard-won details from HDfury and the community. Most of them explain behaviour that looks wrong at first sight but is not.
Dolby Vision
Dolby Vision modes 0 and 1 travel through an 8-bit RGB container, so it is entirely normal for the Diva to report RGB 8b while such a DV mode is playing. Nothing has been lost.
If the Diva is not connected directly to your Dolby Vision TV and there is other equipment in between, connect the Diva TX0 output straight to the TV input first and let the Diva boot. Then disconnect and insert the other equipment in between. The Diva sniffs the DV string from your TV EDID and presents it to your source, which is what lets Dolby Vision travel through equipment that does not itself support it.
EDID
You can read one connected sink EDID, or mix two or three of them, apply forced flags and an algorithm to the result, and then save it as an EDID file. That is how you build your own custom EDID variation rather than settling for one of the predefined tables. The EDID tables and Automix page covers the flags and algorithms involved.
Some sources, the Xbox One S and the Samsung K8500 among them, may need their power cord removed and reconnected between EDID changes before they will look at the new EDID.
Audio and ARC
The TX0 output is the CEC, ARC and eARC capable one, which is why it is the output you connect to the TV when you want audio to come back the other way.
Atmos over ARC requires an HDMI cable that supports 192kHz ARC. A cable can carry a 600MHz video signal perfectly and still fail on the 192kHz audio signal, so if Atmos over ARC drops out, change the cable before you change anything else.
AVI infoframe examples
If you are writing custom AVI infoframes in the HDR and Dolby Vision section, these examples are a useful starting point.
| Signal | AVI infoframe |
|---|---|
| BT.2020 RGB | 00:E8:64:5D:00 |
| BT.2020 YCbCr 4:2:2 | 20:E8:64:5D:00 |
| BT.2020 YCbCr 4:4:4 | 40:E8:64:5D:00 |
| BT.2020 YCbCr 4:2:0 | 60:E8:64:5D:00 |
| 4K24 4:2:2 709 YCbCr, no BT.2020 | 20:88:00:00 |
| 4K24 4:2:2 YCbCr BT.2020 | 20:c8:60:00 |
| 4K24 4:4:4 709 YCbCr, no BT.2020 | 40:88:00:00 |
| 4K24 4:4:4 YCbCr BT.2020 | 40:c8:60:00 |
| 1080p 4:2:2 709 YCbCr, no BT.2020 | 20:88:00:10 |
| 1080p 4:2:2 YCbCr BT.2020 | 20:c8:60:10 |
Control
iRule uses \x0D instead of \r to terminate an RS232 command string, and \x0A instead of \n. If your commands work from a terminal but not from iRule, that is usually why.
Reported values
Any 4:2:2 signal is always processed at 12-bit and never clipped. That is why the Diva describes such signals as up to 12b.
Frame rate is the other figure that surprises people. Very few devices report the correct frame rate, because it is really about clock frequency: the theory says 24/1.001 = 23.976023976, but there is no phase-locked loop at the source producing a clock that yields exactly that. Once a signal leaves the source the clock is always slightly off, and it ebbs and flows continuously. HDfury decided to show what the clock really is from that particular source rather than approximating what it ought to be, which is what most other devices do because they cannot report an exact frame rate.