EDID Override - Injecting a Dolby VSVDB Block

Feature Complete - Update 5

  • Fix defect with DV content and [GUI peak luminance in HDR PQ mode] not being applied.

  • Change VS10 up and down mapping to: SDR, HDR10, Dolby Vision

    • After further investigation in linux-amlogic even though there are clear modes for SDR8 and SDR10, for the DV Engine both come down to just SDR and sent for processing the same way, so no point having two distinct options in the UI.

    • Have left in [for SDR8] and [for SDR10] → SDR mapping which may appear counter intuitive, but until proven that it does nothing useful in both cases (i.e. requires capture and compare analysis) leaving them in for now.

    • Note for HDR HLG that is also sent to the DV Engine as SDR [sending as HDR HLG does not work - at least on the g12a/b SoC] (probably why the colours are off - to my eyes), have noted this in the UI help text, but left in the mapping in incase the user does not have a HDR HLG Display - this mapping may still be useful in that situation.

  • Add testing ssh parameter for max luminance control. (More on that later) @philgaultier

  • Code refactoring

    • Various improvements (no user visible changes)

When testing use the below tar to update a fresh install of CE-21 ng.

[Version Removed] please use next version here.


Dolby VSVDB Calc (no update)


P.S.

Even though [Feature Complete] was thinking maybe one more!, if there is suitable need and genuine interest.

Currently if playing content with both DV and HDR10+ enhancements it will pick DV.
Could add another option in that case to prefer the HDR10+ instead.

Note: [GUI peak luminance in HDR PQ mode] cannot distinguish HDR10+ so would have the caveat for that, as per post on last update, in this case it would take the luminance control as per DV (VS10 config).

Note: There is talk of having something like this upstream in Kodi - if that materialises later then no need to do it here, and should be able to then resolve the luminance control issues as well.

2 Likes