Posts by CroqueMr

Quote from w46n3r

I tested on a N100 DDR5 mini PC and on 23.976Hz have yet to find any playback performance problems. The Dolby Vision logo is enabled every time (Marantz AV Receiver + LG C2) and in all videos I tested I did not experience frame drops or skips.

I noticed that on FEL test files the player, even at 23.976Hz, in some cases drops quite a bit of frames (almost a frame per second on one called "FEL TEST ST DL P7 CMV4.0 4000nits V4.mp4") but I'm not too worried about it given its just a test.

I'll continue to test it as I use it but the initial feeling is that is already completely usable even on the lowly N100.

Thanks for the feedback, good news for the N100, I was expected a good support from this CPU.

Profile 7 FEL require more GPU than other profile, I will deeply investigate on the CM4 / Profile 7 FEL, for me the N100 can read it without any drop at 24-30fps. maybe I need to optimize a little bit more.

EDIT : I found your file, peak GPU rendering usage is 52% on my 11390H, I do not have any dropped frame
I'm still going to try to reduce the GPU load.

I’ve seen that you’re really good at testing Dolby compatibility (probably better than I am) so your feedback will be very precious

I’m going to start looking into AMD drivers to extend compatibility. I do have an AMD platform (running a 7430U), but it’s currently under heavy use for my professional usage, and it will be complicated to test deeply on it.

I can confirm right now that, unfortunately, I won't be looking at any other platform: no ARM platform, nor dedicated GPU, I do not have the hardware to develop on it, and for ARM platform when I see the GPU render engine usage, I'm afraid optimizing my implementation might be beyond my capabilities.

I have just published a first version

Feel free to test it out and report any bugs or issues.

Tested on an 11390H. It "should" run smoothly on an N100/N150 thanks to some performance optimizations, but that still needs confirmation. If you want to stress test it on any CPU, try setting a Profile 7 FEL or a Profile 10 and add subtitles

Pretty sure 50 fps won't be smooth on an N100/N150, though.

GitHub - CroqueMr/intel-dv-libreelec: Experimental native Dolby Vision playback in Kodi on compatible Intel HDMI systems. LibreELEC community build with source patches and installable images.

Experimental native Dolby Vision playback in Kodi on compatible Intel HDMI systems. LibreELEC community build with source patches and installable images. -…

github.com

Done.

First real Dolby Vision playback on LE in Kodi with an x86 Intel CPU (i7-11390H).

From the libreELEC community on Reddit: WIP - Native Dolby Vision support on x86 Intel CPU in LE & Kodi

Explore this post and more from the libreELEC community

www.reddit.com

There are still quite a few glitches to fix (starting with Kodi completely choking on the UI/UX while a Dolby Vision movie is playing), but the full playback chain is now working.

The TV is properly switching into Dolby Vision, there are no frame drops, and playback itself is already very clean.

I’ll now start tuning, fixing, optimizing, and thoroughly testing every Dolby Vision profile.

I haven’t tested Profile 7 FEL yet. In theory, the implementation already supports it, so if I hit any issues, I expect them to come mainly from the additional GPU load. That said, I’m fairly confident the 11390H should be able to handle it without major problems.

Even though, from my vision, everything is 100% legal, using only open source and no proprietary code, I’m not quite sure how to share the build once I’ve finished a more robust implementation.

I’ve started working on a LE build with DV support, initially targeting the 11390H.

The good news is that the driver/kernel changes are largely shared with my mod with the 226V in Kubuntu and mpv. They could potentially cover a wider range of intel CPU, including the N100/150 although compatibility still needs to be verified on each platform, performance is an open question on small iGPU

The Kodi integration requires substantial changes beyond the driver work. I’ll be digging deeper into that with GPT-6 Astra this weekend

I’ve just finished cleaning up the build, and it’s now available privately on GitHub. If anyone is interested in seeing how it works, I’d be more than happy to share access.

I’m also very, very interested in your take, chewitt, on the legal side of this before I start trying to adapt the implementation for LE.

The high- evel overview of the impacted components and patches is as follows:

Hi,

I’m the guy from Reddit who recently got proper Dolby Vision playback working on Linux with an Intel Ultra 5 226V.

On the 226V in Linux, the implementation is already very close to perfect from what I can see. Across all the modern DV profiles I’ve tested, I’m not seeing playback issues, any frame drops or obvious metadata problems. The main exceptions are the older legacy profiles and profile 20, which I haven’t focused on.

The current implementation still has noticeable rendering and memory bandwidth overhead, so performance on smaller or older iGPUs is an open question. I only perfomed tests with a 226V, which uses specific drivers.

Right now I’m cleaning up the build, removing debug/experimental code and preparing something shareable for a public. I’m aiming to push a first version by the end of the week.

For LibreELEC, I also want to try a native implementation on lower end Intel iGPU. I have an i7 11390H available, so that will probably be my first test platform. I will work on it in October

I should be able to reuse around 50-60% of the current work. The main difference is that my current DV path relies on a custom mpv build. For a clean LE integration, I’d rather port the Dolby Vision handling directly into Kodi’s VideoPlayer/DRM output path instead of keeping mpv as an external player.

For legal aspect, I don’t see any obvious issue, the work is mainly modifications to open source components (Linux/Intel DRM, mpv, FFmpeg and libplacebo) for interoperability. There is no Dolby proprietary code involved, no DRM/HDCP bypass, and obviously no claim of Dolby certification.

That said, if any of you see potential licensing, patent or other legal concerns that I may have missed, I’d be VERY interested in your feedback.