EDID Override - Injecting a Dolby VSVDB Block

[rover2001]

I set the UI to 1080p@60/59.94 to solve this problem. It did happen both in CE an Android from day one. Assumed the HDMI port of AM6B+ is not so good enough.

[rover2001]

this is the key to make everything back to normal. Thank you.

[okvcos]

Thank you @rover2001 , but it’s not a solution, I always have to manually change the resolution to 2160p

[cpm]

@okvcos

implement HDR10+ encoding

Will need quietvoid’s buy in as best way will be a new method on exposed capi, at this point not even sure it is achievable just putting it out there as seems plausible.

@okvcos

I’d like to lock the screen resolution when turning on.

Don’t know how to fix the resolution on boot - maybe others can help.

---

In meantime next element from me will be allowing VS10 on the software decoders - currently it is just coded for the AML HW decoder.

FYI: If you put the device into DV Mode: [On] then play a vc-1 24p using the ffmpeg s/w decoder it is leaving DV on as not knowing to switch it off or leave it on, and conversely for DV Mode: [On Demand] it will never be in DV.

[Boulder]

I wonder if you can use a trick to echo the desired output mode to /sys/class/display/mode.

[cpm]

Feature Complete - Update 11

• Add vs10 for all decoders
  • For example vc-1 progressive 24fps software decoding (courtesy of @PurplePlayer) can now by given the vs10 treatment as to personal preference.
  • OSD for such decoding will now also follow the GUI Peak Luminance setting as per hdr/dv usage.
  • Significant refactor of where DV open and close is done, positions code better for when HDR10+ can be identified upstream.

---

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

Update tar

---

Dolby VSVDB Calc (no update)

---

If upgrading from an older version and you experience issues with wrong playback mode e.g. DV playing in HDR etc. then try:

• Set - For Dolby Vision [SDR]
  • Play some DV content
• Set - For Dolby Vision [off]
  • Play some DV content

[OCEFDA]

@cpm

FYI: If you put the device into DV Mode: [On] then play a vc-1 24p using the ffmpeg s/w decoder it is leaving DV on as not knowing to switch it off or leave it on, and conversely for DV Mode: [On Demand] it will never be in DV.

@cpm is this comment in relation to your version FC10, or FC11, or something else?

Thank you.

[cpm]

Comment was for FC10 and previous versions with the [DV Mode] switch.

For FC11 I moved the logic for DV Open (On) and DV Close (Off) up to the VideoPlayer level out of the AML HW Codec level so other Codecs are now included.

There is still a caveat on HDR10/HDR10+, because cannot differentiate that currently above the Codec level, so DV On / Off logic for that is still only in the AML HW Codec. But when/if can detect HDR10+ earlier in the process then can remove that limitation as well. Guess not to much HDR10 software codec usage anyway.

[cpm]

@okvcos

Can likely combine with the below to trigger the mode switch on hot plug - I think a good chance that could work:

EDID Override - Injecting a Dolby VSVDB Block

Regarding the caveats on hotplugging, I solved this with a udev rule. In .config/udev.rules.d/ I created a file named 99-edid.rules with the following contents: ACTION=="change", SUBSYSTEM=="extcon", ATTR{name}=="hdmitx_extcon_hdmi", ENV{STATE}=="HDMI=1", RUN+="/bin/sh -c \"[ -f '/storage/.config/edid.bin' ] && echo 'load /storage/.config/edid.bin' >/sys${DEVPATH%%/*}/edid\""

Need to change the RUN element to trigger the mode instead of loading an EDID.

[cpm]

Looks like just triggering TV and graphics layer to be DV, but not the video layer, not seeing logging to say processing the video through the DV Engine, so guess on the kernel side it has to still be a hardware decoder.

Had some setting difference on TV between SDR, HDR and DV so saw a small difference, but probably underlying is the same.

Will leave in for now as less mode switching.

[anon62335196]

Trying to help a friend set this up on his Sony TV with only HDR support.

What is the best way to determine the new VSVDB? Is it through the calc spreadsheet, or is it this method:

EDID Override - Injecting a Dolby VSVDB Block

It needs your EDID as a base, the first tool is for both Mac and PC so should be good if you did not know , it is not hard - better to teach how to fish Do you have the original spreadsheet that png was taken from? Would be useful to have. Steps required: Make sure the Ugoos is connected in your normal setup, projector, receiver etc. without your LLDV converter device. ssh into the Ugoos ssh needs to be enabled for CoreELEC via the settings use terminal on mac to access the u…

[cpm]

You will need to work out the VSVDB payload, so need to use the spreadsheet calc, the other post you refer to was adding that payload (once calculated) to an EDID, no longer need to do any of that as the payload is directly injected in the code now.

Basically need to know what colour gamut the TV works with, and min and max luminance.

There are a couple of other options, for your case Player Led (HDR) - need to be supported lldv yuv422 12 bit the option on the left, the ones on the right for 10 and 12 should be set unsupported.

As most people probably doing this for Player Led (HDR) I think I should update the spreadsheet to default to those settings.

[DMDreview]

Maybe I’m missing the point of the question, but isn’t it possible to find out what’s in the file by mediainfo
for regular HDR will have the line
HDR format : SMPTE ST 2086

If there is HDR10+, there will be a line containing SMPTE ST 2094.

[cpm]

@DMDreview

SMPTE ST 2094

Needs support in the kodi/ffmpeg combo used.
Was not there yet last time I checked, so currently looking directly at the frame side data.

Current kodi/ffmpeg identification logic:

  if (av_stream_get_side_data(pStream, AV_PKT_DATA_DOVI_CONF, nullptr) || convert_dual_stream) // DoVi
    hdrType = StreamHdrType::HDR_TYPE_DOLBYVISION;
  else if (pStream->codecpar->color_trc == AVCOL_TRC_SMPTE2084) // HDR10
    hdrType = StreamHdrType::HDR_TYPE_HDR10;
  else if (pStream->codecpar->color_trc == AVCOL_TRC_ARIB_STD_B67) // HLG
    hdrType = StreamHdrType::HDR_TYPE_HLG;
  // file could be SMPTE2086 which FFmpeg currently returns as unknown
  // so use the presence of static metadata to detect it
  else if (av_stream_get_side_data(pStream, AV_PKT_DATA_MASTERING_DISPLAY_METADATA, nullptr))
    hdrType = StreamHdrType::HDR_TYPE_HDR10;

https://ffmpeg.org/doxygen/trunk/pixfmt_8h.html#ad4791ea14975f098b649db7fcd731ce6

Not seeing any stream level metadata to help.

Tried to peek a frame (using ffmpeg lib) to get the frame level metadata but also could not get it working, and even if working probably not easy with ffmpeg to seek back across all streams smoothly.

One solution maybe to shell out to media info - but then loading will take longer etc.
At this point I would guess media info is also looking at the first frame to get the side data.

[cpm]

Feature Complete - Update 12

• Dolby VSVDB Payload Injection

  • Improved way to inject payload, with smaller code change footprint.
  • Toggling off the VSVDB Payload UI switch will now revert (on next play) to the connected hdmi’s dv-info (VSVDB) instead.
  • Hot plugging in a different display should now dynamically show the DV Type options for that display - previously had to reboot.

• FFmpeg Decoding

  • Switch off DV if on - as DV Engine not used.
    • Prefer not to have the “Fake” DV - i.e. not using the DV Engine just the display has been triggered into DV setup and now just have the display in the correct mode for the content.
  • VC-1 Side Note:
    • I had partial success on getting VC-1 24fps 1080p using AML HW decoding working correctly. - By removing “deinterlace” from the vmap used.
    • Under the hood the HW decoder was always correctly decoding as progressive, but output only half the image with “deinterlace” in the vmap.
    • But this resulted in a 10fps frame rate drop though so to not useful at this point, something else not right.
    • Oddly putting into 50 or 60 hz improves things but still not correct, nothing on the system looks strained, and no frames are skipped it just runs slow in 24 hz.

• Mode switching

  • Alternative approach to deal with DV-Std CD 12bit.

    • Setup mode and toggle frame on AML side before video playback.
    • No need to wait for video playing.
    • I think no frames are now hidden on playback.

  • Re-work DV On / Off mode switching again to take advantage of above, and think should now have the most minimal switch time.

    • Still see the video rewinding back on start of playback most of the time, e.g. it plays 1 sec then seeks back and plays again from the starting point - think this must be something in Kodi.
    • Audio is taking a while to get going as well 1-2 sec on start of playback, again I think this must be something in Kodi.

---

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

Update tar

---

Dolby VSVDB Calc (no update)

---

If upgrading from an older version and you experience issues with wrong playback mode e.g. DV playing in HDR etc. then try:

• Set - For Dolby Vision [SDR]
  • Play some DV content
• Set - For Dolby Vision [off]
  • Play some DV content

[DMDreview]

You are doing a great job. Maybe you can find the source of the problem of audio sync after rewind or chapter transition when playing from M2TS DV with FEL layer. The problem is exactly with m2ts, mkv has no problems with audio unsynchronization.
For some reason CE team ignores the problem, although it exists and confirmed.

[vpeter]

@DMDreview

For some reason CE team ignores the problem, although it exists and confirmed.

You really want to go with this tone? Does team CE owe you anything?
Users want lot of things but time is limited for devs. Which do work for free you know!

And one more thing: When I see such posts as yours my desire to do any work just go down.

[DMDreview]

I didn’t mean to offend anyone, what the CE team is doing is a great job, I just see that there are no reports on this problem, no reaction from the CE team (maybe I missed such reports). That’s why I suggested @cpm, maybe he can find the cause faster.

[dragonorp]

downloaded the 11 version, using an HDR10+ dislplay (s95b). playing kung fo panda shows screen as green and purple. I set settings to player led HDR and payload with bt2020 space.

any reason why it doesnt work well?

[cpm]

Just to rule things out, try this first - don’t think it would be the issue but easy to check:

• Set - For Dolby Vision [SDR]
  • Play some DV content
• Set - For Dolby Vision [off]
  • Play some DV content

If still have the issue with For Dolby Vision [off] then paste the Payload you have typed in here, and can check it.

If the Payload is not accepted / invalid then would expect the purple and green you see.

Can also try using the the Payload in the help text as below, that I think would at least get past the purple and green but not to spec for your display.

2A3801515999AA