Summary of "yeah... no wonder movies look cheap on new TVs"

Summary of technological concepts & product/feature implications

“Jitter/stutter” on 60Hz TVs for 24fps movies: The video argues that most TVs refresh at 60Hz while most movies are 24fps, so the TV must “fit” 24 movie frames into 60 refresh cycles. This often results in some frames shown for 2 refresh cycles and others for 3, creating micro-stutter/jitter, especially visible during panning shots. The presenter notes this is commonly discussed as jitter/stutter in TV reviews and is not typically caused by bad internet or HDMI cables, but by the TV’s conversion process.
24fps → 60Hz conversion methods (two visual outcomes):
1. 3:2 pulldown / uneven frame hold (“laggy” jittery look): The TV holds frames for different cycle counts (2 vs. 3), producing the stutter.
2. Smoothing / frame interpolation (“buttery smooth” look): Many TVs “invent” intermediate frames to appear smoother. The presenter claims this can create a look that doesn’t match the director’s intended motion characteristics, because the added frames change how motion is rendered.
Director intent vs TV processing: A major theme is that filmmakers deliberately shape motion clarity (including how motion blur looks). The video uses Spielberg’s Saving Private Ryan as the main example, claiming TVs can erase that intent by applying smoothing or the wrong frame-hold strategy.
Frame-rate authenticity in the demo video: The presenter explains that their own video was shot to be switchable between 24fps and 60fps, and encourages viewers to play it at 60fps. The comparison is used to show how TV settings affect motion.
Why the 24fps film “standard” exists (historical + technical reasons):
- Film projectors/cameras expose images frame-by-frame with shutters, and 24fps became a stable convention.
- The presenter describes film’s persistence of vision and projector behavior to justify why certain frame timing historically “worked” visually.
- They also mention film-related practicalities like film length per minute, and audio sync.
A second, deeper motion-related cause: shutter angle / exposure time (cinematic “look”):
- Beyond fps mismatch, the video claims Saving Private Ryan uses a narrower shutter angle (45°) compared to the common 180°, meaning each frame is exposed for a shorter time (roughly ~1/200s vs ~1/48–1/50s typical thinking for 180°).
- Result: less motion blur / more “frozen” crispness, which the presenter argues creates the iconic look of that sequence.
- They connect this to how different shutter speeds can look like “accidentally cinematic” phone footage outdoors (due to automatic exposure changing shutter time).
Higher frame rate formats aren’t “wrong” everywhere (sports/gaming):
- For sports (and potentially gaming), the presenter argues higher fps is beneficial, and TVs with frame blending or higher refresh rates (e.g., 120Hz) can make motion more immersive.
- They state 120Hz is divisible by 24 and 30, reducing the need for harsh conversions.
Potential technical solutions / TV features (actionable checklist-level ideas):
- Use 120Hz TVs with motion/frame blending features for smoother sports.
- Variable Refresh Rate (VRR): some TVs can adjust refresh rate to match 24fps playback (e.g., ~24Hz). The presenter says this may require:
  - a TV that supports VRR,
  - a playback device (e.g., Apple TV) with correct VRR output,
  - an HDMI cable that supports VRR, and
  - enabling the feature in the streaming/player settings.
- The presenter cautions that many TVs may not support the needed VRR behavior.
Personal “review” angle (their content choices matter):
- The creator admits their own channel typically shoots at 24fps for a “film look,” but that YouTube viewing is mostly on 60Hz screens, meaning their own videos likely get the same pull-down/stutter conversions and smoothing artifacts.
- They suggest a possible shift toward 30fps to better align with broadcast standards, while admitting this conflicts with “film snob” preferences.
Extra content/theme: The video briefly mentions other TV controversies and points to another video about a separate controversial TV/streaming feature, but doesn’t detail it in this transcript.

Main speakers/sources (as stated in the subtitles)

The YouTube presenter/host (no specific name given in the subtitles)
Janusz Kaminski (cinematographer referenced for Saving Private Ryan)
Steven Spielberg (director referenced for Saving Private Ryan)
Peter Jackson (referenced regarding The Hobbit HFR choice)
(Example filmmakers referenced): Gladiator, Chicago, Children of Men (no specific individuals named)
BBC / broadcast spec sheets (as a cited source of frame-rate standards)
Genspark (sponsor: AI workspace mentioned; features like Speakley and automation described)