The main difference is where the color conversion happens, either predominantly on the TV side or on the PC side
And if it happens on the PC side inevitably it leads to a performance hit (more stuff to do, after all). Correct?
But the output on the TV (the actual pixels lighting up, I mean) is supposed to be identical?
And if it happens on the PC side inevitably it leads to a performance hit (more stuff to do, after all). Correct?
But the output on the TV (the actual pixels lighting up, I mean) is supposed to be identical?
Yes, performing the conversion on the PC adds GPU work and has a performance cost in our implementation.
Both paths are intended to produce the same final picture, but I wouldn’t claim "bit identical" output at the panel. The TV’s internal processing isn’t fully documented, and differences in calculation precision, rounding and quantization can introduce slightly different results.
I’d expect those differences to be almost invisible, Hardware acceleration itself doesn’t necessarily reduce accuracy, what matters is the arithmetic and precision used by each implementation. In the Master reference circuit, I used the most accurate calculation possible accelerated by GPU.
Hello DMD
I released a debug version with a "Dolby vision Master Reference IPT" pipeline, It’s the same as the Master reference (Non IPT) in the non-beta version, though in a different format to help you to compare this output with other player. If you need any modification nor format is not what you excpected please let me know.
I’d be interested in your feedback on this circuit, it will be rolled out more broadly in the next release. It isn’t fully optimized yet, an N100 processor can just manage 30 fps with FEL enabledwith 2,8ms headroom, but it can’t sustain 60 fps. I made sure that not a single bit changes between each modification. As I mentioned, it’s a very "overkill" circuit, featuring full-resolution calculations and the cleanest possible filters, the changes vs standard dolby vision output in the build are almost invisible, the implementation is similar the difference are in the rounding and precision.
Thank you, I’ll continue testing. I think that although the standards allow both color representation options, for some reason all players output ITP in an RGB 8‑bit tunnel. This may be due to the need or desire to send the same ITP Full range signal to the TV so that the TV perceives it identically. Since both DV P7 with Ycbcr and DV P5 with ITP are presented in the same ITP Full range in the tunnel.
For those who want a bit more insight into the difference between Master Reference and Standard in my build you have my detailed analysis and the impact on the picture here : https://github.com/CroqueMr/libre…d-2026-10-21.md as I said, impact is invisible, screenshot are taken when the difference is at its maximum in a 10min sample. Yes the screenshot are in SDR (but the movie was in DV), you need to be in DV to see the real impact, but do not trust me, you have the timestamp you can pause on the frame and switch the mode during the pause with the small submenu accessible through "O" 
Overall, "Dolby Vision Standard" I think runs on pretty much any x86 CPU with an iGPU supported in the build (so an AMD or Intel CPU released within the last 7-8 years or so). "Dolby Vision Master Reference" can even handle lowend ones like MatteN’s J5040
60fps movies can be a little bit complicated to play properly, but in my opinion it's not a big concern, a N100 handle it but the headroom is not that big.
As soon as I get more feedback, I'll add a "recommended hardware" section.
And I received my 3200U, I will focus the stable build on this setup.
Yeah I think I can give it a try, alors I think you was interested in DV to HDR10 expert conversion I saw some issue, black are crushed I will investigate to see the cause behind.
Yep definitely still crushed but performance is completely fixed. Looking forward to the update thank you.
Currently using basic and it's very surprising seeing the improvement vs HDR (DV disabled)
I tested a side circuit doing direct Profile 5 vs converted to YCbCr, and the differences were imperceptible. But it's definitely planned to skip this conversion for Profile 5 in the stable release, which can be avoided even though in reality it involves almost no loss in quality.
Look forward to it.
If anyone is interested https://discourse.coreelec.org/t/learning-abo…opment/50998/65 has a bunch of links that show ICtCp is better for the chroma sub-sampled video, so not converting the profile 5 converting to YCbCr is objectively better even disregarding computation aspects.
Look forward to it.
If anyone is interested https://discourse.coreelec.org/t/learning-abo…opment/50998/65 has a bunch of links that show ICtCp is better for the chroma sub-sampled video, so not converting the profile 5 converting to YCbCr is objectively better even disregarding computation aspects.
Thanks for the info.
Of course avoiding a lossy conversion will be everytime better. I am finalizing the profile 5 path without ycbcr, it will replace the old circuit for profile 5 in the next update.
Hi, CroqueMr hadesdevls
Huge thanks for making this happen, DV on PC was basically a myth before!
Do you think adding support for older NVIDIA Pascal cards might be possible in a future update?
Hi, CroqueMr hadesdevls
Huge thanks for making this happen, DV on PC was basically a myth before!Do you think adding support for older NVIDIA Pascal cards might be possible in a future update?
Yes, it's planned for this WE on my side
That’s amazing, thank you! Looking forward to the release
Hi CroqueMr , I tested Beta5 and the DV DT file does not play correctly still, it seems to just display nothing or some vague wavy stuff, I think I was seeing my purple kodi theme in the back or something, like see-though? Not a big deal as nothing is in DT in MKV.
I found a bad bug for me, if I put PGS subtitles ON, if any GUI is on, may it be the standard kodi gui, or my plexmod gui, etc. everytime there is a subtitle on screen, the video freezes and then plays correct when the subtitle disappears.
It seems to be fine with SRT subtitles though and there is no freeze on those, only on PGS.
Can you reproduce that and find a fix please?
Thanks to you and hadesdevls for your work!
Hi CroqueMr , I tested Beta5 and the DV DT file does not play correctly still, it seems to just display nothing or some vague wavy stuff, I think I was seeing my purple kodi theme in the back or something, like see-though? Not a big deal as nothing is in DT in MKV.
I found a bad bug for me, if I put PGS subtitles ON, if any GUI is on, may it be the standard kodi gui, or my plexmod gui, etc. everytime there is a subtitle on screen, the video freezes and then plays correct when the subtitle disappears.
It seems to be fine with SRT subtitles though and there is no freeze on those, only on PGS.
Can you reproduce that and find a fix please?
Thanks to you and hadesdevls for your work!
Thank you for the feedback.
DT is a known issue and a PR is already merged to fix this issue, the first fix was insufficient.
For the subtitle I will invesrigate some fixes are also ongoing, but I don't think it will cover your point.
what about for rtx 3050?
what about for rtx 3050?
Already covered
Hi, first of all, thank you very much, I'm testing on a MINISFORUM Mini PC UM760 Slim (AMD Ryzen 5 7640HS) and it's been working great !
One question, I see that we already have HDR to DV tonemapping, is it possible in a future release to add SDR to DV too ? Like the avdvplus build does on Amlogic using VS10 ? That would be awesome.
https://paste.libreelec.tv/bonnetlike-tempie.log
This is my log file. Display still outputs to laptop screen and not tv. Using beta 5 debug build on rtx 40 series gaming laptop. I was away and couldn't send it sooner. Hope this helps. Thank you.
Hi, first of all, thank you very much, I'm testing on a MINISFORUM Mini PC UM760 Slim (AMD Ryzen 5 7640HS) and it's been working great !
One question, I see that we already have HDR to DV tonemapping, is it possible in a future release to add SDR to DV too ? Like the avdvplus build does on Amlogic using VS10 ? That would be awesome.
I’ve already looked into it on my end, and it’s not really in my plans since I don’t see the benefit, though I could be wrong.
VS10 essentially just wraps SDR content into a DV container, no important metadata is generated to actually leverage the panel. It’s pretty much equivalent to playing SDR natively and setting your TV to Filmmaker mode.
At most, what could be interesting would be trying to genuinely generate HDR or Dolby Vision metadata a bit like what I did for the HDR-to-DV mode. The AI relies on scene-by-scene analysis to generate L1 and L3 metadata. We stay very conservative: we don't force a creative direction that the director didn't intend, nor do we recreate creative trims. We simply leverage Dolby processing capabilities through L1 and L3 metadata.
For SDR, this approach isn’t viable, or we won't have any major gain. The other direction would be attempting to convert SDR to HDR, but that’s a whole different beast: it requires heavy lifting to get right, and you end up completely overriding the original director intent.
I prefer to focus for now on features that benefit more people.
https://paste.libreelec.tv/bonnetlike-tempie.log
This is my log file. Display still outputs to laptop screen and not tv. Using beta 5 debug build on rtx 40 series gaming laptop. I was away and couldn't send it sooner. Hope this helps. Thank you.
Thanks.
I had two laptop yesterday with Nvidia GPU for my tests and I did not see any issue I will check your log
ok, i get rtx 3050 used, and DV & HDR work fine!
i have issue with HLG when try Channel via PVR addon
when playing TV channels: the screen turns green, and sometimes the system restarts when a channel is launched. The problem goes away when I disable "Use HEVC VAAPI"
but I need to keep it enabled for other types of video content; furthermore, without it, Dolby Vision cannot be played.
