Displays: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
* With long HDMI cables (~8 meters), it can be impossible to have a 4k signal at 60Hz transmitted correctly (I had pixel artefacts all over the picture). You really need a premium, high quality recent cable for such purposes (usually these cables are optical or active cables and cost much more). They are also directional and not bi-directional. | * With long HDMI cables (~8 meters), it can be impossible to have a 4k signal at 60Hz transmitted correctly (I had pixel artefacts all over the picture). You really need a premium, high quality recent cable for such purposes (usually these cables are optical or active cables and cost much more). They are also directional and not bi-directional. | ||
* Note that long cables cannot be certified with an official HDMI certification (such as Ultra High Speed, with 48 Gbps bandwidth). The official HDMI certification stops at around 3 meters. Thus you have to find a vendor at random that does provide such cables with a high enough bandwidth, so that they work correctly. | * Note that long cables cannot be certified with an official HDMI certification (such as Ultra High Speed, with 48 Gbps bandwidth). The official HDMI certification stops at around 3 meters. Thus you have to find a vendor at random that does provide such cables with a high enough bandwidth, so that they work correctly. | ||
= DisplayPort = | |||
* DisplayPort seems better than HDMI for connecting a PC GPU to a monitor. I've ran into a lot of issues with HDMI - in particular, the screen would not wake up after sleeping, or it would take a long time to activate when the PC starts or reboots. | |||
* DisplayPort 2.1 is only needed if you want to go beyond a 4K resolution at 144Hz, else DisplayPort 1.4 is enough. In that case you need a GPU, screen and cable that all support DP 2.1. | |||
* If you are using DP 1.4, it's better to select 1.4 as the DP version in your monitor as well if you have the option. With my Gigabyte Aorus FO32U2P, the screen would constantly go black randomly for 1-2 seconds (before reactivating) until I switched to 1.4. | |||
= USB Type C = | = USB Type C = | ||
Latest revision as of 20:27, 28 October 2025
Firmware Updates
- Modern displays usually have firmware that can be updated. It's important to run these updates, especially if you're having issues. For instance, I had an important issue between one monitor and an nVidia RTX 3080 Ti card, when screen remained black at boot. The issue was fixed by a firmware update.
Suspending & Waking up
- I had an issue with a ViewSonic monitor connected to an HDMI matrix where the display would not wake up after sleep. I had to turn off and on the monitor to get the display back. It was fixed completely by turning off in the monitor's settings the option "Auto-Detect".
Screen Tearing
- On modern hardware there seems to be many options to remove screen tearing entirely:
- HDMI starting with version 2.1 has an extension called VRR (Variable Refresh Rate) that seems to take care of the problem. But this requires both an HDMI 2.1 capable monitor and an HDMI video card (only very recent nvidia cards from 2020 have that).
- AMD has FreeSync but it requires an AMD card (Radeon).
- Nvidia has G-sync but is quite useless as it needs a monitor supporting G-sync. Almost no monitor does because G-sync require a special hardware module, whereas they all support FreeSync since FreeSync is free.
- Nvidia finally started supporting FreeSync on most monitors but it requires a DisplayPort cable since in fact it uses a DisplayPort technology for VRR (whereas AMD cards can do it over HDMI, even without HDMI 2.1). Nvidia probably won't add support for FreeSync over HDMI 2.0 and lower (see for instance https://www.nvidia.com/en-us/geforce/forums/discover/292013/freesync-with-hdmi/).
- For HDMI TVs, no solution except HDMI 2.1.
- If you cannot use a hardware solution (mostly it means using an nvidia card connected to a monitor by HDMI), you have to resort to software Vertical Sync. See for instance this article for screen tearing / vertical sync on KDE.
Tearing on specific applications
- On SMPlayer (with mpv multimedia engine) with an Intel integrated GPU, screen tearing happened while using the libmpv pr gpu video outputs, but not with xv (Intel Textured Video).
Testing Screen Tearing
- This is a good URL for checking screen tearing in Chromium: https://www.youtube.com/watch?v=DaBQ3hCJxpE.
- Moving around windows very quickly is also an efficient way of testing tearing on the desktop environment.
- There are also downloadable movies for checking movie players (available for instance at http://silverlinux.blogspot.com/2013/05/vsync-test-videos.html).
HDMI
- With long HDMI cables (~8 meters), it can be impossible to have a 4k signal at 60Hz transmitted correctly (I had pixel artefacts all over the picture). You really need a premium, high quality recent cable for such purposes (usually these cables are optical or active cables and cost much more). They are also directional and not bi-directional.
- Note that long cables cannot be certified with an official HDMI certification (such as Ultra High Speed, with 48 Gbps bandwidth). The official HDMI certification stops at around 3 meters. Thus you have to find a vendor at random that does provide such cables with a high enough bandwidth, so that they work correctly.
DisplayPort
- DisplayPort seems better than HDMI for connecting a PC GPU to a monitor. I've ran into a lot of issues with HDMI - in particular, the screen would not wake up after sleeping, or it would take a long time to activate when the PC starts or reboots.
- DisplayPort 2.1 is only needed if you want to go beyond a 4K resolution at 144Hz, else DisplayPort 1.4 is enough. In that case you need a GPU, screen and cable that all support DP 2.1.
- If you are using DP 1.4, it's better to select 1.4 as the DP version in your monitor as well if you have the option. With my Gigabyte Aorus FO32U2P, the screen would constantly go black randomly for 1-2 seconds (before reactivating) until I switched to 1.4.
USB Type C
- Now USB-C cables can carry video (DisplayPort Alt Mode). However this can be problematic in some cases if you only want to use USB-C to carry data. For instance, on my Gigabyte Aorus FO32U2P monitor, I connected the HDMI-1 port to the nvidia 3080 Ti card, and the USB-C port to the USB-C port of the PC. However, the display then used the USB-C connection for video (from the iGPU of the AMD Ryzen 9700X), and did not use the HDMI output. Explicitely turning off the AMD / USB-C output in Windows worked, but then the USB-C port was not used at all (the mouse connected to a screen USB-B port would not work).
- I did not find any option in the screen to make my setup work, so I ended up dumping the USB-C connection and used an USB-B cable. This was a bit disappointing. Note that I tried this only on Windows, not on Linux.