Figured that, but I more meant how to decode that to get the list of supported modes. Assuming that you used EDID Decode to get those snippets. That gives me
Vendor-Specific Video Data Block (Dolby), OUI 00-D0-46:
Version: 2 (12 bytes)
DM Version: 4.x
Backlt Min Luma: 100 cd/m^2
Interface: Standard + Low-Latency
Supports 10b 12b 444: Not supported
Target Min PQ v2: 80 (0.00837904 cd/m^2)
Target Max PQ v2: 3095 (1082 cd/m^2)
Unique Rx, Ry: 0.67968750, 0.32031250
Unique Gx, Gy: 0.26562500, 0.69140625
Unique Bx, By: 0.14843750, 0.05859375
which doesn’t indicate that my tv support tv-led DV using a 12-bit YUV422 format - but it clearly does.
Brilliant work as always thanks for your dedication, will test later and report back.
Out of curiosity is uplifting with 21 difficult or that will be later after the final result?
Changes are now fairly isolated, should be fairly easy to change between any version. That is why I can do both the -ng and -no versions without much issue.
Only really using 20.5 because that is what I first started with. Anything specifically in the 21 version that is work updating for? All I’ve really seen is better FEL support which doesn’t apply here
Is mainly addons & plugins like inputstream and such, is all updated in 21. It’s not massively important so it can wait as the main thing is easier for you.
Thanks.
Guess I’m not planning to make a 21.5 version then
@Sholander@xmlcom Didn’t realise people were giving this enough use to care about the version… I’ll update to the latest -ng version next time I play with the code
Why are you surprised? You just broke the first and fundamental law of DV physics, which until your work was: “To reproduce DV material, all devices in the reproduction chain, S0C/Box, transmission and display, must be DV certified”.
Now my N2, which does not have any DV certificates, properly reproduces DV material.
I thought I have been able to play them from within Kodi, but it was from the LG internal player then. Too much tinkering too fast for my brain I guess.
I’ve set it already, but no luck. DTS:X plays well, TrueHD plays fine, only Atmos does not trigger my receiver anymore, but it doesn’t have anything to do with your build I think.
Thank you for your input.
fyi @Sholander@xmlcom and anyone else interested in an update to the CoreELEC version to 21.
Likely not going to happen anytime soon, CE-21 cannot build libdovi from source as is required and I don’t know how to create a patch that would allow that to happen.
Also not going to be any further updates to the -no version until the deal-breaking problems I am seeing in the nighties get resolved.
Despite what was stated by the devs, the problem is the outdated rust version that causes errors that prevent anything compiling.
I have tested this by reverting back to the original 21.1-Omega tag, which to my understanding is well before libdovi was removed. Re-adding libdovi is working for cpm because using the existing libdovi doesn’t involve compiling it. I needed to compile it because I have made some required modification.
with the second one resulting in error about the rust version. This was also a problem in CE-20.5, but thanks to @vpeter a patch was provided that updated fixed the issue.
Based on the file name, and other comments by the CE team, I assume that this patch isn’t applicable for CE-21 - may be wrong here. In any case, I’m do not intend to spend the time myself to try and figure out how to make such a patch - it will surely soon become outdated and broken anyway.
The best approach long term is really to just not use libdovi and just parse the original DV sei bitstream directly in c code. Actually a straightforward task - does not involve rewriting libdovi in c - just a small part. Not something on my immediate to-do list, have other things I would like to look at.
Maybe someone else would be interested in doing parsing in c code? If so, I can say exactly what would be required - essentially just need to extract this struct and any listed metadata blocks.
@Sholander If you can get the two above commands to successfully run on any commit from the coreelec-21 branch, I would move the CE-21 without without much issue.
That or someone write c code that parse the DV sei data the same as libdovi does - that way this problem could never reoccur and would also mean that no modifications to the kodi repo are required either.
