| HDMI is a pain in different ways, and these are just examples in my house. Keeping track of version 1-2.2b has become a small chore. Perhaps it is time I burn it all down to claim insurance and start over. As soon as you go past 1080p@60Hz, as you pointed out, you can't just grab any cable. I suffered a great deal from this moving to 4K screens. Sparkles, drops, and black screens are usually a connection problem. Some smarter device/driver combos will work around a bad connection by dropping colour information to fit into the available bandwidth, some won't. I have one 4K display where HDMI 1 is, well, HDMI version 1. HDMI 2 (as in the second port) is HDMI version 2 and will actually display 4K@60Hz. I have TVs that need fiddling to get the proper native resolution and framerate. Some need game or PC mode to disable overscan and show the whole image. Currently on my desktop connected to a 4K TV, if I try to set a game to 1920x1080, the driver seems to pick something strange and I get no image at all. I'm not sure who to blame here. I still have devices that won't do 4K@60Hz, they're limited to 30Hz. It's a device limitation, fine. A Raspberry Pi 4 will output 4K@60Hz but not by default. You have to enable it in the firmware config. |