this post was submitted on 29 Feb 2024
399 points (98.8% liked)
Open Source
31114 readers
1 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Me neither. I play at 1440p/120hz. Both cables can manage that resolution and frame rate.
The only difference I get is when I use DisplayPort and leave my computer alone for 20 mins, the GPU goes to sleep and the monitor won't display anything although I hear background apps/games running.
Without changing any settings, using a HDMI cable solved that.
HDMI it is.
its starts i matter more when you do more exotic connections. display port is more friendly for merging it into another form factor, and between the two, the only one capable of tech like daisy chaining monitors.
hdmi also requires a licensing fee to use, which technically add a cost to the end user.
In a multi monitor set up, when a screen connected to display port goes to sleep my computer treats it like that screen was disconnected - meaning all my open applications get shoved from one screen to another. I've also used HDMI to avoid that.
Ugh, so THAT'S why it happens? It's quite irritating, and only rebooting seems to fix it.
Even if HDMI manages the same framerate it will still have a higher latency.