I decided to make the circuit selected in the settings menu the default on startup, as I find it more user-friendly.
Absolutely, while I respect and share ht2tweak's desire to tinker endlessly with conversions, results, etc., a normal usage pattern for sure sees a user testing the different modes available, deciding what's right for them, putting that in settings and forgetting about it.
Maybe a "toast" message should inform users about the cause of the fallback. So they know about the need for different settings, and that it's not a bug.
Maybe a "toast" message should inform users about the cause of the fallback. So they know about the need for different settings, and that it's not a bug.
I have a fallback message for many use case, I think this one is not covered, I will add it
Absolutely, while I respect and share ht2tweak's desire to tinker endlessly with conversions, results, etc., a normal usage pattern for sure sees a user testing the different modes available, deciding what's right for them, putting that in settings and forgetting about it.
Please do not change this.
Agree. I was only testing as the functionality is there. I've tried VS10 and all kinds of processing solutions for years and settled on pure/direct, and just watch the content in the native format.
Hi, many thanks for the good read and your efforts the last few weeks, really awesome what you have built in such a short time frame. Both your builds do not seem to work with my newly aquired AMD RX550 LP. Dolby Vision does fallback to HDR on CroqueMRs Build, and on HADES build the tv shows the Dolby Vision logo and i can hear Audio, Attached is a log from CroqueMR build, i tested two scenarios: plugged directly into the TVs HDMI4 Port and also with my Denon AVC-x3800H in between. Hope i can contribute to this project by testing and shareing my logs. Please let me know if i did something wrong or if you want me to test anything. 01_KODI.log
I’ve noticed one little bug: when I play a video from my S24 (HDR10+)—processed as Dolby Vision—and then stop the clip, the screen remains black. The PC hasn’t crashed, though; I can tell because I can hear the audio feedback as I navigate through the menu. Is this a known issue, or should I provide a log?
DolbyVisionFriend Yes, please capture this with diagnostics on. The menu sounds show that Kodi is still responding, but I need the state after stopping to see whether the Dolby Vision signal was removed and the normal output restored.
Rename DIAG-OFF.TXT to DIAG-ON.TXT on the boot partition, play the S24 clip as Dolby Vision, then stop it and leave the black screen for at least 30 seconds before restarting. Attach the hades-diag folder from that run. It records the output state 5 and 30 seconds after Dolby Vision ends, which is the part I need here.
If possible, please include a short original S24 clip that reproduces it, without re-encoding. Please also say whether the TV still reports Dolby Vision while the menu is black. I cannot yet say whether this shares anything with the overlay stutter. Good to hear chapter skips work on FEL MKV here.
Quote from ApexAftermath
Diagnostics attached.
ApexAftermath One remaining test for the HDR depth option: the attached RC8 run is native Dolby Vision on the GT 1030, so it does not establish the HDR10 rendering depth on either card.
When you next test HDR10, enable System > Display > "HDR at more than 8 bits where the card sends RGB at 8 (NVIDIA)" at Expert level and capture a diagnostic for each card separately. Please identify which is the GTX 1060 and which is the GT 1030.
I need both the rendering-buffer depth and the HDMI output depth. RC8 can report a 10-bit link while still drawing at 8 bits if the display plane rejects the vertical reflection required by its own HDR buffers, as the GTX 1060 report in issue #17 showed.
Quote from SunnySnacksALot
Hi, many thanks for the good read and your efforts the last few weeks, really awesome what you have built in such a short time frame. Both your builds do not seem to work with my newly aquired AMD RX550 LP. Dolby Vision does fallback to HDR on CroqueMRs Build, and on HADES build the tv shows the Dolby Vision logo and i can hear Audio, Attached is a log from CroqueMR build, i tested two scenarios: plugged directly into the TVs HDMI4 Port and also with my Denon AVC-x3800H in between. Hope i can contribute to this project by testing and shareing my logs. Please let me know if i did something wrong or if you want me to test anything.
The attachment here is from CroqueMr RC3, not from Hades. I read it as a comparison. On this card his kernel reports the AMD family as unsupported for native Dolby Vision (family_supported=0), so native output is not started (native_dv=false, native_eligible=false). Playback then sets HDR at 3840x2160. That matches the fallback you described. Both sessions in the file see the G3 (LG TV SSCR2) on HDMI; I do not see a Denon EDID in this log.
Hades takes the other path on the same card: it does start native Dolby Vision, which is why the TV shows the Dolby Vision logo and why you still hear audio. The picture staying black is the fault I am investigating. The Godzilla capture in that diagnostic is MEL, so the black screen is not limited to FEL reconstruction.
The comparison I still need is the same Godzilla file, over the same direct HDMI connection, with "Dolby Vision as HDR10" selected, plus whether opening the playback controls during native Dolby Vision leaves those black as well. Please keep diagnostics on and attach the folder on the GitHub issue.
My BL/EL code is very sketchy, it has accumulated a lot of patches I really don't like this part of my code, I plan to redo it later
Hi CroqueMr,
Haha, thanks for the honest reply! It totally makes sense now. Sometimes a bunch of accumulated patches happens to fix a specific case (like Transformers 2) without being a clean architectural solution.
This perfectly explains why you decided to rework the entire FEL/EL pipeline for RC4. I completely understand that Hades needs a different approach rather than copying your patchwork.
Take your time with the RC4 rebuild. I'll be here ready to test the new architecture as soon as it's ready!
Is anyone having issues using HDR10 to Dolby Vision? I've tried 2 films and both closed after several minutes of playback, this is both with DVD Rendering and Adaptive HDR Mapping. After the movie closes automatically I see the console which I believe is restarting the video driver.
The films I tried are Ghost In The Shell and The 365
I'm not sure how to collect logs, but if anyone can point me to a tutorial I'll attach them.
My PC is 9800x3d RTX 4090 64GB DDR5-6000 RAM. Libreelec is installed in a NVME connected via USB 10gbps. My movies are in sata HDD connected directly to the motherboard.
Finally I cannot start how much I'm enjoying this release, DV looks amazing on my TV, way better than using MadVR in Windows 11 and HDR10.
hadesdevls Thank you for reading the CroqueMR log too, stumbled upon that while reading the logs myself - very curious what he thinks about the attached log, but i also want him to take breaks to not overwork himself - both you guys please take breaks if you feel like you need to (and even if you do not feel like you need to but your loved ones tell you to).
I did the tests you wanted me to (and some mistakes along the way) and sent you the logs on github. For now i will keep the Denon AVC-x3800H out of the equation - as i feel it would overcomplicate things unneccessarily. If you guys are able to make it work on a direct connection, then i will happily test it with my Denon in between.
Very excited about both your approaches, i like my homatics Box with coreELEC, but even just scrolling the menu you can tell its performance is not up to my (way too high) standard.
hadesdevls Thank you for reading the CroqueMR log too, stumbled upon that while reading the logs myself - very curious what he thinks about the attached log, but i also want him to take breaks to not overwork himself - both you guys please take breaks if you feel like you need to (and even if you do not feel like you need to but your loved ones tell you to). I did the tests you wanted me to (and some mistakes along the way) and sent you the logs on github. For now i will keep the Denon AVC-x3800H out of the equation - as i feel it would overcomplicate things unneccessarily. If you guys are able to make it work on a direct connection, then i will happily test it with my Denon in between. Very excited about both your approaches, i like my homatics Box with coreELEC, but even just scrolling the menu you can tell its performance is not up to my (way too high) standard.
SunnySnacksALot Thank you for the extra tests and for sending the logs to the GitHub issue. I will go through them there. Thank you as well for the kind note about taking breaks.
Leaving the Denon out for now is the right call. Once native output works over the direct HDMI connection, your offer to test it with the receiver in between will be very useful.
Haha, I understand about the Homatics. I also have one with my own custom build based on the nightlies, which I have not uploaded, but I do appreciate the performance difference a PC can give.
Hi everyone, I’m not sure if this is the right thread for my question, but how do I adjust the volume in VacuumTube? It works when using a connected keyboard (via the + and - keys), but it doesn't work when using a remote control (via the volume up/down buttons). I’m using LibreELEC 13 and running VacuumTube via Flatpak. Thanks!
Posting a quick diagnostic summary from testing on my setup with the current build (`DV-R1.0.0-RC3 Generic.x86_64` on Intel Arc)
1. Native Profile 7 FEL is Fully Functional: - True 4K UHD Blu-ray Remux files (Profile 7 FEL with lossless TrueHD Atmos) trigger Dolby Vision correctly on my display and AVR. The enhancement layer reconstruction is decoding and playing smoothly.
2. HDR to DV Tone-Mapping Does Not Engage: - Standard HDR10 streams fall back to native HDR10 output. - The on-the-fly conversion/tunneling of standard HDR10 into Dolby Vision is not happening. Is there a specific configuration toggle, player setting, or kernel module flag required on Intel Arc to force HDR-to-DV tone-mapping?
3. Diagnostics Clarification (MegaNexus vs Native Kodi): - Native Kodi PlayerProcessInfo HUD (invoked via action `PlayerProcessInfo` / OSD control 70050) is 100% functional, confirming active hardware decoding (`ff-hevc-vaapi`) and solid cache/buffer performance. - The MegaNexus skin diagnostic card fails and displays "Source layer: Unknown / Base layer is shown" solely because its backend script (`dv_diagnostics.py`) hardcodes checks for Amlogic sysfs nodes (`/sys/class/amhdmitx/`, `amvdec`) which do not exist on x86 hardware.
Looking forward to testing the new support build next week whenever you get back to your desk. Thanks for the great work on this project!
Posting a quick diagnostic summary from testing on my setup with the current build (`DV-R1.0.0-RC3 Generic.x86_64` on Intel Arc)
1. Native Profile 7 FEL is Fully Functional: - True 4K UHD Blu-ray Remux files (Profile 7 FEL with lossless TrueHD Atmos) trigger Dolby Vision correctly on my display and AVR. The enhancement layer reconstruction is decoding and playing smoothly.
2. HDR to DV Tone-Mapping Does Not Engage: - Standard HDR10 streams fall back to native HDR10 output. - The on-the-fly conversion/tunneling of standard HDR10 into Dolby Vision is not happening. Is there a specific configuration toggle, player setting, or kernel module flag required on Intel Arc to force HDR-to-DV tone-mapping?
3. Diagnostics Clarification (MegaNexus vs Native Kodi): - Native Kodi PlayerProcessInfo HUD (invoked via action `PlayerProcessInfo` / OSD control 70050) is 100% functional, confirming active hardware decoding (`ff-hevc-vaapi`) and solid cache/buffer performance. - The MegaNexus skin diagnostic card fails and displays "Source layer: Unknown / Base layer is shown" solely because its backend script (`dv_diagnostics.py`) hardcodes checks for Amlogic sysfs nodes (`/sys/class/amhdmitx/`, `amvdec`) which do not exist on x86 hardware.
Looking forward to testing the new support build next week whenever you get back to your desk. Thanks for the great work on this project!
Display More
Could you please send me the log,
And unfortunaty for skin I can not expose the information like amlogic and dolby, but I have a comprehensive player info pannel, and thanks to a great developper we will have a new play info soon
Player information now reads in three columns: Input (what the file carries), Processing (what CB1 does with it) and Output (what leaves the box). Each column…
And unfortunaty for skin I can not expose the information like amlogic and dolby, but I have a comprehensive player info pannel, and thanks to a great developper we will have a new play info soon
Separating it cleanly into Input -> Processing -> Output makes tracking the entire pipeline so much clearer—especially having the CB1 engine/DVDVMR circuit status, active RPU metadata blocks, and TV-Led tunnel precision right there in a native panel without having to rely on skin add-on scripts.
Following up on the log: I pulled up the native Player Information HUD during playback of an HDR10+ stream (screenshot attached), and it reveals the exact roadblock:
Under "OUTPUT & PROCESSING": - Requested policy: Dolby Vision Rendering - Pending output: Admission checked (not committed) - Output availability: Source cannot use this processing mode
The player is actively requesting Dolby Vision output, but the CB1 engine is reporting that the HDR10/HDR10+ source cannot use this processing mode, dropping the tunnel back to native HDR.
Let me know if this is a known limitation with the HDR10/HDR10+ admission logic in RC3 that will be resolved in your upcoming support build early next week. Thanks!
Whenever you get a moment to review the log, please let me know what you see regarding why HDR-to-DV conversion isn't engaging on my Intel Arc setup. Looking forward to the upcoming player info panel as well!
RC4 Preview is up with certain fixes, much like with RC3, the preview will receive small, regular updates.
Hardly any changes, no further updates expected over the weekend or early next week.There are things that are higher priority, Zelda Ocarina of time is available
LibreELEC x86_64 with Dolby Vision support for Intel, AMD, and Nvidia. I REBASE MY REPO UNTIL THE STABLE RELEASE - Releases · CroqueMr/libreelec-x86-DV
I pulled up the current Player Information screen on my RC3 build during playback of an HDR10+ stream (screenshot attached), and it caught the exact admission failure:
Under OUTPUT & PROCESSING: - Requested policy: Dolby Vision Rendering - Pending output: Admission checked (not committed) - Output availability: Source cannot use this processing mode
Kodi requests Dolby Vision, but CB1 returns "Source cannot use this processing mode" and drops back to native HDR.
Is there any config toggle or parameter in RC3 to bypass this admission check, or is HDR-to-DV conversion admission for Intel Arc also being addressed in the upcoming support build?
I pulled up the current Player Information screen on my RC3 build during playback of an HDR10+ stream (screenshot attached), and it caught the exact admission failure:
Under OUTPUT & PROCESSING: - Requested policy: Dolby Vision Rendering - Pending output: Admission checked (not committed) - Output availability: Source cannot use this processing mode
Kodi requests Dolby Vision, but CB1 returns "Source cannot use this processing mode" and drops back to native HDR.
Is there any config toggle or parameter in RC3 to bypass this admission check, or is HDR-to-DV conversion admission for Intel Arc also being addressed in the upcoming support build?
