this post was submitted on 19 May 2024
121 points (93.5% liked)

Technology

34982 readers
179 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] kevincox@lemmy.ml 4 points 6 months ago (1 children)

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.

[–] lengau@midwest.social 6 points 6 months ago (1 children)

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.

[–] PipedLinkBot@feddit.rocks 1 points 6 months ago

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.