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

  • Thanks for your reply!

    I understand your point, but my experience with your build is actually a little different.

    Regular Blu-ray discs play perfectly fine directly from my optical Blu-ray drive under your LibreELEC build, including menus and normal playback.

    Even my original 3D Blu-ray starts playing directly from the optical drive. However, instead of native HDMI 3D frame packing, I get two images side by side.

    Looking at the compatibility table in your video, both 3D Blu-ray ISOs with BD-J menus and MVC MKVs are marked as working.

    This makes me wonder whether the actual MVC decoding is already working in my case, and only the native 3D frame-packing output is failing.

    Since my Optoma projector correctly reports "3D present" in its EDID, could the limitation be related to my Ryzen 5 2400G / Vega 11 and its DisplayPort-to-HDMI connection?

    In other words, is native HDMI 3D frame packing technically supported on Vega 11 through DisplayPort-to-HDMI in your build, or is a native HDMI output required?

    I'd really appreciate your technical opinion on this.

    Thanks again for your work!

  • about 3D part i don't know.

    i have 3400g (vega 11 as igpu), plays dv p7 fel very nice

    but DisplaPort doesn't work with DV profile 7 FEL. this is sure !!!

  • Thanks to both of you for your replies!

    ht2tweak Thanks for pointing me towards CroqueMr and hadesdevls.

    testmest Your experience with the Ryzen 3400G / Vega 11 is particularly interesting, especially the DisplayPort limitation.

    My HP EliteDesk 705 G4 SFF with Ryzen 2400G / Vega 11 currently uses DisplayPort-to-HDMI.

    Interestingly, HP also offered an optional HDMI output module for this model, which I could potentially install.

    Before buying additional hardware, I'd really like to know whether native HDMI 3D frame packing is supported by this build on Vega 11 at all.

    CroqueMr  hadesdevls Could you please clarify whether the AMD 3D implementation supports Vega 11, and whether a native HDMI output is required?

    My original 3D Blu-ray already plays directly from the optical drive, but only displays two images side by side instead of frame-packed 3D.

    Thanks again for your help!

  • about 3D part i don't know.

    i have 3400g (vega 11 as igpu), plays dv p7 fel very nice

    but DisplaPort doesn't work with DV profile 7 FEL. this is sure !!!

    has to be native HDMI , the data goes through hdmi or something. a hdmi adaptor from DP to HDMI won't even work. has to be linked to gpu using native hdmi

    Samui67 yeah it isn't really a limitation, there is no other way

  • Hello, I am running the RC3 build and having some playback issues. On an Intel Tiger Lake-H laptop, Kodi freezes (black screen, UI unresponsive, process stays alive) in several playback situations that do not use the Dolby Vision renderer. Dolby Vision files, and HDR10 files with "HDR10 playback" set to "Dolby Vision Rendering", play correctly. The main thread is blocked in `drm_syncobj_wait_ioctl` and never returns. This seems related to the "Tiger Lake 10-bit driver issue" listed under known issues, but it also happens with plain SDR content, with no 10-bit surface recreation in the log.

    ## System
    - Build: LibreELEC (community) `DV-R1.0.0-RC3`, build `00615a5a5e-backlog-fba738eba0`, Kodi 22.0-RC1 (21.90.901), kernel 7.2.6, Mesa 26.2.3
    - Laptop: ASUS ROG Zephyrus M16 (GU603HM), i7-11800H, Intel UHD Graphics (TigerLake-H GT1, 8086:9a60) + NVIDIA RTX 3060 Mobile (GA106M)
    - Display: HDMI port is on the Intel GPU (`card0 HDMI-A-1`); the RTX 3060 has no connected output. Sink is an Onkyo AV receiver (EDID reports standard DV, HDR10, PQ and HLG)
    - Boot: installed to NVMe; internal panel disabled with `video=eDP-1:d`
    - Settings: Dolby Vision playback mode 4 ("HDR10 Rendering"); HDR10 playback tried with 0 ("Kodi default") and 1 ("Dolby Vision Rendering")
    - Content is played over SMB, or through PlexKodiConnect, from another machine

    ## What works
    - Dolby Vision files, including FEL (MP4 FEL test clips and a DV REMUX): stable, 0 drops in steady state
    - HDR10 file with HDR10 playback set to "Dolby Vision Rendering": plays

    ## What hangs (each reproduced more than once)
    1. **2160p SDR HEVC WEB-DL (H.265, DD+ 5.1), repeatable on every attempt.** Hangs right after playback starts, before the first picture is presented (`stream=0 picture=0`). Last log lines before the hang:
    ```
    VideoPlayer: OnLostDisplay received
    CB1 shader cache: loaded=40 api=372 stream=0 picture=0 ...
    VideoPlayer: OnResetDisplay received
    FindVideoPlane(): Adopting gui plane as video plane [3840x2160] id:36, format:AR24, modifier:INTEL_Y_TILED_GEN12_RC_CCS_CC
    Display resolution ADJUST : 3840x2160 @ 23.976000 Hz
    ```
    Then nothing further. `/proc/<kodi pid>/stack` shows `drm_syncobj_array_wait_timeout` / `drm_syncobj_wait_ioctl`.

    2. **HDR10 file with HDR10 playback = "Kodi default".** Hangs right after `Output surface recreated at 10-bit` and `Adopting gui plane as video plane [3840x2160] format:AR30, modifier:INTEL_Y_TILED_GEN12_RC_CCS_CC`, with `hdr_value` set and `colorspace_value=9`.

    3. **Player process-info dialog (the `O` key) on an HDR10 file already playing through the DV path.** The dialog (`DialogPlayerProcessInfo.xml`) loads, then `Output surface recreated at 10-bit`, DV is deactivated (`requested_dv=0 restoring=true`) and Kodi hangs the same way.

    Separately, on a DV FEL file, opening the same dialog causes a one-off hitch of about 1 second (20–32 dropped frames, two `OutputPicture - timeout waiting for buffer` warnings) and then plays cleanly. No hang.

    ## What I ruled out
    - **Storage:** reproduced on both a USB 2 stick and an NVMe SSD
    - **GPU clock or CPU power state:** pinned the GPU to 1450 MHz minimum and CPU EPP to performance; no change in the hang or the drops
    - **Temperature:** CPU package about 46–50 °C
    - **Hardware HEVC decode:** disabled `videoplayer.usevaapihevc`; the SDR file still hangs
    - **VT-d for graphics:** added `intel_iommu=igfx_off` (kernel confirms `DMAR: Disable GFX device mapping`); no change
    - **Optimized GUI rendering (`dvbridge.optimizedgui`):** no change
    - **Kernel GPU state:** `i915_engine_info` showed Reset count 0 and, in one case, a `hungE` request from kodi.bin on rcs0; in other cases no hung request, so it is not always an engine hang that i915 detects. No i915 errors in dmesg.

    ## Notes
    - NVIDIA kernel modules load, but `nvidia-drm` reports "Cannot find any crtc or sizes", so the dGPU does not drive the display.
    - Happy to provide full `kodi.log` files, `dmesg`, and `i915_engine_info` captured during a hang.
    - Not yet tested on the AMD Cezanne iGPU in a VM with this exact build: *fill in if you have tested it*.


  • From CroqueMr
    https://forum.kodi.tv/showthread.php?tid=385600&pid=3315592#pid3315592

    Quote

    And no, unfortunately, DV doesn't work over DP. You need a native HDMI output with no adapters or converters in between. Technically, we could modify the drivers for some DP -> HDMI converters, but that's way too messy.
    Also, be careful with desktop PC, even if they have an HDMI port, it isn't always native HDMI. Sometimes it's actually DP behind, which means DV won't work. This is pretty common with 8th and 9th gen Intel systems


    and this when I asked dev about that hdmi module

    Quote

    and

    No it's not a native HDMI port, you can even see the DP converter on the board.

    A native HDMI port is wired directly to your GPU or iGPU, if you have a module like that, you always have a DP converter to something else

    https://forum.kodi.tv/showthread.php?tid=385600&pid=3315646#pid3315646

    I gave up on those business machines, it has to be a native HDMI port, no adapter or module. It won't work

  • DV over DP->HDMI is possible. I have it working on PS5 and Intel iGPU (only tested on Kaby Lake so far).

    Yeah it's possible but not on all converter, and if we need to adjust driver for all LSPCON it will be a nightmare to maintain.

    DP should be ok for 3D, can you send me the log? for DP to HDMI as I said, it's too sketchy and complicated to support it properly, and yes the HDMI module is a DP converter you can not have a native HDMI output using your iGPU on this PC unfortunatly.

  • Hello, I am running the RC3 build and having some playback issues. On an Intel Tiger Lake-H laptop, Kodi freezes (black screen, UI unresponsive, process stays alive) in several playback situations that do not use the Dolby Vision renderer. Dolby Vision files, and HDR10 files with "HDR10 playback" set to "Dolby Vision Rendering", play correctly. The main thread is blocked in `drm_syncobj_wait_ioctl` and never returns. This seems related to the "Tiger Lake 10-bit driver issue" listed under known issues, but it also happens with plain SDR content, with no 10-bit surface recreation in the log.

    Try the current RC 4 preview build and, under system, force 8 bit color depth output. I am currently using a i3-1115G4 (Tiger Lake as well) and I discovered that, otherwise, even SDR gets outputted as 10bit. And that messes up everything on our machines.

    If the above setting solves things for you, you have my same exact situation.

  • Thinking about switching from the AM6B+ to a mini pc that can do LE. Specifically one that's 16GB ram and H 255.

    Wondering what I'm gaining here. Will Plex 4K Kodi be able to read higher bit rates? Will it has LLDV as good as the UGOOS? Sorry if all of these have been answered but I just want cliff notes.

  • Thinking about switching from the AM6B+ to a mini pc that can do LE. Specifically one that's 16GB ram and H 255.

    Wondering what I'm gaining here. Will Plex 4K Kodi be able to read higher bit rates? Will it has LLDV as good as the UGOOS? Sorry if all of these have been answered but I just want cliff notes.

    I don't think it currently does LLDV, not sure about PLEX.

  • Hi CroqueMr,

    Thank you for your reply and for looking into this!

    I've attached a sanitized excerpt from my Kodi log, focusing on the 3D Blu-ray playback attempt. Some unrelated entries have been removed for privacy.

    The original 3D Blu-ray (Doctor Strange) is played directly from the internal optical drive of my HP EliteDesk 705 G4 SFF (Ryzen 5 PRO 2400G / Vega 11).

    My setup is:

    DisplayPort → 30 cm 4K DP-to-HDMI cable → HDMI splitter → Optoma UHD projector

    The same HDMI splitter works correctly with my Panasonic UHD Blu-ray player, including native Blu-ray 3D and 4K output.

    One thing I noticed in the log is:

    [WHITELIST] Searching the whitelist for: width: 1920, height: 1080, fps: 23.976, 3D: true

    Followed by:

    Display resolution ADJUST : 1920x1080 @ 23.976080 Hz 3D sbs (32)

    Kodi seems to recognize the 3D content but selects SBS instead of frame packing.

    Could this be related to the available DRM display modes or the DP-to-HDMI connection?

    I'd appreciate your thoughts.

    Thanks again for your help!

  • Hi CroqueMr,

    First off, huge appreciation for the build and the R1.0.0-RC4 release! Testing on an Intel Arc GPU with LibreELEC x86 connected to a Denon AVR and Sony A80K OLED, the CB1-HDR10DVR circuit is performing exceptionally well—flawless TV-Led / YCbCr tunnel inside RGB 4:4:4 / 8-bit, solid TrueHD Atmos / DTS:X passthrough, and zero frame drops with real-time AI metadata generation (CB1-L1L3).

    Feature Request: Could you consider adding an opt-in SDR -> Dolby Vision conversion circuit (e.g., CB1-SDRDVR / inverse tone-mapping) in a future update?

    Currently, standard 8-bit BT.709 SDR streams rightly bypass processing and stay in "SDR / Kodi playback". Having a dedicated CB1 SDR mode that can map Rec.709 gamma into the Dolby Vision tunnel (expanding specular highlights while anchoring SDR 100-nit diffuse white to preserve tones and shadow detail) would be fantastic for SDR Blu-ray remuxes and regional web streams.

    Would an inverse tone-mapping circuit like this fit into the roadmap alongside HDR10/HDR10+, or does the engine intentionally strictly restrict to HDR sources?

    Thanks again for the incredible work!

  • Kodi seems to recognize the 3D content but selects SBS instead of frame packing.

    I checked your log: Kodi is on connector DP-3 and its mode list has no 3D modes (no 1920x2205 frame-packing line). On AMD the kernel patch behind 3D on these builds offers those modes only on real HDMI connectors, because DP-to-HDMI dongles rejected the 3D timings in link validation.

    The "3D sbs (32)" is the same plain 1080p mode (32) as your 2D playback, with Kodi drawing both eyes side by side. No 3D signal reaches the projector, which is why you see two images. So the limit is the DP output, not Vega 11, and SBS or TAB files need the same 3D modes. We have only tested 3D on native HDMI.

  • Hi cinemaONE and CroqueMr,

    Thank you both for your explanations and for taking the time to investigate my log!

    I understand that the current AMD 3D kernel patch only exposes frame-packing modes on native HDMI connectors, while my DP-to-HDMI connection fails to provide these modes.

    Since CroqueMr mentioned that DP should be OK for 3D, I was wondering whether extending the kernel patch to support DP-to-HDMI connections might be technically feasible.

    I'd be very happy to volunteer as a test candidate for an experimental kernel patch or custom LibreELEC build.

    I've been working with Linux-based HTPCs since 2004, starting with VDR, followed by OpenELEC, LibreELEC, CoreELEC and other systems.

    My hardware is available for testing, and I can provide logs, EDID information and detailed feedback.

    The same HDMI splitter and Optoma projector already work correctly with native Blu-ray 3D from my Panasonic player.

    Of course, I understand that such a patch might require significant development work and may not be possible.

    Thanks again for your excellent work!

  • I’ve been around since the first days of CE having FEL support and I watched CPM get burnt out by incessant requests while the CE team got so fed up that they banned all discussion of forks. I don’t want to see this replicated here. The code is already an enormous amount of effort that has taken over CroqueMr life over the past month. I’ve seen them delay their work to fix this which is a danger sign. I also want perfect Dolby Vision, but not at the cost of somebodies mind, job or happiness.


    DP-to-HDMI conversion adds a whole new layer of complexity to code and support. Sure, it would be nice, but, frankly, not necessary. Let’s let the core work be finished and give all the devs a well-deserved break.