what TV are you using?
philips 65" oled 808, from 2023.
this tv is comparable with lg c2, even better (it has dts support). peak brightness is around 800 nits.
it has even support for hdrp10+ adaptive. and of course also dolby vision support
computer is connected to hdmi port 1 (with 48gbps support, 4k 120hz)
kodi gui resolution is set to 1080p at 30hz, to reserve more power for video playback
Display Morehi, my first post on LE forum. and my findings about this project
LE image version 0.2.1a opt1
my hardware:
asrock industrial x1314
intel i5-12400 cpu (has uhd 730 as igpu)
corsair 64 gb (4* 16gb at 2133mhz), ordinary memory (no ecc or no registered)
i installed bootable img.gz LE on samsung 256gb usb stick
booted and at LE bootscreen did RUN command (works like as Live Linux usb)
tried couple of DoVi FEL movies (mkv and bdmv)
my findings:
all my FEL-movies play as HDR10
tried with cheap ass hdmi cable and with high-end hdmi cable. even with high-end hdmi cable i get hdr10 according player proces info (key O during playback in kodi, O of Otto).
hdmi cable isn't the cause, because the same cable i use with minix u22-xj (coreelec panal p3i) and i get FEL according PPI.
is there anything that i am missing to get FEL?
Can you send me the kodi.log file please?
It seems a driver issue, the system consider your iGPU as not supported, but I should be able to confirm with your kodi.log file.
Also ISO file is not read properly in this release, Kodi take the HDR10 video track (it's fixed in my internal build)
FI : My next release will be huge with many new features, and will extend supported drivers for Intel iGPU and with a first version of AMD DV drivers. Should be published next week if everything goes smoothly.
Can you send me the kodi.log file please?
It seems a driver issue, the system consider your iGPU as not supported, but I should be able to confirm with your kodi.log file.
Also ISO file is not read properly in this release, Kodi take the HDR10 video track (it's fixed in my internal build)
bdmv is a bit different from iso
https://paste.libreelec.tv/multispired-jaye.log
playing movie CLOUD ATLAS 2012 (FEL movie) as bdmv
2nd log, playing Titanic movie (FEL) as mkv
https://paste.libreelec.tv/squirmiest-adah.log
during mkv-playback the fos drops to around 12-13fps when i press O button for PPI information. closing PPI sets playback fps back to around 24fps
Looking forward to it. With AMD, could the 3D work by cinemaONE be merged at some point. Thought of DV FEL + perfect 3D in a non-Amlogic box sounds amazing.
Everything is possible. Unfortunately, I think the merge won't be straightforward
I don't have a 3D TV or the hardware to test it and be sure that everything is correct. I'll state right now that I won't be doing the merge, but if cinemaONE feels up to integrating my DV engine into its work and build, it would be my absolute pleasure.
ht2tweak CroqueMr Thanks for the offer. Some background first:
I'm happy to put work into a combined build as long as those helpers can be licensed GPL-2.0-or-later. Is that possible, or does their PGenerator-Plus origin rule it out? If it works out, I'd start once your AMD release is out. I can test DV now and then on a Panasonic TV, but more testers would be welcome.
Prepared with Claude Code (Anthropic)
ht2tweak CroqueMr Thanks for the offer. Some background first:
- The 3D playback in my builds is mainly work by popcornmix (Kodi and the FFmpeg MVC decoder); bringing it to Kodi upstream is his call. My part is the AMD kernel side (HDMI 3D output in amdgpu, under review at AMD) and some Kodi fixes.
- Your transport helpers, CroqueMr, are GPL-3.0-or-later. Linked into Kodi, they make the whole Kodi binary GPL-3, and that could never go upstream the way the 3D work is meant to.
I'm happy to put work into a combined build as long as those helpers can be licensed GPL-2.0-or-later. Is that possible, or does their PGenerator-Plus origin rule it out? If it works out, I'd start once your AMD release is out. I can test DV now and then on a Panasonic TV, but more testers would be welcome.
Prepared with Claude Code (Anthropic)
I need to review the licensing details properly,I relied on ChatGPT for that early on. The repo right now is a bit of AI-slop, but I'm doing a complete rewrite for the next release. I mostly just wanted to push the code quickly to identify big compatibility bugs.
Everything is being redone and cleaned up (even the implementation of DV support) the new release should drop next weekend (Saturday or Sunday).
A little bit of teasing but I am working on something cool 👀, a lot of thing to fixe before a potential release of this feature, I don't think this one will be available next weekend.
i thought VRR was important for gaming, not for media or video playback.
QMS has something to do with video playback
I apologise for my confusion, but which is the latest version please - R0.2.1a-opt1 or R0.3.0?
I have N5095, N100 and N150 mini PCs I can test on.
I apologise for my confusion, but which is the latest version please - R0.2.1a-opt1 or R0.3.0?
I have N5095, N100 and N150 mini PCs I can test on.
The R0.3.0 is a pre-release with added features not perfectly stable (DV to HDR10 conversion, and Player Panel information). For testing R.0.3.0 will be better because of more precise log.
Feel free to test it and report any issue and if possible with the kodi.log attached. I will investigate and fix it for my next release in a few days. 
I will probably have my new NUC with N150 ready in a couple of days, looking forward to test your new build.
I also have a ASRock N100 DC-ITX with 16GB DDR4 RAM that i could run tests with.
Also my small finding when I compare a 226V and a 11390H : even if the GPU is far stronger on the 226V the rendering engine that handle all the workload is similar in term of performance.
I will compare with a N100 and a N95, I think it is also similar. If it's the case, iGPU support will be wider than I expected and trying to improve the performance will not be as important as expected.
Tomorrow I will perform a detailed benchmark with a N95/N100/11390H
Display MorePerfect if we can find a good way to work
Don't worries about hardware I have a 9950X3D + 5090 + 96Gb RAM, I’m currently doing the final merge of all macro feature. It’s taking longer than expected, so the code may only be ready tomorrow if GPT behaves tonight
The time-consuming part isn’t really compilation itself, it’s running the full end to end test suite and making sure there are no regressions across the different playback and conversion paths.
At a high level, the next release will be stable, but some features might not work as expected since I won't have time to complete functional testing beforehand. I'd rather make the code available to you earlier and I'll run the tests in parallel. It will effectively be a pre-release, and I'm going to fork LE.
What will be the changelog :
Technical :
- Merge with Kodi 22 rc1
- Rebuild of the repo with the Dolby Vision processing logic is now separated from the playback layer, making it easier to reuse, test, evolve independently and with a dedicated API.
Rendering option for Dolby Vision input
- DV Native - standard Dolby Vision playback while preserving the original intent and metadata.
- DV Enhanced - dynamically adjusts the existing Dolby Vision metadata to better exploit the display’s peak brightness. The goal is to extend highlights and overall dynamic range in a controlled way, while preserving black levels and shadow detail rather than simply stretching the image and crushing the lower end.
- HDR10 Basic / Expert - conversion from Dolby Vision to HDR10, with an Expert mode using additional display characteristics such as peak brightness and use all DV metadata to dynamically tone map the picture into an HDR10 output for non compatible DV display
- HDR10 Fallback - standard Kodi / vanilla HDR10 path.
Rendering option for HDR10 input
- DV Reconstructed (AI) - reconstructs Dolby Vision metadata from the HDR10 source using image analysis and AI (I trained a small LightGBM ML model to reproduce L1 & L3 metadata it should be better than the VS10 conversion from dolby, the model is very small and fit in any CPU)
- DV Enhanced - reconstructs a Dolby Vision representation and then applies the same controlled metadata enhancement, extending the usable dynamic range while preserving blacks and shadow detail.
- HDR10 Native - untouched/native HDR10 playback.
Quick switch rendering settings : playback panel that lets you switch between the different output modes while the video is playing, so you can compare the rendering directly on the same scene. (This feature is actually blocking the build, it's VERY complicated to be able to switch on the fly the rendering path without any instability)
Drivers:
- Intel : Extended support for older iGPU
- AMD : First version of AMD DV Driver
Once everything is merged and published, I’ll mainly focus on
1- Fixing and refining the conversion algorithms, especially DV Enhanced, which is by far the most complexe rendering path since I use all metadata and it's personally the feature I’m most interested in. And DV -> HDR10 Expert conversion is also very complex I will investigate deeply into it after the pre-release push.
2- Start an optimization audit for the 7430U
3- Start an optimization audit for N100 and N95 (I have both CPU) and try to finally fix the frame drop seen on DV 7 FEL. Since you will receive a N100 I will prioritze the support of AMD driver, and I will stop the implementation of the VRR-QMS with DV interface rendering.
I think your improvements to the processing pipeline will be very welcome and should also help us support a wider range of hardware, but non-regression test will be huge to include that properly, push your PR I will applied my testing framework and protocol.
I am very happy to share the new build R1.0.0 Beta1 
https://github.com/CroqueMr/libreelec-x86-DV/
Curious to hear your feedback and see how the DV and HDR10 rendering modes perform.
Maybe I should start a new dedicated thread to collect more feedback now that AMD is supported too (the AMD drivers are really in beta; I have a feeling there will be a lot of compatibility issues to fix).
Known issues : Still having that frame drop issue on the N100/N150 on few DV profil 7 FEL
cinemaONE Unfortunately, the repository is still under GPLv3. I will try to remove the GPLv3 components in an upcoming release.
dangerouslaser Feel free to push any PRs I will test and merge as fast as possible unfortunately I can not edit the repo to fork LE
I am very happy to share the new build R1.0.0 Beta1
Tried it but curiously all DV and HDR related stuff appeared as "/unavailable" on my N100... on the same hardware that had everything working in release R0.3.0. So I can't even play test it.
As a side note. I tried both dangerouslaser and R0.3.0 CroqueMr build on "Tron Ares" (a DV P7 highbitrate REMUX) and on both I get the same 1 frame drop per second. So it seems that lightweight file test or gigantic movie file size really don't matter.
Yes AMD card support VAAPI, DV playing works great on my 7430U (just a small issue on Profile 5 but it is easy to fix), this is why I prefer to not use a 2nd path for Intel, and try to capitalize on optimization that benefit both Intel and AMD.
I have some free time, so I’d like to integrate your changes as soon as possible while waiting for the fixes coming via the issues. If that works for you, I’ll go ahead and integrate your two major enhancements; it shouldn't take long, as I can see how to do it cleanly.
The issue on the frame dropping is almost fixed, the next release will address it.
Could you send me the kodi.log file? I ramped up the fallback mechanisms so that even devices without DV support could use the build and play DV content via HDR10, I might have been a bit too aggressive with that.
Yes - you can integrate my changes!
edit:
One thing I have been trying to figure out is how we can scale the FEL layer with nearest neighbor. Based on my reading, that seems to be how the mediatek chipsets in the high-end UHD players scale the layer. Unfortunately neither vaapi or qsv has an out of the box nearest neighbor scaling option. It is possible to do it with the CPU - but then we lose the performance gains from offloading this upscale to the GPU.
I am not entirely sure how much of a difference it actual makes but some people have complained about chroma and tearing issues when upscaling with bilinear etc.
Display MoreYes - you can integrate my changes!
edit:
One thing I have been trying to figure out is how we can scale the FEL layer with nearest neighbor. Based on my reading, that seems to be how the mediatek chipsets in the high-end UHD players scale the layer. Unfortunately neither vaapi or qsv has an out of the box nearest neighbor scaling option. It is possible to do it with the CPU - but then we lose the performance gains from offloading this upscale to the GPU.
I am not entirely sure how much of a difference it actual makes but some people have complained about chroma and tearing issues when upscaling with bilinear etc.
My minimum target CPU is the N95/N100, if with your optimization and the asynchronous frame preparation I see again some frame droping I will investigate on that, but I am pretty sure it will be sufficient for Native DV.
Today N100 is almost perfect for DV vanilla, but stutter and frame drop a lot when you activate any custom profile (DV Enhanced etc...) a huge optimization will be necessary. I think to be able to cover all profile
Edit : Unfortunately using VAAPI to upscale FEL layer has an small impact on the picture, I will try to see if it's visible, and the planar output is very complicated to integrate to my new engine, I will work on it tomorrow.
yeah any upscaling of FEL that isn't nearest neighbor won't exactly match what an oppo / panasonic outputs. libplacebo uses lanczos for the upscale which is expensive for the CPU and still doesn't match exactly.
Could you send me the kodi.log file? I ramped up the fallback mechanisms so that even devices without DV support could use the build and play DV content via HDR10, I might have been a bit too aggressive with that.
Ok, here it is.
Click to download files: https://file.kiwi/0276153b#lIuT9DXvgLIcryhRyFxgkw
