Originally Posted by mdrejhon
Doesn't stop me from trying.
Been mythbusting "humans can't tell 30fps from 60fps" since 1993. (MOTION.ZIP -- MS-DOS QuickBasic source code
The world is slightly more educated now in motion blur science. Not always by a huge amount, but far more so than 1993. And few believed in my Arduino scanning backlight
from mid-2012, long before LightBoost 2D was "discovered" en-masse. For those wondering, I've actually published my strobe backlight research here
. And now, the small boom of post-LightBoost-era low-persistence LCD's is beginning (EIZO Turbo240 in FG2421, BENQ Blur Reduction in XL2720Z
, and G-SYNC's optional strobe mode). Truly CRT-motion-clarity LCD's are no longer pie in the sky anymore. But the journey doesn't end here; strobing is a motion blur band-aid because we cannot achieve low-persistence with continuous light yet; doing so with today's technology still requires light modulation (aka strobing / phosphor decay / laser scanning). 0ms GtG doesn't equal "low persistence", but not everyone understands the difference between transitions (GtG) and persistence (static pixel state creating motion blur)
Thank you for your work, btw