Try this image. I disabled HDMI scrambling in Intel driver. That's been known to fix signal dropouts on some Samsung/LG TVs.
Posts by smp
-
-
-
-
-
Could you link it here, please?
windowing/gbm: add a colour range setting and signal it via Broadcast RGB by smp79 · Pull Request #30099 · xbmc/xbmcDescription On GBM, "Use limited colour range" compresses the levels to 16-235 in Kodi's shaders but never tells the display: the connector's…github.com -
My TV is calibrated to 16-235, I activate "Use limited color range (16-235) under Settings/System/Display/General but if I play back both HDR and SDR material, black level is raised, obviously wrong looking.
That's because levels are compressed twice - in the shaders and by the driver. I have an open Kodi PR with a fix.
I tested the stable release (12.2.1) and it doesn't happen.
Your NUC has 2 HDMI ports - one native, the other one via DP PCON. Try another port.
-
IMO this should stay in community builds.
-
-
It stays with the metadata of the intro until playback stops.
https://github.com/xbmc/xbmc/pull/26731. Apparently mid-stream video reconfigure would cause black screens. I tested with The Abyss sample (with that PR reverted) and there is indeed a small glitch during metadata change.
-
-
It will not work with LE. HW deinterlacing require Amlogic BSP kernel.
-
I think this may be outdated and no longer correct?
Yes, interlaced is always doubled.
QuoteFor this rate doubling to work, we need to ensure the whitelisted 1080p modes do not contain 1080p @ 25/29.97/30Hz rates, else Kodi will see an exact match against resolution and refresh rate and you will see high CPU loads and 50% of frames being dropped.
As far as I remember that was true for Generic-X11 (Legacy).
-
Post the debug log. AV1 plays fine on my pc with hw decode.
-
Our general preference with packages is to always be explicit in what we enable.
I don't see how this is relevant to this particular case. The only use case for setting codecs explicitly is to disable non-free codecs. That was the only reason for the 2022 Mesa change.
In 2022 codecs were set explicitly in LE only because there was no other choice due to that questionable Mesa change. It already caused MPEG2 breakage (unnoticed for years), then it caused av1 and vp9 breakage, it would cause more breakage in the future when new codecs will arrive.
In 2023 PR Mesa tried to fix their mess by introducing "all" and "all_free" options. "all" is the safest option, it simply brings back the old behaviour (pre-2022 changes).
Do you have sample media that exhibits those problems or a link to a thread discussion such? Would like to test such media on my rx 6600
That was in circa 2020 when I still had Vega 3 APU. I don't remember which MPEG2 videos caused issues. Try some random DVDs with vaapi on and off. I remember there was a discussion about this but I can't find it.
-
Our preference has always been to be explicit
In this case "all" is the correct option for LE. This is the "video codec support option" PR in Mesa that was the reason for this change. "all" option didn't exist back then, so it was needed to set codecs explicitly.
This Mesa PR introduced the "all" option, so "-Dvideo-codecs=all" would restore the old behaviour.
-
meson: Add all, all_free (default) options for video-codecs option (!26320) · Merge requests · Mesa / mesa · GitLabWhat does this MR do and why? What: Adds two new possible values to the -Dvideo-codecs build option: 'all' and 'all_free'...gitlab.freedesktop.org
Looks like it should changed to -Dvideo-codecs=all to enable all codecs rather than list them individually. Current Mesa defaults to "all_free" if "video-codecs=' is not used.
-
Maybehttps://github.com/LibreELEC/LibreELEC.tv/pull/7280is not needed anymore. What happens if you revert it rather than add mpeg2?In any case, vaapi-mpeg2 is problematic on AMD, image quality-wise. At least that's how it was a few years ago but I don't think anything changed.
-
So I guess kodi outputs a standard BT709/gamma SDR image, but signals BT2020 colorspace which doesn't quite match.
I'll ping reardonia with this. Does indeed look like a Kodi bug.