3 ms·
> it’s a might fine standard for achieving the desired motion blur. Why? You can have nice motion blur in 60fps, what’s special about 24? Why would 24 be more
by dahart 7y ago
> it’s a might fine standard for achieving the desired motion blur.
Why? You can have nice motion blur in 60fps, what’s special about 24? Why would 24 be more desirable than, say, 36fps? And maybe more specifically: your own example demonstrates that it’s your eyes that are blurring, not the image. When you wave your hand around, it’s not blurry, you only see it that way. That suggests that 1000 FPS with no blur should be better than 24fps with a lot of blur, and that you will still perceive 1000fps as motion blurred.
> We don’t want ultra sharp movies, and we don’t want a blurry mess either
Pans in 24fps are an absolute blurry mess no matter what you do. I can’t stand pans in movies anymore. I do want ultra sharp movies with higher frame rates.
> It’s not about what one is “used to” in seeing in cinema either.
I’ve noticed that kids tend to like higher frame rates and don’t find them weird. This seems to indicate it really is about what one is “used to”.
> Higher != better always. Also a reason we don’t get speakers that can push 200 dB (surely better than a puny 100-120 dB right?)
Hahaha! Like I totally agree with the blanket statement that higher is not always better. But 200dB is physically impossible (max air pressure on earth is ~194dB), and if it were would actually make the listener deaf or maybe kill them. https://en.m.wikipedia.org/wiki/Sound_pressure#Examples https://en.m.wikipedia.org/wiki/Sound_pressure#Examples
It’s a bad analogy. In audio, sampling rates and resolution do go higher, and it is considered better. People master audio tracks at 200kHz rather than 20kHz, and they use 24 or 32 bits of resolution rather than 16.