What about our GPUs (via modetest), and Kodi itself (via the limited color range option)?
Forcing RGB full/limited is only needed in some special cases when you know what you are doing.
Kodi's color range setting seems broken. Has an effect only on GUI, at least on Generic.
So Lanczos3 optimized performs better on Windows? It's quite possible that Windows GPU driver performs better than Mesa driver on that ancient Sandy Bridge iGPU.
You can also try Generic-Legacy LE image and Generic LE 13 nightly, maybe you'll get better results.
Select a different scaling method, eg. Bilinear
the issue on the intel gitlab is completely stalled as cannot reproduce
I'm not convinced that this is an Intel issue. Looks to me that those affected AVRs (Denon?) are all using the same chipset which has some issue with 4K 12-bit modes.
Name it kodi-aesinkalsa-fix.patch
Messing about with those cache settings would not make high bitrate 4K videos (UHD BDs?) play smoothly on 100Mbit LAN. You will have to upgrade to Gigabit.
Dell Optiplex 3070 micro
The onboard HDMI on this is v.1.4 so it can not possibly pass through HDR.
Kodi was previously able to play HDR content when the Optiplex was running Windows 10
TV switched to HDR mode? How it was connected to the TV?
Odd but for some reason Intel has no support for YCbCr 4:2:2
YCBCR 4:2:0 handling in DRM layer [LWN.net]
They initially added 4:2:2 but then dropped it.
I tried to re-add it with this patch but after applying it the colors are wrong, so I obviously missed something.
My Samsung TV would switch to PC mode only if the device icon is named "PC". It does not matter if the signal is RGB or YCbCr.
How can I get Libreelec to output YCbCr
I have AX201 and it works fine in LE. I would assume AX200 should work too.
Could be related to this change.
It should be reported in a new Kodi github issue.
Looks the same as
and
Anyone got any ideas what can be done to solve the problem?
Maybe open another Kodi github issue?
diff --git a/drivers/gpu/drm/i915/display/intel_hdmi.c b/drivers/gpu/drm/i915/display/intel_hdmi.c
index 7816b2a..758f3dc 100644
--- a/drivers/gpu/drm/i915/display/intel_hdmi.c
+++ b/drivers/gpu/drm/i915/display/intel_hdmi.c
@@ -2196,7 +2196,7 @@ intel_hdmi_output_format(struct intel_connector *connector,
if (connector->base.ycbcr_420_allowed && ycbcr_420_output)
return INTEL_OUTPUT_FORMAT_YCBCR420;
else
- return INTEL_OUTPUT_FORMAT_RGB;
+ return INTEL_OUTPUT_FORMAT_YCBCR444;
}
static int intel_hdmi_compute_output_format(struct intel_encoder *encoder,
@@ -2215,8 +2215,8 @@ static int intel_hdmi_compute_output_format(struct intel_encoder *encoder,
if (ycbcr_420_only && crtc_state->sink_format != INTEL_OUTPUT_FORMAT_YCBCR420) {
drm_dbg_kms(&i915->drm,
- "YCbCr 4:2:0 mode but YCbCr 4:2:0 output not possible. Falling back to RGB.\n");
- crtc_state->sink_format = INTEL_OUTPUT_FORMAT_RGB;
+ "YCbCr 4:2:0 mode but YCbCr 4:2:0 output not possible. Falling back to YCBCR444.\n");
+ crtc_state->sink_format = INTEL_OUTPUT_FORMAT_YCBCR444;
}
crtc_state->output_format = intel_hdmi_output_format(crtc_state);
@@ -2247,7 +2247,7 @@ int intel_hdmi_compute_config(struct intel_encoder *encoder,
adjusted_mode->flags & DRM_MODE_FLAG_INTERLACE)
return -EINVAL;
- pipe_config->output_format = INTEL_OUTPUT_FORMAT_RGB;
+ pipe_config->output_format = INTEL_OUTPUT_FORMAT_YCBCR444;
if (pipe_config->has_hdmi_sink)
pipe_config->has_infoframe = true;
This kernel patch would force YCbCr 4:4:4 on Intel.
I know there's probably a way to override it like we use to.
Only by hacking Kodi.
Why use oscam at all? Tvheadend has pretty much all of the oscam's CA client functionality.
Meteor Lake support could be buggy in kernel 6.6. Try LE 13 nightly (non-legacy).
I think you'll need to apply this commit.
