You are incorrect a bunch of ways. First, as someone else mentions, tv is actually 30 fps, interlaced. so you scan every other line, then the other half of the lines, so the electron beam makes 60 passes a second.
Second, if movies were projected at straight 24 frames per second, you would see lots of flicker. But, film is in a way 48 fps. The light is blocked when the frame is moved into place. after the frame is in place, the light is unblocked. The light is then blocked off again, but the frame is not changed. The process then repeats.
This gives 48 flashes a second, which fools your eyes as far as flicker goes (although, I can see it in scenes with lots of white).
Slashdot Mirror
You are incorrect a bunch of ways. First, as someone else mentions, tv is actually 30 fps, interlaced. so you scan every other line, then the other half of the lines, so the electron beam makes 60 passes a second.
Second, if movies were projected at straight 24 frames per second, you would see lots of flicker. But, film is in a way 48 fps. The light is blocked when the frame is moved into place. after the frame is in place, the light is unblocked. The light is then blocked off again, but the frame is not changed. The process then repeats.
This gives 48 flashes a second, which fools your eyes as far as flicker goes (although, I can see it in scenes with lots of white).
And I really do quote, "'This guy,' he proclaimed, 'is the best at Visual Basic.'" Oh crap, no way man. Visual basic, ph34r his 1337 skillz.
Hmm, Sounds a bit like what happened at a certain university I go to... I wonder if his email included the term "unprecidented" in all caps :)