4 ms·
Wait, why should we care about 120hz? It seems like 60hz should be good enough for people who aren't professional gamers? I wonder how much battery life could
by skybrian 8y ago
Wait, why should we care about 120hz? It seems like 60hz should be good enough for people who aren't professional gamers?
I wonder how much battery life could be saved by turning the refresh rate down to 30hz?
- minimaxir 8y agoIf you haven’t tried an iPad Pro that can display 120fps, I recommend you do. It makes a surprising difference.
- bitpush 8y ago+1. This, and "640K ought to be enough for anybody"
- nixpulvis 8y agoThere is an important distinction between a phonomonan that stops being detectable at high enough values (to humans), and the size of memory for a computer system.
- gpm 8y agoI think VR has sufficiently demonstrated that > 60fps is easily detectable by the vast majority of humans.
- jcelerier 8y ago> high enough values (to humans), and we know experimentally that for humans, "high enough values" > 500Hz https://www.quora.com/What-is-the-highest-frame-rate-fps-that-can-be-recognized-by-human-perception-At-what-rate-do-we-essentially-stop-noticing-the-difference https://www.quora.com/What-is-the-highest-frame-rate-fps-tha...
- jug 8y agoIt was shown that a system won’t even rum with 640K, so this (disputed) quote became an example of shortsightedness in tech. However, a system does not need to meet the maximum detectable frame rate of the human eye to be usable, or even close to it. There is a difference in use, yes, but a mere luxury. That’s why I think this comparison doesn’t hold.
- jcelerier 8y ago> However, a system does not need to meet the maximum detectable frame rate of the human eye to be usable, or even close to it. for me it's really the same thing. It's physically painful to go back to 60hz screens after getting used to 120hz, just like it would be to go back to 640k systems, even if I have used 60Hz screens for many years and my first computer only had a 5 1⁄4 drive and no disk - and back then I managed just fine (though I was quite young :p).
- zozbot123 8y ago60hz may indeed be enough, but in general, touch-friendly UI needs tight bounds on latency to user input (which may be a problem with a mere 30hz). Every "drag"- or "swipe"-like interaction on a touch UI is basically the UX equivalent to moving a mouse pointer - something that has used a hardware-accelerated sprite since forever, precisely in order to put a tight bound on max latency!
- jcelerier 8y agojust having the mouse cursor at 120 hz is striking
- rkangel 8y agoIt only renders on vsync, so if you screen can only do 60Hz (which I believe is most) it'll never be more than 60Hz. Also,if nothing is moving, then its 0Hz.
- izacus 8y agoPretty much all better mobile devices (laptops, tablets and mobile phones) use adaptive refresh, where new frames are only sent to the screen when an actual update has happened. So looking at still image on your phone will not cause 60Hz refresh cycles. Having said that - 120Hz updates when things are moving are noticably smoother than 60Hz updates. You can see this on modern iPads.
- aphextron 8y ago>Wait, why should we care about 120hz? It seems like 60hz should be good enough for people who aren't professional gamers? Fuchsia is being developed with AR/VR in mind from the OS level on up. The target for UI animation has to be way higher than 60FPS to accommodate that.
- ghusbands 8y agoThe most obvious difference for most people is to how readable text is while it is moving, and how fast it can move while still being readable. For touch interfaces, this is important, as people do read while pushing things around. In essence, anything above a pixel per frame is not very readable. So at 30fps, text is only readable when moving at less than 30 pixels per second (60 for hi-DPI). At 120fps, you can move everything four times faster and still have it look sharp. You could expand your knowledge greatly by visiting blur busters [1]. It is trivial for humans and cameras to see the difference between 60Hz and 120Hz motion [2], especially when tracking motion. When we were all on CRTs, the difference was much less noticeable, give or take flicker sensitivity, because they display things in pulses. Most modern displays will hold the image until it changes, which any tracking visual system (eyes or camera) will see as smearing. You can see images of this at blur busters. A lot of often-cited sufficient-for-everything frame rates are incorrect. 24fps is claimed to be sufficient for motion for cinemas, but it only works with heavy motion blur and a lack of fast camera sweeps. 30fps is claimed to be sufficient for games, but it impacts reaction times, input lag and blur in motion. 60fps is claimed to be sufficient for games, next, but it stopped being so when we stopped using CRTs (visit blur busters for more detail). We're now at 120fps for many things and it's almost good enough. [1] https://www.blurbusters.com/ https://www.blurbusters.com/ [2] https://www.blurbusters.com/faq/60vs120vslb/ https://www.blurbusters.com/faq/60vs120vslb/
- skybrian 8y agoThis is good information, but to quibble, "noticeable" does not mean "not good enough". Being able to notice a difference doesn't mean it matters to the user; that's more subjective and both versions might be considered fine by many users. For example, I'd be surprised if most users would care about reading text while moving it quickly. (Well, maybe they would care with sufficient advertising?)