Re: NSTimer causes events to be lost
Re: NSTimer causes events to be lost
- Subject: Re: NSTimer causes events to be lost
- From: Peter Maurer <email@hidden>
- Date: Mon, 21 Mar 2005 08:47:16 +0100
The human eye pretty much craps out at 60fps and 25fps is TV
quality...
I take issue with that last statement. I think that the phosphors in
displays crap out, not the eye. Personally I can tell the difference
between 60 fps and 75 fps quite easily, and 100 fps looks noticeably
better to me as well. I've never seen higher than 120 fps, but at
that rate it really looks liquid. Maybe it helps to be fully
synchronized and frame-accurate as well? :-}
[Sliding badly off list-topic, though of interest to anyone who does
animation or video generation or playback...]
The human eye can see certain features of pictures up to very high
frequency and it's certainly possible for most people to tell the
difference between 80Hz and 100Hz images if the image content is of
the right sort.
Moreover, Shaun might have confused the temporal frequency required for
(i) perceiving fluid motion from an apparent motion stimulus (e.g.,
motion on your computer's display) with the one you need for (ii) not
perceiving flicker. Motion and flicker detection are separate
"channels" of visual processing.
<swank>Maurer, J.P. & Bach, M. (2003) Isolating motion responses in
visual evoked potentials by pre-adapting flicker-sensitive mechanisms.
Experimental Brain Research, 151, 536–541</swank>
In brief, 60 fps are highly sufficient to perceive fluid motion, while
CRT displays should indeed have higher frame rates.
Cheers,
Peter.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden