Why 23.976 and not 24 FPS?

Re:Why 23.976 and not 24 FPS? by Dylan16807 on Monday October 10, 2022 @02:43AM (#33148492)

But the timestamp is not recording actual seconds, right? Half the time it's recording intervals of .999 seconds. That is much weirder to handle than merely having the right framerate.

[ Parent | on HN ]

Re:Why 23.976 and not 24 FPS? by klodolph on Monday October 10, 2022 @03:21AM (#33148696)

The time code is always incrementing by one frame at the given frame rate. For any of the NTSC-derived framerates, there are then two ways of incrementing. You can increment as if the frame rate is integral--so after 30 frames at 29.97 fps, your timestamp will show that 1 second has passed. The other option is a "drop-frame" timecode, where you skip over certain numbers when incrementing.

In all cases, the time code increments at the frame rate you are using.

[ Parent | on HN ]