EDID Override - Injecting a Dolby VSVDB Block

Unsupported/EOL HW/SW Community Projects
73

Latest Update

  • :warning: Changed the Dolby VSVDB to only accept the payload element of only V1 and V2 Dolby VSVDB - allows for simpler code avoiding a couple of pitfalls I cannot test fully for.

    • Only the payload should be specified.
    • If you have a Dolby VSVDB in the UI already you will need to change it for this version.
    • Remove the first 10 characters (in bold below) from your existing entry - for example:
      • Existing: EB0146D000490348A15855A2
      • Replace with: 490348A15855A2
      • This should now always be exactly 14 characters long - that and other checks are in the logic but not checked at the UI level.

  • Limited the Dolby Vision type UI selection according to connected display (mostly)

    • Display Led (DV-Std) [Available when CE says the display is DV capable]
      • I think there is likely a corner-case with old Sony TV which only do Player Led - needs a better differentiator in CE.
    • Player Led (DV-LL) [Available when CE says the display is DV Low Latency capable]
    • Player Led (HDR) [Available regardless of the display capability - but should really check it is HDR capable]

  • Fixed defect - playing original content e.g. HLG HDR without using VS10 - i.e. want the original HLG, it played incorrect as SDR in that situation.

  • Fixed defect in Dolby VSVDB - memory allocation issue - was not causing a visible problem but filling log and would cause some additional CPU usage - side stepped by using a different technique.

  • Fixed defect in Player Led (HDR) - it was frequently re-creating the DV metadata parser (looks on each change of the RPU) - because that bit of code thought a HDR output signal meant it no longer needed it, this is now corrected - probably not even noticeable on CPU usage but better anyway.
    Edit: This may have just been because of a bad mkv need to check more later, if so can revert this element as would not be needed.

  • General code improvements to reuse more - to reduce footprint of change.

Whilst checking on some of the above it looks to me that even though the HLG HDR is “working” with VS10 and we get DV output etc. it looks internally to me that it takes the HLG HDR as SDR and then converts to DV, I tried to force it into going HLG HDR → DV but got a green screen. It looks like this maybe a limitation on the SoC level I think some later TV SoC can handle more correctly likely on a later revision of DV.

Not done too much testing on this version yet, put it out as will be away for a time, please revert back to previous versions if you find a show-stopper.

8 Likes