HDR10 blanking screen intermittently on Nightlies (not on stable), plus wrong video output levels.

    Quote from smp

    Try this image. I disabled HDMI scrambling in Intel driver.

    Could you double check the image? I can't seem to be able to write it. I am using the LibreELEC USB-SD creator that I've used many times in the past few days but when I click on write the progress bar simply cycles the "light blue effect", without giving any percentage. I tried waiting some minutes and then ejecting the key and trying to boot but I received errors from LE run process. I have tested on two different keys (both new, I bought them two weeks ago and they've always worked fine).

    EDIT: used Balena on Linux and it went ok... I don't what's wrong with the creator tool. Maybe I should reboot the Windows machine. Yes, the build runs fine, it just booted. Now I'll test.

    Hi smp some new data points. If I leave color bit depth to auto, I assume it tries switching to 12 bit and no signal is received. But it I limit it to 10 bit, it works. Just fine, it works. No glitching.

    BUT (and this is unfortunately a deal breaker) the first test was conducted before configuring audio. Once I activated passthrough, the Atmos stream started having intermittent sound breaks, like a split second of silence here and there.

    So with sound decoded to PCM it was fine. When I activated Atmos, the remux file I'm using started to randomly drop bits of audio.

    Crap... :( for a little while I was so hopeful.

    (your builds incorporate the video levels, 16-235 fixed you liked before, right?)


    EDIT: last thing I checked, if I deactivate passthrough but set speaker layout to 7.1 (which my system handles anyway), I don't get any audio glitches. It's just Atmos. And that I think rules out bandwidth as the source of the problem. Uncompressed 7.1 PCM I'm pretty sure outweighs an Atmos stream (that's 7.1 compressed as mlp, meridian lossless packing).

    Edited 3 times, last by ashlar: Merged a post created by ashlar into this post. (November 5, 2026 at 4:28 PM).

    Hello, I tried to fix the blanking remotly with my support and remote control build with very precise log (the build is based on my DV build unfortunatly, but the issues is also present in my build) nothings very huge but this is my findings

    - There was no Kodi crash or GPU reset clearly associated with the blackouts, it is not a bandwith limitation issue. 8bits at high refresh rate that need more bandwith do not have black screen.

    - HDMI monitoring caught brief losses and recoveries of the channel 0 lock, while clock detection and scrambling remained active. However, not every reported blackout had a corresponding lock change but every sample that had a black screen had at least a lock change captured in the log, so this isn’t a complete explanation and it is more the problem capture than anything else.


    All logs and reports (made by codex sol 6.1) : https://files.catbox.moe/sle3we.zip

    The only other thing I can report, last I wanted to try, is that even remuxes with DTS-X audio have small glitches. Going by memory they seem less... long? As if in Atmos the glitches mute the audio for 0.2 / 0.3 seconds while in DTS-X the audio has a very, very small glitch, like 0.05 seconds.

    Don't know if this could be in any way relevant but I thought about adding the info.