Dolby Vision w/FEL + 3D for PC (AMD/Intel/nVidia)

    Quote from CroqueMr

    I had this issue once and I never managed to reproduce it. Could you run all your file that not work properly and share the log file please :) for HDR10+ I am on it the pipeline does not work as expected and I do not have my HDR10+ screen to properly fix it.

    I activated verbose logging for components I thought might be relevant. I'm gonna send you a download link by PM, as the log is quite long (verbose logging).

    I tried the same movie on Hades build, it gets converted to Dolby Vision and it does not show the same problem (screen blanking intermittently, once every... whatever it wants, I don't think it's always in the same places). The log runs for a little bit, enough for at least three or four "blanks" to happen. Hopefully you'll notice something in the log.

    Quote from sat4all

    Hi,

    CroqueMr Unfortunately, your build isn't working on my Zotac ZBOX EN1060K. it gets stuck on the boot splash screen same as official LE image.

    hadesdevls Dolby Vision is falling back to HDR on my setup. Could you please check the attached logs?

    Thanks in advance!

    sat4all Thanks, the logs show exactly what happens. Dolby Vision does start, but at 3840x2160 23.976 Hz the driver of your GTX 1060 wants to send its own HDMI vendor InfoFrame for that mode (the HDMI VIC of a 4K 24 Hz mode), and that is the same InfoFrame the Dolby Vision signal travels in. So the driver turns down every Dolby Vision frame, 268 times in two seconds, and then Hades goes back to HDR10, as it's meant to. That one is on Hades to handle: the way is to give the mode in the AVI InfoFrame instead, as Hades already does for HDR10+ on those modes, so the vendor InfoFrame stays free for Dolby Vision. Your Denon shows the PC its own EDID, which is why the driver picks the HDMI VIC there.

    Two things you can try meanwhile, and both tell me more: turn "Adjust display refresh rate" off so the video plays at 4K60, which has no HDMI VIC, and Dolby Vision should go out; and, if you can, connect the PC straight to the TV once.

    hadesdevls I tested through USB key. One thing I could suggest: make the options clearer when one boots from it.
    I have a dedicated NUC (NUC11TNKI3) for this, so I prepared the key on a different, Windows 10, machine. Once I booted the NUC with usb key inserted, I was trying to understand what the different "Run/Run*/Installer/Live" options meant and it autostarted as Run almost immediately (a few seconds, really). Maybe it was on your github page, I don't know, but I found it alarming.

    The HDR10+ movie that was giving me trouble on CroqueMr build played fine, converted to Dolby Vision. And, generally speaking, everything seemed to work ok. I connect the NUC to a Denon X3800H AVR and that to an LG C1 (I mention this as I saw on your github that you keep track of hardware tested and you mentioned no AVR tested yet). Both Atmos and DTS-X played ok.

    I noticed the GPU was always or almost always sitting at 100% and headroom was most definitely not ample (and this on 24fps movies). Not something I'd be comfortable with if we were talking madVR profiles optimization. It looked like it could easily drop frames on "complicated" scenes.

    Considering my hardware should be a fair bit more powerful than the N100 which works fine for 24p content on CroqueMr, I wonder if I am missing something or if, simply, your builds are more targeted toward more powerful hardware (I come from a past where the last HTPC I used for media purposes had a RTX 4070, but I'd very much like to remain fanless).

    CroqueMr , I tested RC1.1 and I am happy to report the freeze when PGS subtitles are on the screen at the same time as any GUI in DV movies is gone! All seems fine now!

    My guess is that fixed it?:

    Fixed mixed PGS subtitles and SDR GUI composition in Master Reference.

    In any case, I want to thank CroqueMr and hadesdevls for their work on this it's really exciting! I didn't test HADES yet because no time but I will check it out too!

    Congrats to CroqueMr to making the most accurate DV of any player according to DMDreview ! This is great to see and makes it so my am6b+ will not be used anymore probably but I'll keep it as an option!

    Open source is so great, especially lately with AI's help it's so refreshing compared to big corpos who makes half-assed products just to make money. The passion in open source projects will always make more refine products in the end because the makers actually care about the end result product.

    Thanks for your feedback it helps to improve the overall build. Yes you found the right line in the changelog for your issue ;)

    Quote from ashlar

    hadesdevls I tested through USB key. One thing I could suggest: make the options clearer when one boots from it.
    I have a dedicated NUC (NUC11TNKI3) for this, so I prepared the key on a different, Windows 10, machine. Once I booted the NUC with usb key inserted, I was trying to understand what the different "Run/Run*/Installer/Live" options meant and it autostarted as Run almost immediately (a few seconds, really). Maybe it was on your github page, I don't know, but I found it alarming.

    The HDR10+ movie that was giving me trouble on CroqueMr build played fine, converted to Dolby Vision. And, generally speaking, everything seemed to work ok. I connect the NUC to a Denon X3800H AVR and that to an LG C1 (I mention this as I saw on your github that you keep track of hardware tested and you mentioned no AVR tested yet). Both Atmos and DTS-X played ok.

    I noticed the GPU was always or almost always sitting at 100% and headroom was most definitely not ample (and this on 24fps movies). Not something I'd be comfortable with if we were talking madVR profiles optimization. It looked like it could easily drop frames on "complicated" scenes.

    Considering my hardware should be a fair bit more powerful than the N100 which works fine for 24p content on CroqueMr, I wonder if I am missing something or if, simply, your builds are more targeted toward more powerful hardware (I come from a past where the last HTPC I used for media purposes had a RTX 4070, but I'd very much like to remain fanless).

    ashlar Thanks for testing it, and for the AVR detail: a Denon X3800H with an LG C1, Atmos and DTS:X working, goes on the tested list, and so does HDR10+ as Dolby Vision on your NUC.

    You're right about the boot menu, it should say more. What each entry does: Run, the default, starts Hades from the key with the internal disks hidden; "Run (internal disks read-only)" shows them, read-only; Live starts without keeping anything; and Installer only installs if you pick it, and asks which disk and for confirmation before it writes. Five seconds is short for a first look, so I'll give the menu a longer wait and plainer names.

    On the GPU: Hades draws every frame at full fidelity for as long as the graphics keep up, so the meter sits high, and what matters is whether frames arrive in time, not the percentage. In madVR terms, the number to watch is the render time against the 41.7 ms of a 24p frame: kodi.log gives the average GPU time per frame every 10 s, much like the render times in madVR, along with how many frames came late, and the automatic step-down works like a profile that switches itself to a lighter one only when frames stop fitting. All of that GPU time goes into the picture and the menus, and the log accounts for it frame by frame. HDR10+ converted to Dolby Vision is a 4K picture rebuilt and sent as Dolby Vision on every frame, which is heavy work for UHD Graphics with 48 units, and bringing that load down on graphics like yours is on my list. If you'd like a firm answer for your NUC, a diagnostic of that film would show the GPU time per frame and every frame that came late.

    Creator44 Thank you, that's kind, and you're right about open source: a lot of people here clearly care about the result. When you find the time, Hades runs from a USB drive, so it's easy to try next to what you already have, and I'd love to hear how it does on your setup. And if DMDreview runs another round, Hades would be glad to be part of it.

    Quote from dangerouslaser

    Kernel. You could do it on a VM with GPU pass through, but not native in Windows. Software / LLDV would work though.

    So tv-led would not work in a vm? These builds running in windows would make a secondary pc just for libreelec useless for windows users but I think there would still be fragrant issues like framerate switching etc which is shaky in Windows so... Libreelec brought a lot of stability for media playback for x86

    Quote from Creator44

    So tv-led would not work in a vm? These builds running in windows would make a secondary pc just for libreelec useless for windows users but I think there would still be fragrant issues like framerate switching etc which is shaky in Windows so... Libreelec brought a lot of stability for media playback for x86

    TV-led will work in a VM - but you need to pass the full GPU through to the VM. Virtual GPU or partial pass through will not work. The VM needs full control of the HDMI output.

    on a pc with a dGPU and (usually unused) iGPU it should be possible to pass the igpu to the VM for full DV/HDR10+, if the igpu is compatible. Then have two HDMI cables, or a switcher, to the TV/AVR so you could fire up the VM from desktop shortcut as if it were any other app, then even automate the TV/AVR switching over to that port to bring up the interface.

    I know from experience that passing the igpu to a VM sometimes takes some extra tinkering but it's generally worked for me on modern intel platforms with linux hosts. keep in mind of the amd (AM5 mostly I think) chips that have an igpu only have a very limited, barebones gpu intended for getting to bios or just getting a desktop on screen... they might struggle so keep that in mind, the proper G parts (they call those APUs) with a real ipgu would be fine though.

    That way you dont need to reboot, and you dont need two dgpus, and you can still easily switch back to the desktop and treat libreElec almost like it was just regular Kodi.

    CroqueMr, thanks, the faint media icons and subs issue is fixed. As is the occasional lip synch I had w/N150 using DV Master. Couldn't replicate, but it's a non-issue now. Your build feels very stable, ready for primetime, general usage by anyone new or those coming over from Amlogic. A lot of amazing work in what feels like lightning speed; congrats!

    CroqueMr , I assume you already saw this, but here's a picture of the player process infos and there are words that are cutted with the "..." following it because of not enough space to show it all.

    Do you think you can fix this by shortening the names or changing the column length?

    Also, I tested the DV DT file again and this time I can see the text "yous hould not see this text except on TV apps" but there's also a kodi gui interface on top with the name of the file and the 5 star to rate i think? It is better than before because before I could not see the image correctly at all. Am I suppose to see "This device can decode FEL" like with the other two test files that works?

    Quote from hadesdevls

    sat4all Thanks, the logs show exactly what happens. Dolby Vision does start, but at 3840x2160 23.976 Hz the driver of your GTX 1060 wants to send its own HDMI vendor InfoFrame for that mode (the HDMI VIC of a 4K 24 Hz mode), and that is the same InfoFrame the Dolby Vision signal travels in. So the driver turns down every Dolby Vision frame, 268 times in two seconds, and then Hades goes back to HDR10, as it's meant to. That one is on Hades to handle: the way is to give the mode in the AVI InfoFrame instead, as Hades already does for HDR10+ on those modes, so the vendor InfoFrame stays free for Dolby Vision. Your Denon shows the PC its own EDID, which is why the driver picks the HDMI VIC there.

    Two things you can try meanwhile, and both tell me more: turn "Adjust display refresh rate" off so the video plays at 4K60, which has no HDMI VIC, and Dolby Vision should go out; and, if you can, connect the PC straight to the TV once.

    Indeed, disabling "Adjust display refresh rate" allows DV output to work. However, connecting the PC directly to the display doesn't change anything—DV output still fails when "Adjust display refresh rate" is ON.

    Thank You!