DisplayPort and HDMI: In this article we'll point out the differences between the two interfaces, how the choice of monitor fits into this, and why GPU vendors seem to prefer DisplayPort over HDMI.
DisplayPort and HDMI: In this article we'll point out the differences between the two interfaces, how the choice of monitor fits into this, and why GPU vendors seem to prefer DisplayPort over HDMI.
No, but HDMI splitters are very cheap: https://www.amazon.com/s?k=HDMI+spl...prefix=hdmi+splitter,aps,234&ref=nb_sb_noss_1The article fails to mention that DisplayPort also supports daisy chaining for multiple monitors, which HDMI does not.
A splitter doesn't allow daisy chaining; it only allows you to duplicate the same signal onto a second monitorNo, but HDMI splitters are very cheap
That's a good point and the only reason why I skipped multiple monitoring configurations is that it's not something that's usually associated with high refresh rate gaming. Of course, with new monitors typically supporting high refresh rates and motorsport/flight sim rigs often containing two or three monitors, it's valid that it should be in the article. I'll add it as soon as I can.The article fails to mention that DisplayPort also supports daisy chaining for multiple monitors, which HDMI does not.
What graphics card and monitor do you have? As noted in the article, some monitors only support their advertised refresh rate using DP.HDMI doesn't let me run 170Hz on my monitor at 1440p, just 144Hz max. Is that some HDMI limitation or do I just need a better cable? The one I use is what I got in the package with the monitor. DisplayPort lets me run 170Hz no problem and that's what I'm using.
GeForce RTX 30 series has DP 2.0 and HDMI 2.1, so there's no reason for the 40 series to not have DP 2.0 - it's monitors that don't have it.And DisplayPort 2.0 is now on the shelf for Fairy Tales, next to stories about super batteries, flux capacitors and alike.
The rumor has, RTX 4xxx won't have DP 2.0 either. Such a disgrace!
Gigabyte M27Q, RX 6700 XTThat's a good point and the only reason why I skipped multiple monitoring configurations is that it's not something that's usually associated with high refresh rate gaming. Of course, with new monitors typically supporting high refresh rates and motorsport/flight sim rigs often containing two or three monitors, it's valid that it should be in the article. I'll add it as soon as I can.
What graphics card and monitor do you have? As noted in the article, some monitors only support their advertised refresh rate using DP.
GeForce RTX 30 series has DP 2.0 and HDMI 2.1, so there's no reason for the 40 series to not have DP 2.0 - it's monitors that don't have it.
Just checked the manual for the M27Q and 1440p 144 Hz is supported over HDMI 2.0 - interestingly, the monitor only has a DP 1.2 port, although that is good enough for that resolution and refresh rate without compression. The culprit would seem to be your cable.Gigabyte M27Q, RX 6700 XT
60 Hz at 4K isn't really a high refresh rate anymore, though.This is what I use and I get the full 60Hz at 4K
Well, since most displays are still 60Hz and 4K or less, it means that this cable would easily cover over 95% of the market for gaming and 100% for televisions. I'd say that's pretty damn good for something sold at a dollar store!60 Hz at 4K isn't really a high refresh rate anymore, though.
That's all I was saying. I was pointing it out because for most people, the expensive stuff is irrelevant and they're better off putting money towards things that will matter. Although, if you have some halo-level display, then it matters. Of course, if you have a halo-level display, money's not an issue either.*Coughs and points at the article title, specifically the bit that says "What's best for high refresh rate gaming"
Naturally if one doesn't need/desire more than 60 Hz, HDMI 2.0 is more than good enough for anything, and even el-cheapo cables will do.
If you watch Netflix, Amazon, Hulu, etc. on Windows and want to see it in greater than 720p, you'll need to run an HDMI cable at least once (and to use Edge, and to install Microsoft's HEVC codec.) I'm not sure what this "magic handshake" that can only happen over HDMI is exactly, but once it's been accomplished between a given display and computer/gpu, you can go back to a DP cable between them if you want.
Not knowing this little tidbit cost me a couple hours one night a while back...
The thing is DP is supposed to support HDCP, and the various status checks (I.e., nvidia control panel) indicated HDCP was working. Still, Netflix would not go over 720p until I switched to HDMI, which displayed the very same HDCP working status, but this time actually worked. I suspect this may be a widevine implementation issue in terms of how it checks for HDCP vs. a fundamental limitation in the cable?That would be the HDCP (High Definition Content Protection) handshake so if any part of the handshake does not support HDCP you'll not get the full HD/multi channel audio experience it will just be 1280x720p / stereo audio. HDCP is easy to get around nowadays as you've discovered but don't look for it to last it can request another handshake at anytime which means you'll have to do your cable switcharoo once again