#ntsc#framerate#colortelevision
Why is TV 29.97 frames per second?
1.3M subscribers • 12 videos on Hallway
- Recommended by 5 people: 4 on Hacker News and 1 on Lobsters.
- A classic. People kept recommending it from 2016 to 2025.
- Presented by Matt Parker, stand-up mathematician
Beginner. No background in the topic needed.
2.1M views10 years ago5 recommendations
Graphics and audioHistory and cultureRenderingHistory of computing
Matt Parker explains the history and mathematics behind the NTSC television standard running at 29.97 frames per second.
I look at the historical quirks which gave us TV at 29.97 frames per second. In North America at least. It's a comfortable 25 fps in Europe. More on that thing I mentioned at the end of the video here: patreon.com/standupmaths Here is the spherical video I was making with Henry Segerman which made me research NTSC frame rates in the first place: youtube.com/watch?v=Yp12c3-IL-I Yes, technically, if you divide 4,500,000 by 286 you get a horizontal frequency of 15,734.26573 lines per second. That matches a frame rate of 29.97002997002997… and so old TVs used 30/1.001 = 29.97002997002997… CORRECTIONS: - A lot of people pointing out that increasing the number of horizontal lines without increasing the bandwidth would be a loss of resolution. Which is a good point. Music by Howard Carter Design by Simon Wright MATT PARKER: Stand-up Mathematician Website: standupmaths.com/ Patreon: patreon.com/standupmaths Nerdy maths toys: mathsgear.co.uk/Why it's here
5 people recommend thisWhat people say. Recommended as a clear and comprehensive explanation of the historical and technical reasons behind the NTSC frame rate.
mikepurvison Hacker News • Recommends
On “My Eight-Year Quest to Digitize 45 Videotapes”
mxfhon Hacker News • Recommends
On “The “432 Hz vs. 440 Hz” conspiracy theory”
santixon Hacker News • Recommends
On “Color Television: NTSC Tutorials”
walkerbrownon Hacker News • Recommends
On “The biggest CRT ever made: Sony's PVM-4300”
djsumdogon Hacker News • Mentions
On “Learn FFmpeg the hard way”