8bit signal
Try setting the "EDID" to "Expanded". If this does not work dump the projector's EDID and post it here.
BT.709 color space
Use my build for BT.2020
4k 10bit 24hz 4:2:2
4:2:2 is not supported by Intel. However, I seriously doubt that it is really required.
I cannot see that TV settings are relevant as the colours are correct when running Kodi for windows on 24hz or any other settings.
Intel GPU driver for Windows may behave differently, e.g. it can support YCbCr output, in Linux it only supports RGB. Your issue has something to do with incorrect handling by your display of RGB full / RGB limited at 24Hz. Most modern TVs have a user selectable quantization range for RGB and also the Auto setting.
I had this issue with J4105 board + 2018 Samsung 4K TV.
4K 50/60Hz mode should work with LE11 and HDMI UHD Color=off. It will be limited to 4:2:0 8-bit.
Try to disable "Input Signal Plus / HDMI UHD Color" in Samsung TV settings (General-->External Device Manager).
It is broken in 20.1 and master. Removing this part of the code fixes it:
diff --git a/xbmc/cores/VideoPlayer/DVDDemuxers/DVDDemuxFFmpeg.cpp b/xbmc/cores/VideoPlayer/DVDDemuxers/DVDDemuxFFmpeg.cpp
index bc6b54c..7f58204 100644
--- a/xbmc/cores/VideoPlayer/DVDDemuxers/DVDDemuxFFmpeg.cpp
+++ b/xbmc/cores/VideoPlayer/DVDDemuxers/DVDDemuxFFmpeg.cpp
@@ -525,23 +525,6 @@ bool CDVDDemuxFFmpeg::Open(const std::shared_ptr<CDVDInputStream>& pInput, bool
"empty. Please report this bug.");
}
- // don't re-open mpegts streams with hevc encoding as the params are not correctly detected again
- if (iformat && (strcmp(iformat->name, "mpegts") == 0) && !fileinfo && !isBluray &&
- m_pFormatContext->nb_streams > 0 && m_pFormatContext->streams != nullptr &&
- m_pFormatContext->streams[0]->codecpar->codec_id != AV_CODEC_ID_HEVC)
- {
- av_opt_set_int(m_pFormatContext, "analyzeduration", 500000, 0);
- m_checkTransportStream = true;
- skipCreateStreams = true;
- }
- else if (!iformat || ((strcmp(iformat->name, "mpegts") != 0) ||
- ((strcmp(iformat->name, "mpegts") == 0) &&
- m_pFormatContext->nb_streams > 0 && m_pFormatContext->streams != nullptr &&
- m_pFormatContext->streams[0]->codecpar->codec_id == AV_CODEC_ID_HEVC)))
- {
- m_streaminfo = true;
- }
-
// we need to know if this is matroska, avi or sup later
m_bMatroska = strncmp(m_pFormatContext->iformat->name, "matroska", 8) == 0; // for "matroska.webm"
m_bAVI = strcmp(m_pFormatContext->iformat->name, "avi") == 0;`Updated build with Kodi 20.1
- added BT.2020 patch
- Linux 6.2.5
- added a fix for DTS-HD detection in m2ts files
- added a fix for GUI flickering during TV channel switching
- Intel media-driver updated to 23.1.3
- Mesa updated to 23.0.0
LibreELEC-Generic.x86_64-11.0-devel-20230312065957-84d83d1.img.gz
The new build is based on "vanilla" Kodi. It is almost the same as official LE11 image. The old one was based on lrusak's HDR branch which isn't updated since April last year.
Copy it to /storage
Can anybody give instructions to acomplish this.
Add only this:
~/./proptest -M i915 -D /dev/dri/card0 95 connector 97 1Look for "HDMI black level" or something similar in your TV's settings.
I can reproduce this with AV1 10-bit video. Probably some issue with Intel media-driver and/or ffmpeg.
As a workaround you can disable AV1 hardware decoding (Player -> Use AV1 VAAPI -> off).
lrusak hasn't updated his HDR repo for a long time, so no new builds.
Some of his HDR work was merged in Kodi, so it partially works in official builds.
Only HEVC 24p HDR10 videos seem to work for now.
What does not work (TV does not switch to HDR mode): VP9 HDR videos, HLG videos, any 50/60 fps HDR videos.
Also, Kodi require an extra patch that allows the TVs to switch to BT2020 colorimetry mode. This is not yet merged in Kodi.
This build include the BT2020 patch. What does it say if you play 4K HDR file at 60Hz?
Why would you want it to boot from an SD card? Why not boot from USB and install to internal eMMC?
HDR requires HDMI 2.0 or DP 1.4. This board has neither.
What motherboard?
That image was intended for Noumenon for troubleshooting his projector issue with his NUC11. The reason for tigerlake optimization flag is that I use it in my personal builds and I don't really have time to do a clean build with default gcc optimization flags.