Repository navigation
Replies: 3 comments
|
Implementing in the next T4d_dev build, exposing both InfoLabels for compatibility. Thanks! |
0 replies
|
Switch to the beta channel in CE Settings to get the latest build, where the two InfoLabels are exposed. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Hi,
@R3S3t9999 requested that I display the EDID target brightness in my PPI when using player-led Dolby Vision.
https://forum.kodi.tv/showthread.php?tid=388348&pid=3306586#pid3306586
Looking through the source, Kodi already reads the Dolby Vision display capabilities and calculates maximum luminance in
DolbyVisionAML.cpp, but I couldn’t find aPlayer.Process()label exposing that value.Would you consider adding one that returns the target maximum luminance in nits? For example,
Player.Process(amlogic.dv.target.max.nits), although I’m happy with whatever naming fits your implementation.Ideally, this would report the effective target used for player-led output, including any active VSVDB injection or override, with documented behavior when the value is unavailable.
That would let me display it in PPI using a supported interface without reading sysfs or interpreting settings myself. Having the same label and behavior across both builds would also make skin support easier.
Thanks!
All reactions