[x86-64] Dolby Vision w/FEL + Full 3D for PC (Intel & AMD, nVidia)

  • Don't buy extra RAM, it won't help. This conversion process is just a draft in Beta3 and will be optimized in Beta4, maybe your hardware will be good enough

    I've already updated the basic HDR10 conversion in my internal beta4 preview build, but since it's heavy on the GPU, I think low end chips like the N100 won't handle it, but we will see after the rebuild of the pipepline. In the next release Beta4 the performances and optimization will not moved we will be close to the R1.0.0 stable. Important point, in Expert mode, tone mapping is managed by the rendering engine in LE, so be sure to disable tone mapping on your TV/projector.

    Determining whether a CPU/iGPU is powerful enough is tricky. Performance relies heavily on the rendering engine in the GPU, which is hard to benchmark, and other limiting factors are still not perfectly understand.

    Brilliant I'll wait then! Thought maybe it was the memory bus/bandwidth from single stick of ram instead of 2. Thanks for all your efforts I've genuinely got a smile on my face finally something works.

  • I've reviewed your code, and unfortunately, it's based on an old version of my build. We've made significant progress since then, particularly in performance optimization. As it stands, your build will struggle quite a bit on weak CPUs.

    Your NVIDIA integration looks good, though. I'll incorporate it into my release this weekend :)

  • I've reviewed your code, and unfortunately, it's based on an old version of my build. We've made significant progress since then, particularly in performance optimization. As it stands, your build will struggle quite a bit on weak CPUs.

    Your NVIDIA integration looks good, though. I'll incorporate it into my release this weekend :)

    Hey Croque, glad you took a look at it and that you're planning to implement some things in your build!!!

    I actually started working on this the very day you first shared your code, trying to get it running on my hardware and experimenting with other implementations. I've also made quite a few general updates to the code since then, but I'll check out the latest changes in your fork to see if there are any useful optimizations I might have missed. Thanks for the heads-up!

    So far, it's been running pretty well on the hardware I've tested, although I haven't tested it on that many different setups, and none of them have been particularly low-end since I don't really have any modest hardware at home. I guess that could explain why I haven't encountered the issues you mentioned, which would make sense.

    The lowest-end hardware it's been tested on so far is a borrowed laptop with an Intel i5-12450H. I also want to test it on a couple of laptops I have at home, but neither is exactly representative of lower-end hardware (one has a Ryzen 9 5980HX with an RX 6800M, and the other has an i7-12650H with an RTX 3080 Ti Mobile).

    So if anyone else gives it a try and notices any performance issues, please let me know!

  • Send me the complete log please. I will check

    Was finally able to solve my own issue. Turns out changing the refresh rate to 120Hz messes up Libreelec recognising the TV's ability to play dolby vision. Switching it back to 60Hz and now all is well again. Funny enough if you switch to 120Hz within the Kodi it still works as long as you don't reboot ;)

  • Was finally able to solve my own issue. Turns out changing the refresh rate to 120Hz messes up Libreelec recognising the TV's ability to play dolby vision. Switching it back to 60Hz and now all is well again. Funny enough if you switch to 120Hz within the Kodi it still works as long as you don't reboot ;)

    That's possibly the same "bug" that I saw in CoreElec NO when I was talking to Portisch. He pointed me to a line of code that checks if a certain bit in the Dolby Vision VSVDB (Vendor Specific Video Data Block) in the EDID of the display is not ON then this says that the display cannot do DV at 120Hz. I have an older TV that cannot do DV at 120Hz and one that can and the bit was different on both, that's how I found out about the bit.

    The problem is, it seems that CoreELec NO is checking the GUI Hz wrongly and thinks the video that you are starting the playback is a 120Hz video even if it's the GUI that is 120Hz and not the video. Probably something about when the video starts the playback because I was seeing 2 or 3 times switching res and/or Hz in the kodi log.

    I still have the picture of the bit it's this one:

    dv_reserved_bit.png

    It says "reserved" but it's in fact called "Parity" and it'S a 120Hz compatibility bit for DV for the display. That picture is just from an older DV Header when it didn't yet serve any purpose.

    I said to Portisch maybe this should be fixed but he just said use 60Hz in GUI so I did that on my AM9 Pro. I also think it may be from LibreElec 13 since CoreElec NO is a fork of LibreElec 13 if I am not mistaking. So that's why we see it here too maybe?

    On my AM6B+ with CoreElec NG I do NOT have that problem and am using 1080p 120Hz and DV works fine so they changed or added the check for this bit in CoreElec NO / LibreELec 13.

    Portisch replied with the line of code for the check here:

    Amlogic-NO discussion
    This is your bit: So don’t use higher than 60Hz! And read Wiki how to provide logs:
    discourse.coreelec.org

    The line of code is here:

    common_drivers/drivers/media/vout/hdmitx_common/hdmitx_edid_parse.c at 5.15.196_20260225 · CoreELEC/common_drivers
    Contribute to CoreELEC/common_drivers development by creating an account on GitHub.
    github.com

    I don't see "common_drivers" in LibreELec's git repos though... I will try to put 1080p 120Hz and see if I have the same problem.

    ...

    tested and I do NOT have a problem playing back DV while my GUI is at 1080p 120Hz. This may be a CoreElec NO only problem and maybe this has nothing to do with bang gun 's problem? It sure looks like the same problem from what he his experiencing though but I don't experience that like I did on CoreElec NO. Also, if I do a search for "dv->parity" in LibreElec's repo I find nothing.

    Which file were you trying to play bang gun ?

    Edited 4 times, last by Creator44 (October 16, 2026 at 3:44 AM).