Two ports at once have been used for Samsung’s 5120x1440 240hz monitors. Each port refreshes half of the screen and there are two scanlines going from left to right. Using the calc here you might be able to use two DP2.1 UHBR80 cables with DSC and nonstandard timings to run 4k 1000hz 10bit.
Not really? Modern hardware gets almost 1000 fps in rocket league. You don’t need exactly 1000 to get a benefit, even getting 800 fps will give you a smoother experience
Here’s a real-world use case where this difference is noticeable to the average person. We don’t need to render video games at 1000 Hz, but many things that can be rendered with comparatively low GPU power could be made a better experience with it. The real question is whether/when the technology becomes cheap enough to be practical to use in consumer goods.
90hz is enough to prevent motion sickness in vr. That’s a frame per 11ms and that’s basically the limit of human perception. 120 is allegedly even better, but beyond that there’s no point. Yeah we’re rehashing the 30 vs 60 fps debate again but this time for reals.
Latency between your input and computer output. It might not be that noticeable on PCs with keyboards and mice, but my god latency is awful on touch screens! Even the fastest screens in mobile phones are slow AF. 1,000Hz is a must for touch screens.
Refresh rate isn’t inherently tied to response time. We already have 1ms response time monitors that aren’t 1000hz. It just takes that long for the monitor to display the signal it’s receiving.
It is though. 1ms response time for monitors is the time they need to switch pixel colour. But if it runs at 100Hz you are getting at least 10ms delay between your action and what the screen is showing. In practice it’s even larger.
I’m sure some people will demand it. But for 99.9% of the population you don’t need 1000Hz content. The main benefit is that whatever framerate your content is it will not have notable delay from the display refresh rate.
For example if you are watching 60Hz video on a 100Hz monitor you will get bad frame pacing. But on a 1000Hz monitor even though it isn’t perfectly divisible. the 1/3ms delay isn’t perceptible.
VRR can help a lot here, but can fall apart if you have different content at different frame rates. For example a notification pops up and a frame is rendered but then your game finishes its frame and needs to wait until the next refresh cycle. Ideally the compositor would have waited for the game frame before flushing the notification but it doesn’t really know how long the game will take to render the next frame.
So really you just need your GPU to be able to composite at 1000Hz, you probably don’t need your game to render at 1000Hz. It isn’t really going to make much difference.
Basically at this point faster refresh rates just improve frame pacing when multiple things are on screen. Much like VRR does for single sources.
Here’s a big part of why they want 1000Hz. You don’t need to fully re-render each frame for most cases where 1ms latency is desirable - make a 100 Hz (or even 50 Hz) background and then render a transparent layer over it.
“Now wait for 1,000 Hz content and capable GPUs.”
Forget the content and GPU, you need an input port capable of that.
HDMI 2.1 and Display Port 1.4 cap out at, what? 240?
With DSC DP 1.4 can do 4k 360 but it still ain’t close to 1000
So you just need 3 4090’s with 1 displayport each to the monitor and a whole new version of sli.
… I actually wonder if the graphics cards could multiplex across multiple dp to a single display.
I vaguely remember that being a thing for early commercial 8k projectors, but I don’t know anything about the implementation.
Two ports at once have been used for Samsung’s 5120x1440 240hz monitors. Each port refreshes half of the screen and there are two scanlines going from left to right. Using the calc here you might be able to use two DP2.1 UHBR80 cables with DSC and nonstandard timings to run 4k 1000hz 10bit.
Ez
Isn’t 4k 360hz equivalent to 1080p 1440hz? I wouldn’t expect 1000hz at 4k any time soon but 1080p in competitive FPS is easy
I think so? Honestly not sure how the math works on that one.
If you want 1000fps, 4k and DP are the least of your problems
Not really? Modern hardware gets almost 1000 fps in rocket league. You don’t need exactly 1000 to get a benefit, even getting 800 fps will give you a smoother experience
Easy, just connect 4 cables!
Now wait for humans who can see the difference
Here’s a real-world use case where this difference is noticeable to the average person. We don’t need to render video games at 1000 Hz, but many things that can be rendered with comparatively low GPU power could be made a better experience with it. The real question is whether/when the technology becomes cheap enough to be practical to use in consumer goods.
Here is an alternative Piped link(s):
Here’s a real-world use case where this difference is noticeable to the average person
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
90hz is enough to prevent motion sickness in vr. That’s a frame per 11ms and that’s basically the limit of human perception. 120 is allegedly even better, but beyond that there’s no point. Yeah we’re rehashing the 30 vs 60 fps debate again but this time for reals.
It’s not about the perception of an image, it’s about latency.
Latency between frames? Or latency to the screen? We have low latency monitors already.
Latency between your input and computer output. It might not be that noticeable on PCs with keyboards and mice, but my god latency is awful on touch screens! Even the fastest screens in mobile phones are slow AF. 1,000Hz is a must for touch screens.
Refresh rate isn’t inherently tied to response time. We already have 1ms response time monitors that aren’t 1000hz. It just takes that long for the monitor to display the signal it’s receiving.
It is though. 1ms response time for monitors is the time they need to switch pixel colour. But if it runs at 100Hz you are getting at least 10ms delay between your action and what the screen is showing. In practice it’s even larger.
I’m sure some people will demand it. But for 99.9% of the population you don’t need 1000Hz content. The main benefit is that whatever framerate your content is it will not have notable delay from the display refresh rate.
For example if you are watching 60Hz video on a 100Hz monitor you will get bad frame pacing. But on a 1000Hz monitor even though it isn’t perfectly divisible. the 1/3ms delay isn’t perceptible.
VRR can help a lot here, but can fall apart if you have different content at different frame rates. For example a notification pops up and a frame is rendered but then your game finishes its frame and needs to wait until the next refresh cycle. Ideally the compositor would have waited for the game frame before flushing the notification but it doesn’t really know how long the game will take to render the next frame.
So really you just need your GPU to be able to composite at 1000Hz, you probably don’t need your game to render at 1000Hz. It isn’t really going to make much difference.
Basically at this point faster refresh rates just improve frame pacing when multiple things are on screen. Much like VRR does for single sources.
Here’s a big part of why they want 1000Hz. You don’t need to fully re-render each frame for most cases where 1ms latency is desirable - make a 100 Hz (or even 50 Hz) background and then render a transparent layer over it.
Here is an alternative Piped link(s):
Here’s a big part of why they want 1000Hz
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.