CroqueMr and cinemaONE, can't thank you guys enough. Having full DV and full 3D working well on my AMD 5800H is amazing. Just tested a bunch of test clips and movies for both. Thanks to dangerouslaser as well. This is getting there in beating the best Amlogic solutions to date in terms of speed, power, and fluidity.
[x86-64][CroqueMr Builds] Dolby Vision w/FEL, HDR10+, and 3D
-
ht2tweak -
March 14, 2026 at 2:33 PM -
Thread is Resolved
-
CroqueMr and cinemaONE, can't thank you guys enough. Having full DV and full 3D working well on my AMD 5800H is amazing. Just tested a bunch of test clips and movies for both. Thanks to dangerouslaser as well. This is getting there in beating the best Amlogic solutions to date in terms of speed, power, and fluidity.
I second that! Being able to use my powerful mini pc and decode absolutely everything with one box is awesome and it's thanks to you guys!
-
I went from 25 minutes, scanning my Jellyfin library on my Homatics box (CoreELEC), to 4 minutes on the N100.
-
What's the chance some of this work begins to get merged to master?
At the moment the chances are low because development is in the full-throttle rush of bring-up with everyone getting high on new frontier models doing previously unthinkable magic
I would encourage focus on the "insert disc, press play" capability that allows DV media to work on a broad selection of devices and distros with a simple user experience. Avoid the temptation to add lots of config options and display readout. Kodi maintainers are allergic to config options because most are workarounds for kernel drivers that do the wrong thing; and the correct albeit slower resolution for that is always fixing the kernel driver. Similarly, if metadata is useful for development, log it in a debug log instead of cluttering up the OSD.
LE (master) will be happy to start doing official experiments once we see engagement on upstreaming. I suspect that will take time, but we are not in a rush (least of all Kodi) and we prefer to see things done in a long-term sustainable way.
NB: I'm thinking to take an N150 box with me to the VideoLan developer conference in Rome next weekend as there's normally a show-n-tell session, although there's no guarantee the TV's or projectors in the venue will support DV.
-
Display More
Thanks for the improvements in Beta3! I've tested the same Profile 7 FEL content with fast rendering disabled and enabled.
There does seem to be a noticeable improvement with fast rendering enabled:
- Fast rendering OFF: 119 skipped frames over approximately 60 seconds.
- Fast rendering ON: 67 skipped frames over approximately 130 seconds.
- Both sessions reported 0 dropped frames and 0 presentation failures.
The tests weren't identical in duration or playback position, but with fast rendering enabled, the skipped-frame counter increased much more slowly after the initial playback period, with several intervals showing almost no additional skips.
I'm still seeing repeated OutputPicture - timeout waiting for buffer messages in both sessions.
I also noticed the following message:
CB1 FEL upscaling: VAAPI unavailable, using full shader FEL reconstruction
It looks like the Vega 8 isn't benefiting from the new VA-API FEL upscaling optimization.
Thank you, I will check if we can have a better approch for this kind of CPU can you send me the kodi.log file please.
Display MoreCroqueMr , I have better information about my no gui in DV bug. It seems the GUI does not display in the top and bottom black bars only. I attach a screenshot to show you, you can even see part of the last line of the player debug info on the top of the movie image and the player info is cutted on the bottom in the black bars too.
It does the same thing on an FEL and NO FEL movie.
I tried Gemini man with 1.85 very minor black bars and another full screen 1.78 DV file and I can see all the GUI correctly when playing back these videos.
My minipc specs again:
Beelink SER8 AMD Ryzen 7 8845HS with AMD Radeon 780M 12-Core 2700 MHz.
I see exactly why it does that the cause is an optimization I made in the R0.3 build, I will fix that. -
Sorry if it's a stupid question but any chance someone has tested DV and or 3d with a 3500U? Very cost effective at the moment.
-
I think that if Dolby Vision ever makes it into LibreELEC officially, it will probably be through an approach closer to my initial implementation, before R1.0.0 Beta1, with minimal changes to FFmpeg and other upstream dependencies. I believe such an implementation is possible, but it will take time. It might also be useful to maintain a much simpler build with just the bare minimum needed for DV support. Performance won't be as good, but it will help with the implementation.
All absolutely understandable. For the time being I suppose the question becomes: how likely are you in the future to maintain your builds up to date with changes/new features from upstream? I think everybody understands there's no guarantee and, of course, no obligation. But before committing to a switch from existing working solutions, a reassuring answer on this would go a long way.
I want to stress, though, that, at least for me, a "not likely as I've got better things to do" would be 100% ok. You've already done a lot.
-
Beta 3 is very smooth on N100, its way better than Beta 2 was on N150.
-
I think that if Dolby Vision ever makes it into LibreELEC officially, it will probably be through an approach closer to my initial implementation, before R1.0.0 Beta1, with minimal changes to FFmpeg and other upstream dependencies. I believe such an implementation is possible, but it will take time. It might also be useful to maintain a much simpler build with just the bare minimum needed for DV support. Performance won't be as good, but it will help with the implementation.
We could definitely work on a branch for this. It would not work on an N100 (at least not FEL or 4k60), but it would be more maintainable and higher probability of being accepted upstream.
-
Hi CroqueMr,
First of all, thank you so much for all the hard work you've put into this project. I've been testing Beta3 on my Mini PC (Intel Core i7-1360P / Iris Xe), connected to my LG OLED G5 (TV-Led Dolby Vision), and I have to say this is by far the best version I've tested so far. The improvements are really impressive!, and I have to say this is by far the best version I've tested so far. The improvements are really impressive.
I wanted to share a few things I've noticed:
1. Huge improvement in 4K 60fps playback
This is probably the biggest improvement for me. In previous builds, movies like Gemini Man had really bad frame drops, sometimes exceeding 100 dropped frames.
With Beta3, I'm now seeing fewer than 10 dropped frames, usually around 7. There are still a few drops, but compared to the previous versions, this is a massive improvement. Really great work here!
2. HDR10 to Dolby Vision conversion and player information
HDR10 to DV conversion still has a couple of issues.
When I stop a movie that's being converted from HDR10 to Dolby Vision, the screen sometimes goes completely black for a few seconds before the picture comes back.
I've also noticed something strange when pressing "O" to display the player information. The information under Output & Processing doesn't stay consistent. Some fields appear, disappear, or change unexpectedly while the movie is playing.
I've attached screenshots with red boxes showing exactly what I mean.
3. Kodi crash when stopping playback
Unfortunately, I experienced a crash while watching Boy Kills World. As soon as I pressed Stop to return to the Kodi interface, Kodi crashed and restarted automatically.
I've attached a privacy-cleaned technical crash log. The log shows a failure during the transition back to the GUI, including GBM initialization and EGL errors, followed by SIGABRT.
Hopefully, it helps you track down the issue.
4. Audio information still shows PCM
When pressing "O" during playback, the audio information still shows Decoded player PCM, even when the source audio is Dolby TrueHD or Dolby Digital Plus.
I'm not sure whether this is just how the decoded audio path is reported, but it would be great if the player information could clearly show the original audio codec and whether passthrough is being used.
5. Request for Beta4 – Correct Dolby Vision and HDR10 codec logos
There's one more thing I'd really love to see in Beta4.
When playing a Dolby Vision or HDR10 movie, the Arctic Fuse 3 (AF3) skin still displays the SDR logo instead of the correct video format.
I actually contacted the AF3 skin developer about this. He explained that the skin reads the codec information directly from Player.Process/video.dovi, but Kodi isn't correctly identifying the video codec in this LibreELEC DV build, so the skin falls back to its default logo.
According to him, this would need to be addressed in the LibreELEC DV build itself rather than in the skin.
Would you mind taking a look at this for Beta4? It would be great if Kodi could correctly report Dolby Vision and HDR10 so the skin could display the appropriate logos automatically.
I've attached a screenshot showing what I mean.
I know it's a small visual detail compared to all the technical work you're doing, but I think it would be a really nice addition.
Overall, I'm genuinely impressed with Beta3. The improvement in 60fps playback alone makes a huge difference, and it's amazing to see how far this project has come.
Thanks again for your time, effort, and dedication. Really appreciate everything you're doing, and I'm looking forward to seeing what comes next! 🙂
-
Thanks I will investigate on that, if you want to remove all framedrop in 60fps you need to activate the quick dolby vision rendering, it impact a little bit color detail it is almost invisble but since it affects a little bit the picture this settings is optional and disable by default, in beta4 I will add an option to activate this settings only when you play a 50fps+ DV track.
For your other points I will try to cover all of them for beta4.
-
Thank you, I will check if we can have a better approch for this kind of CPU can you send me the kodi.log file please.
I see exactly why it does that the cause is an optimization I made in the R0.3 build, I will fix that.It's attached to my original post. Are you not seeing that?
-
Thanks I will investigate on that, if you want to remove all framedrop in 60fps you need to activate the quick dolby vision rendering, it impact a little bit color detail it is almost invisble but since it affects a little bit the picture this settings is optional and disable by default, in beta4 I will add an option to activate this settings only when you play a 50fps+ DV track.
For your other points I will try to cover all of them for beta4.
I actually have fast rendering enabled already, as you can see in the screenshot. I'm still getting around 7 dropped frames with Gemini Man at 4K 60fps, but it's definitely much better than before. Thanks again for all your work.
-
Sorry if it's a stupid question but any chance someone has tested DV and or 3d with a 3500U? Very cost effective at the moment.
You can see my other posts where I have. Better performance with beta 3 but still getting frame drops, especially without fast processing enabled.
-
To recap recommended settings, do these look right for lower-end Intel (N97/N100/N150) and AMD (5800H, 3500U or similar). If so, I'll add them to post #1.
Setting Recommended Hardware acceleration — VAAPI ON DRM PRIME decoder OFF DRM PRIME hardware acceleration OFF PRIME Render Method Not used Render path EGL / VAAPI Direct-to-Plane / D2P OFF Asynchronous Frame Preparation ON Dolby Vision Fast Rendering ON (Try OFF for lower-end Intel, but if any skipped or dropped frames, revert to ON)
OFF (for lower-end AMD)Most of these settings don't impact DV playback. Only Asynchronous frame preparation and DV fast rendering actively affect it, the rest only apply to the standard Kodi pipeline. I’m going to avoid including a lot of complex settings as much as possible, after all, a developer's goal is to hide the technical details. I’ll keep the "quick rendering" option, and possibly include other optimizations that might theoretically affect image quality behind this settings. I think asynchronous image preparation will be removed from the stable version and either forced to "Enabled" or made available in the Expert settings.
I actually have fast rendering enabled already, as you can see in the screenshot. I'm still getting around 7 dropped frames with Gemini Man at 4K 60fps, but it's definitely much better than before. Thanks again for all your work.
Very strange on my N100 I do not have any framedrop with a BR Iso of Gemini man, and the N100 is far weaker than your CPU. I will check with your log.
Beta4 won't focus on performance improvements. The priority will be fixing DV Enhanced and the DV ↔ HDR conversion pipelines and other small stuff (3D, FEL not working on some AMD GPU...)I have a busy week ahead, and I'd rather take the time to properly refine and test the conversion and enhancement algorithms than rush the release. My priority is to deliver something reliable and stable.
I'm aiming for a release on Sunday or next week.
-
Most of these settings don't impact DV playback. Only Asynchronous frame preparation and DV fast rendering actively affect it, the rest only apply to the standard Kodi pipeline. I’m going to avoid including a lot of complex settings as much as possible, after all, a developer's goal is to hide the technical details. I’ll keep the "quick rendering" option, and possibly include other optimizations that might theoretically affect image quality behind this settings. I think asynchronous image preparation will be removed from the stable version and either forced to "Enabled" or made available in the Expert settings.
Understand, but for those less familiar w/LE, or migrating from CE now because of DV and/or 3D, it's like what should these settings be, not just for DV, but general playback.
chewitt did mention that Kodi support for DRMPRIME is designed for ARM SoC hardware using direct-2-plane rendering. That if we're using Intel/AMD, to only use EGL/VAAPI.
I'll add the recommendations to post #1.
-
G'day!
Thanks for all the work on this.
A question about discrete Intel cards, specifically Arc Battlemage.
I've picked up an Arc B570 and have a Ryzen 5600 / B550 box to run it in. From having Claude read the patch series the Intel DV patches seem to touch only drivers/gpu/drm/i915/display/* plus the generic hdmi core, with nothing in gt/ or gem/. As far as I understand, the xe driver builds that same display code, and Battlemage is xe-only.
Claude noticed no CONFIG_DRM_XE, so xe isn't built at all and the native_hdmi check should be fine on Battlemage, since its HDMI looks native and not through a converter (connectors show up as HDMI-A-n under xe).
Is xe/Battlemage supported, planned or a non-starter and if I use Claude to enable xe in a custom build and the patches apply, is there anything in the userspace/engine side that assumes an iGPU?
Cheers!
