4K 4:2:0 with Deep color is not a part of HDMI spec. It should always be 8-bit.
No idea how to force YCbCr 4:4:4. Intel driver knows what's best for you and use RGB.
4K 4:2:0 with Deep color is not a part of HDMI spec. It should always be 8-bit.
No idea how to force YCbCr 4:4:4. Intel driver knows what's best for you and use RGB.
From memory, to get it working I booted the j4105 with the TV in UHD mode, got the available UHD modelines via SSH, and then added them via a boot script and xrandr.
That will not give you the 12-bit Deep color modes in 4K (10-bit is not supported by GLK hardware). There is no difference how you force it to output the desired modes.
I also tried to mess around with editing the EDIDs dumped with both HDMI UHD Color On and Off to narrow down the issue.
Any 4K mode that requite the HDMI pixel clock higher than 297 Mhz give "no signal".
Intel driver does not support YCbCr 4:2:2 output. When the EDID report the max.pixel clock of 297 Mhz (UHD Color Off) - Intel driver is using those modes for 4K and they work fine:
4K 24/25/30Hz RGB 8-bit
4K 50/60Hz YCbCr 4:2:0 8-bit
When the EDID report the "high speed" pixel clock mode (594 Mhz) is available - Intel driver is using those modes (and they give no signal):
4K 24/25/30Hz RGB 12-bit
4K 50/60Hz RGB 8-bit
IMO the issue has something to do with Samsung having limited support for 4K RGB modes. It probably expects YCbCr 4:2:2 which Intel does not support.
I know still are some incompatibility example with Samsung HDR TV, which is actually issue of intel driver/
I tried to figure out what is causing that "no signal" issue on Samsung TV when "HDMI UHD color" is enabled.
At first I thought that Samsung does not support 4K RGB modes with Deep Color. But the odd thing is that when trying 4K 50/60 modes - Intel driver is switching to RGB 8-bit and it doesn't work as well.
So, the only 4K HDMI modes that work with GLK+Samsung TV are:
4K 24/25/30Hz RGB 8-bit
4K 50/60Hz YCbCr 4:2:0 8-bit
It's a new Comet Lake CPU. No wonder LE 9.2.0 does not support it. Use the Milhouse nightly build.
Use the keymap editor addon to remap the buttons.
So projector accepting 4K/60 4:4:4 should work like my VisioTV, it means 2160p/60fps and 4:4:4 or 4:2:2, right?
Sure.
Try the build that I posted here. 4K/60 4:2:0 should be usable.
I compiled a build with working HDR from Kwiboo 's work-in-progress branch. Tested on a Gemini Lake J4105 and Samsung 4K TV. In order for HDR to work go to Settings-->Player and enable "Allow using DRM PRIME decoder".
I believe this projector's HDMI port is limited to a maximum pixel clock frequency of 300mhz. This means it will only support 4K 50/60hz 4:2:0 8-bit.
4K 4:2:0 does not work on standard X11 builds of LibreELEC. AFAIK it's a limitation of Intel driver and/or X11.
i tried with the command
echo 1 > /sys/module/di/parameters/bypass_all
That's only for Amlogic devices.
So if I understand you right Zotac has DP as 'primary/native' which is the result of the command
and for physical HDMI output it goes via DP to HDMI 2.0 converter.
Yes, Kaby Lake CPUs don't have a native HDMI 2.0 controller, so manufacturers have to use a DP->HDMI 2.0 converter chip.
Would it make sense to buy DP 2 HDMI cable please?
I don't know. If it is some kind of odd HDMI handshake issue between the Zotac and your new TV I guess that cable could in theory fix that.
Do not understand why it says DP1 connected when I have HDMI cable
Because your Zotac use a DP to HDMI 2.0 converter chip.
Intel GPUs took a recent performance hit with their latest security updates...
Only the old Gen7 GPUs. Also, Intel Gen7 Graphics Mitigation Will Try To Avoid Performance Loss In Final Version - Phoronix
I thought s960 is not produced anymore. I guess I was wrong.
I believe "V2" could be the only released version. Or there is only some minor difference between V1 and V2 (like different power supply). I don't think DVBSky s960 was ever released with a new "B" chipset.
How do I get my DVBSky S960 V2 USB up and running?
It works out of the box.