Dolby Vision Profile, VS10, plus other info on skins

Unsupported/EOL HW/SW Community Projects
389

@cpm Discovered a bug, if you switch from a DV file to a HDR file the values from the DV will remain.

So, you will have an HDR file, but the Dolby Vision - HDR page will report Dolby Vision values. It seems that the code forgets to clear the values when a file is changed.

390

@R3S3T_9999

L6 Min/Max Lum          = BL MDL
L6 MaxCLL/FALL          = BL MaxCLL/FALL
L6 Source Min/Max Lum   = RPU MDL
L6 Source Min PQ/Max PQ = RPU MaxCLL/FALL

?

Please help me.
I’m confused…

391

BL MDL and maxcll are the static HDR10 values reported by mediainfo. @Chros skin has this info so it should be available.

Capture d’écran 2024-10-29 101717
Capture d’écran 2024-10-29 101717930×87 3.24 KB

RPU MDL, is the Source_PQ value
so I would ignore L6 MDL and only use L6 maxcll/fall

392

maybe we need new thread for newer CPM builds so we know which are latest etc depending on who release new builds?

3 Likes
393

So this is correct ?

L6 Min/Max Lum          = BL MDL
L6 MaxCLL/FALL          = BL MaxCLL/FALL
L6 Source Min/Max Lum   = RPU MaxCLL/FALL
L6 Source Min PQ/Max PQ = RPU MDL

I have no idea :skull:
It’s too technical for me, all those numbers… :joy:

394

No,
-L6 and the HDR10 BL metadata are two different things. Look at @chros skin to find out how he displays the HDR10 metadata.

-Source_PQ and L6 values are also two different things.
Source_PQ is the actual RPU MDL while L6 should match it most of the time but not always since many release group will edit it so I would only keep the L6 maxcll/fall value from L6 and take the actual RPU MDL from source_pq

1 Like
395

Gotta say thank you to the @jamal2367 @cpm
CE team and everyone

3 Likes
396

Thank you!

1 Like
397

Thank you very much!!!

398

Thank you for this release.

399

Thank you, much appreciated.

1 Like
400

Yes, then you must make

make clean

or

DEVICE=Amlogic-ng clean kodi

before

What this does ? I was able to make the img yesterday. But I was unable to run “make clean” now on that build and also when I tried to build it once again. I wasn’t able to start clean up with this argument DEVICE=Amlogic-ng clean kodi.

401

to make a full cleanup before building again do:
DEVICE=Amlogic-ng make clean

if you already have a working build and want to just clean kodi package then do:
DEVICE=Amlogic-ng ./scripts/clean kodi

and then to start the build run:
DEVICE=Amlogic-ng make

2 Likes
402

Is that ok to get this warning msg ?

Successful build, creating image…
depmod: WARNING: could not open modules.builtin.modinfo at /home/$user/CoreELEC/build.CoreELEC-Amlogic-ng.arm-21/image/system/usr/lib/kernel-overlays/base/lib/modules/4.9.269: No such file or directory

… maybe some DC server would be nice for better paced conversation (not spaming forum)

403

to my knowledge yes, I also have it (and had for a while)

1 Like
404
405

yes I was facing same issues as Maurice, but I found myself eventually how to fix them.

406

DEVICE=Amlogic-ng make clean
well this is the output I get after execute the cmd:
./scripts/makefile_helper --clean

407

yes, it just shows what ‘internal’ command is issued within the outer make command, nothing wrong here.
if the project is not clean, it will print this command and will wait for quite a while until it’s done and then returns to the prompt. if the project is already clean it will basically just print this command and exit fast.

1 Like
408

I created new thread for CPM community builds for people to use. thank you!

4 Likes