Answers.Body: <p>It only looks like 24fps at first glance.  From the <a href="https://en.wikipedia.org/wiki/SMPTE_timecode" rel="nofollow noreferrer">Wikipedia entry</a> on SMTPE timecode, the section on drop-frame:</p>
  <p>“In order to make an hour of timecode match an hour on the clock, drop-frame timecode skips frame numbers 0 and 1 of the first second of every minute, except when the number of minutes is divisible by ten.”</p>
  <p>Check the first and second frame of each minute.</p>
  <p>A clue that timecode is using drop-frame is when the separator before the frame number is a semicolon instead of a colon, although I’ve seen software ignore this convention.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-07-02T21:54:48.190Z
Answers.LastActivityDate: 2022-07-02T21:54:48.190Z
Answers.UserDisplayName: Jason Conrad
Body: <p>I'm having a hard time understanding how non-integer frame rates are implemented in h264 and hevc.  For example, I just stepped through a 23.976fps video frame by frame using Shotcut, and looking at the timestamp of each frame, it looks like there are full 24 frames in each second.</p>
  <p>How do they do it?  Do the encoders actually write 24 full frames per second to file? (What even would be a non-full frame?)  But that would mean, when playing at 23.976, that to play 1000 seconds you need to render 23976 frames.  But the file contains 24000 frames (does it?)  Do they just drop some frames?  Who does the dropping?  The player?  Or does the encoder drop a frame every n seconds?</p>
  
Tags: <encoding><framerate><h.264><hevc>
Title: h264/hevc: non-integer frame rates
UserDisplayName: ACz
ThreadText: # h264/hevc: non-integer frame rates
  
  (Asked by: username_0 on 2022-07-02)
  
  I'm having a hard time understanding how non-integer frame rates are implemented in h264 and hevc. For example, I just stepped through a 23.976fps video frame by frame using Shotcut, and looking at the timestamp of each frame, it looks like there are full 24 frames in each second.
  
  How do they do it? Do the encoders actually write 24 full frames per second to file? (What even would be a non-full frame?) But that would mean, when playing at 23.976, that to play 1000 seconds you need to render 23976 frames. But the file contains 24000 frames (does it?) Do they just drop some frames? Who does the dropping? The player? Or does the encoder drop a frame every n seconds?
  
  **Tags:** encoding, framerate, h.264, hevc
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-07-02. Score: 1 | Accepted answer
  
  It only looks like 24fps at first glance. From the [Wikipedia entry](https://en.wikipedia.org/wiki/SMPTE_timecode) on SMTPE timecode, the section on drop-frame:
  
  “In order to make an hour of timecode match an hour on the clock, drop-frame timecode skips frame numbers 0 and 1 of the first second of every minute, except when the number of minutes is divisible by ten.”
  
  Check the first and second frame of each minute.
  
  A clue that timecode is using drop-frame is when the separator before the frame number is a semicolon instead of a colon, although I’ve seen software ignore this convention.
  
  
  ---
  
  