Posts by Unsigned0207

    Attaching the logs here.

    What happened in each test (the time is when the O dialog opened)

    FilmDialog openedWhat the log shows
    Bad Apples (SDR)14:07:47OutputPicture - timeout waiting for buffer at 14:07:48. No frame counters exist for this film.
    The Odyssey (HDR10)about 14:08:48The same buffer timeout. In that 10-second window, 1 frame dropped and 44 skipped.
    Mission Impossible (DV FEL)about 14:09:48The same buffer timeout. 21 frames dropped, 2 skipped.
    • Common pattern: every film shows the same buffer timeout at the moment the dialog opens, followed by a short burst of drops or skips. After that the log shows no more.
    • Bad Apples has no drop count: Kodi’s frame statistics only exist on the Dolby Vision path. For plain SDR playback, the buffer timeout is the only evidence, so tell the author that.

    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.

    I tried this on the new RC4 and set the maximum bit depth to 8. That fixed the issue for 4k SDR and 4K HDR movies. But as expected all the 10 bit and now being downsampled to 8 bit. Also still have massive frame drops and stuttering when a movie is playing and you trigger the OSD using the O button on the keyboard. Again this only happens with Tigger Lake. I ran another using vm on proxmox with AMD Ryzen 5 5600G and it had no such issues.

    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*.