[x86-64][CroqueMr Builds] Dolby Vision w/FEL, HDR10+, and 3D

    would love to see what it gets on the cpu benchmark addon
    https://kodi.tv/addons/omega/script.pystone.benchmark/

    and then see how it compares with others here I spent a while making the list (I'll update your score on it)

    Best Kodi-capable, Local Video Playback-focused Media Players in 2025
    docs.google.com
    Quote from Dan007

    Thanks, but no ''always'' option ?

    Or is that what you meant by ''independent L2-trim suppression'' since forcing cmv4.0 disables the L2 trims?

    I do see an "Always" option in RC2.

    CroqueMr I'm happy to report that RC2 has solved the frame rate switching issue that I reported.

    However, for me PGS subtitles are not working properly anymore.

    At first I thought they were not being displayed at all, but when I looked better, I noticed they are now very very small and black instead of their normal color. I tested this on two ripped discs: Avatar 2 and LOTR 1 Extended Part 1.

    I also do not see the brightness or size options for bitmap subtitles that you mentioned in the release notes?

    Quote from Dan007

    Thanks, but no ''always'' option ?

    Or is that what you meant by ''independent L2-trim suppression'' since forcing cmv4.0 disables the L2 trims?

    You have two settings :

    - CM2.9 to CM4.0 : All option available on avdvplus regarding :off, CM2.9 without L2 trims, Always,auto,auto2

    - Remove L2-trim : Yes/No (can be useful on some projector)

    Quote from MrMagic

    I do see an "Always" option in RC2.

    CroqueMr I'm happy to report that RC2 has solved the frame rate switching issue that I reported.

    However, for me PGS subtitles are not working properly anymore.

    At first I thought they were not being displayed at all, but when I looked better, I noticed they are now very very small and black instead of their normal color. I tested this on two ripped discs: Avatar 2 and LOTR 1 Extended Part 1.

    I also do not see the brightness or size options for bitmap subtitles that you mentioned in the release notes?

    Yes, there was an issue when I merged my branch; I’m fixing it now and will include the update in the same release.

    Quote from CroqueMr

    You have two settings :

    - CM2.9 to CM4.0 : All option available on avdvplus regarding :off, CM2.9 without L2 trims, Always,auto,auto2

    - Remove L2-trim : Yes/No (can be useful on some projector)

    Thank you! I was just going by your release notes. This is the option I've been waiting for before trying LibreELEC for the first time (coming from CoreELEC).

    CroqueMr

    First off, thanks for RC2. It's on my 780M box now and it's looking really good.

    I wanted to ask whether you'd consider supporting the OpenGL build of LibreELEC (the Generic.OpenGL device, with Kodi built for GL) as well as GLES.At the moment Dolby Vision only works on the GLES image, so I have to choose between DV for films and the GL image for games. A lot of my time goes into Kodi's game player (RetroPlayer), and some cores and shader presets only work, or only work fully, on desktop GL. It would help beyond LibreELEC too. Most desktop Linux builds of Kodi (distro packages, the flatpak) use GL rather than GLES, so a GL path is what would let your work reach those users, and anything aimed at Kodi itself would need it as well.

    What I think it would take, from going through the RC2 patches: most of the Kodi side isn't tied to GLES, but about 6.5k of the ~23k lines sit in GLES-only classes that a GL build never compiles:

    DVBridgeGLES (~2.9k lines)

    WinSystemGbmGLESContext (~2.7k)

    RendererVAAPIGLES, LinuxRendererGLES and OverlayRendererGLES, plus small bits in RendererDRMPRIMEGLES and the GLES screenshot and filter shader code

    A GL build uses WinSystemGbmGLContext, RendererVAAPIGL, LinuxRendererGL and OverlayRendererGL instead. The way I'd approach it:

    Move the DV/HDR output and DRM handling out of WinSystemGbmGLESContext into WinSystemGbm, or a helper both contexts share.

    Make the DVBridge renderer API-neutral. libplacebo's OpenGL backend takes either a GL or a GLES context, so it should mostly come down to small GL and GLES shims for the EGL image import and the shader headers.

    Mirror the VAAPI, LinuxRenderer and overlay hooks in their GL counterparts.

    Add a Generic.OpenGL build so the GL side doesn't drift.

    I'm happy to help with the Kodi side and to test GL builds on the 780M and know some others who would too.

    Cheers,

    Quote from MrMagic

    I do see an "Always" option in RC2.

    CroqueMr I'm happy to report that RC2 has solved the frame rate switching issue that I reported.

    However, for me PGS subtitles are not working properly anymore.

    At first I thought they were not being displayed at all, but when I looked better, I noticed they are now very very small and black instead of their normal color. I tested this on two ripped discs: Avatar 2 and LOTR 1 Extended Part 1.

    I also do not see the brightness or size options for bitmap subtitles that you mentioned in the release notes?

    Updated : You can re-download RC2 image.

    Installed and working well here. Some feedback on the new features of RC2:

    1. Could the HDR10+ option be separate from the HDR10 options, as you can't currently config HDR10 to DV and HDR10+ to DV without changing it during playback. Also the menu entries in settings remain flagged as (unavailable) based on the previous playing file which is confusing.

    2. Is it possible to show if the CMv4 convertion is active in the PPI? Preferably updating live if one of the auto modes is in use.

    Thanks

    CroqueMr sadly getting the installer USB-Stick to properly boot is proving to be a problem.

    2 different USB-sticks so far have failed and get stuck on the "LibreELEC (Community): DV RC2" screen that comes after the logo.

    The only thing that worked once(also taking like 3 reboots and drive reformats) was the USB SSD, which I need for the OS at the end though.


    So if you could ever offer a way to directly install it to the already correct device without a middle device, just like Hades, that would be great.

    For now I literally cannot get this version to work.

    Quote from nissel

    Installed and working well here. Some feedback on the new features of RC2:

    1. Could the HDR10+ option be separate from the HDR10 options, as you can't currently config HDR10 to DV and HDR10+ to DV without changing it during playback. Also the menu entries in settings remain flagged as (unavailable) based on the previous playing file which is confusing.

    2. Is it possible to show if the CMv4 convertion is active in the PPI? Preferably updating live if one of the auto modes is in use.

    Thanks

    Yeah np I will add that for the RC3


    What is your GPU ?

    Quote from CroqueMr

    Do you use IPT or YCbCr Output for master reference, did you see a regression in term of performance? with master reference in beta5 vs RC2? IPT is far more stressful for your iGPU than YCbCr

    Didnt do any changes what so ever other than uppdating.

    Quote from CroqueMr

    Do you use IPT or YCbCr Output for master reference, did you see a regression in term of performance? with master reference in beta5 vs RC2? IPT is far more stressful for your iGPU than YCbCr

    Quick question: Does the YCbCr vs IPT only change the format sent to the TV and not the PQ? Is the PQ completely identical? DMDReviews seemed to say the standard way is to sent IPT so I switched it to that but not sure if it changes anything in the end?