It will be in wrong place until a debug log is provided
https://wiki.coreelec.org/coreelec:ce_support
@bluesea does A2 update include the improved dtb?
10 posts were merged into an existing topic: CoreELEC 21.1-Omega Amlogic-ng Discussion
It does include the dtb
I get what you are saying and my original post mentioned CPM. But my final post on the proper thread ruled out CPM. So now our posts are clogging up the CPM thread when they should be somewhere else. My last post clearly states that this is NOT a blu-ray menu issue. Yet the issue was rejected based on it being a blu-ray menu issue. End of story.
Please stop trying run defense for the indefensible. I made it clear that I understand he is busy and this is voluntary and that should be enough.
Your suggestion for the sample is appreciated and I will try to get the sample created, tested and attached for him to have a look at.
When using CPM build with A2 and the updated dtb, should VC-1 codec movies be played without HW accelerations as software only or “exclude 24” ? I ask because Dolby Vision inverse tone mapping only seems to work with VC-1 and HW acceleration.
Video bit depth is reported as 0-bit which probably explains why VS10mode is Bypass.
@hdmkv Could you update your kodi post to point to CPM’s releases on github?
Use exclude 24p.
Vs10 only works with hardware decoding.
Yes I thought as much but nice to have it confirmed. Thanks.
Thanks That’s what I was doing. But it means that DV inverse tone-mapping no longer works. Probably because the bit-depth is reported as zero. But from recent answers it’s mainly because VS10 only works with hw decoding which does make sense if true and I see no reason why it shouldn’t be.
Just did, sorry for not seeing your request earlier.
Issue with H/W decode VC-1 so use S/W.
As not going through the H/W side cannot use VS10.
I noticed that the HDR InfoFrame Payload is not injected when playing profile 7 Dolby Vision, while it is correctly being injected when playing profile 8. When playing profile 7 MaxDL, MinDL, MaxCLL, and MaxFALL, are all set to 0 in the HDR InfoFrame. All profile 7 files tried thusfar are FEL.
Has anyone else experienced this issue? I can provide more details later today if anyone is intrested and has questions.
I’m using the A2 build from GitHub on a Nokia 8010 and checking the HDR Infoframe using a HDFury Arcana.
Also many thanks to cpm and all others involved for providing this build. I really appreciate it and no pressure in looking at this issue
When cpm was implemeting the HDR InfoFrame Metadata Payload several versions ago, I helped by developing the tab on the spreadsheet that generates the HDR Infoframe Metadata Payload to be copied to cpm’s version. At that time, I tested it and all worked well but have not tested since then. So not sure if something happened along the way. At that time, if you did not insert a Payload then all values would be zeroes (besides PQ byte) since that will trigger the default values for the sink based on CTA-861.3-A standard.
For the P8 and P7 FEL, can ping over the output of:
cat /sys/kernel/debug/amhdmitx/hdmi_pkt
and
grep "" /sys/module/amdolby_vision/parameters/*
and see what the HDR InfoFrame is in each case.
Not directly related to CPM build, but can those commands also be used for debugging why a certain DoVi clip won’t work on an Ugoos AM8 Pro (-ne) but works on AM6B+ (-ng)? The TV usually just stays black, sometimes blinks between DoVi and HDR. I’ve ruled out any cable issues.
Thanks for the response.
I will remove the HDFury from the chain and check the info frames using that method tonight.
Probably best start with setting the dolby debug param to 1 and test and repeat with setting the dolby debug param to 2 and test. See if any pointers in the log around errors etc.
Is there a good reference page or post on what different VS10 settings do and when I might want to use them?
Eg. VS10 Only vs Player LED
Ideally looking for the best settings to maximize DV content on a Samsung HDR 10+ only screen