There is no forum rule banning CE from being mentioned. However comparison discussions have a habit of attracting trolls, and we prefer to avoid that kind of behaviour. Just keep the discussion sensible.
Yeah of course I was not aware about that, thanks for the informations
There is no forum rule banning CE from being mentioned. However comparison discussions have a habit of attracting trolls, and we prefer to avoid that kind of behaviour. Just keep the discussion sensible.
Thanks for clearing that up, Chewitt. I completely understand, and I'll keep the discussion sensible and constructive. Appreciate it.
Thank you, I’m just happy to contribute. Your iGPU is similar to mine and considerably more powerful than the N100, so the heavier logging should be less of an issue. I’d still recommend updating to the latest version.
Regarding information similar to CoreELEC, I’m not very familiar with exactly what it displays. But details like the DV profile and CM version should be straightforward to expose, since I already have them in the logs.
As for playback options, I’m currently focusing on standard, TV-led Dolby Vision. Adding LLDV (player-led) would be a substantial project. The player need to handle the display mapping currently done by the TV. That could increase GPU load and make things harder for small Intel iGPU. The main benefit would be compatibility with old TVs that require player-led DV and can not perform the display mapping. That said, I’m less familiar with LLDV, so there may be other use cases or benefits
For me, the most interesting Dolby Vision processing features are:
- Baking DV into HDR10
- Generating HDR10+ metadata from DV
As far as I know, CoreELEC doesn't support this. With a stronger GPU on x86, we actually have the performance headroom to experiment with this kind of workload, and this challenge drives me more. But if you seen more usefull usecases to cover I am listening.
I'm interested in HDR10+ to DV, which I already use on AM6B+ but I have very few HDR10+ only videos.
