<p>29.97 is the NTSC compromise for 30 fps.  23.976 is the NTSC compromise for 24 fps.  29.976 is a framerate that results from confusing these two numbers into a single bit of nonsense.</p>

<p>The bottom line is that if you have a mix of 29.97fps and 30fps, then every 1000 frames (about every 33 seconds) there's going to be a glitch.  Either you have to double up a frame of the 29.97fps stream to keep up with the 30fps stream, or you have to skip a frame of the 30fps stream so as not to overrun the 29.97fps stream.</p>

<p>If you never have to composite 1000 differently-timed frames in a row, then you can fudge the two as being equal.  But unless you can read the source code of your video editor, you don't really know at what point the program is going to try to "correct" the glitch.  It might be uppity and try to do it half-way through the 1000 sequence to minimize the average divergence, rather than waiting until the divergence is indisputable.  In that case, best to output your generated frames to match the frame rate of the rest of your content.</p>

CC BY-SA 3.0
2015-11-07T21:56:06.487Z
None of those decimals are exact.  The real values are `30/1.001` and `24/1.001`.  (or with integer ratios, `30000/1001`).  They're good enough for almost everything, though: 29.97 is extremely close to `29.97002997`  (with infinite repeating blocks of ...002997), and 23.976 is also very close to `23.976023976`
Peter Cordes
CC BY-SA 4.0
2018-09-13T09:09:39.533Z
Where does the 1001 divisor come from?
xiota
CC BY-SA 3.0
2015-11-03T21:19:44.143Z
2015-11-03T21:19:44.143Z
Michael Tiemann
<p>My live action footage is Frame Rate 29.97 FPS. When exporting frame by frame animation from Photoshop that I intend to composite on top of the live footage. Since I have the ability in Photoshop to specify should I enter 30 FPS or the exact 29.97 FPS?</p>

<p>You can see <em>Jumper and ISO BG.mov</em> is 30 fps</p>

<p><a href="https://i.sstatic.net/TRKGK.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/TRKGK.jpg" alt="Lines for Jumper and ISO Switch"></a></p>

<p>I read this question:</p>

<p><a href="https://video.stackexchange.com/questions/15442/what-is-the-proper-workflow-for-slightly-different-framerates-i-e-30-29-97-2">What is the proper workflow for slightly different framerates, i.e. 30, 29.97, 29.976?</a></p>

<p>But it has conflicting answers and neither one has many upvotes or marked correct. Will there be any difference if I export it with the precise 29.97 and 30 or does it make no difference?</p>

CC BY-SA 3.0
2015-11-03T01:48:04.533Z
What is your target? There is no "one right rate", only what you need it to be. If the majority of your inputs are 29.97, then sticking with that as the project rate, and for PS export, makes sense.
Jim Mack
CC BY-SA 3.0
2015-11-03T01:54:43.090Z
@JimMack Not sure what you mean by target?
Ryan
CC BY-SA 3.0
2015-11-03T09:39:02.077Z
The frame rate of the final output i.e. edited movie
Gyan
<framerate><animation-rendering><compositing>
Is it worth exporting at the exact 29.97 FPS from Photoshop or just use 30 FPS?
Ryan
# Is it worth exporting at the exact 29.97 FPS from Photoshop or just use 30 FPS?

(Asked by: username_0 on 2015-11-02)

My live action footage is Frame Rate 29.97 FPS. When exporting frame by frame animation from Photoshop that I intend to composite on top of the live footage. Since I have the ability in Photoshop to specify should I enter 30 FPS or the exact 29.97 FPS?

You can see *Jumper and ISO BG.mov* is 30 fps

[![Lines for Jumper and ISO Switch](https://i.sstatic.net/TRKGK.jpg)](https://i.sstatic.net/TRKGK.jpg)

I read this question:

[What is the proper workflow for slightly different framerates, i.e. 30, 29.97, 29.976?](https://video.stackexchange.com/questions/15442/what-is-the-proper-workflow-for-slightly-different-framerates-i-e-30-29-97-2)

But it has conflicting answers and neither one has many upvotes or marked correct. Will there be any difference if I export it with the precise 29.97 and 30 or does it make no difference?

**Tags:** framerate, animation-rendering, compositing

> **Comments:**
> **username_1**: What is your target? There is no "one right rate", only what you need it to be. If the majority of your inputs are 29.97, then sticking with that as the project rate, and for PS export, makes sense.  
> **username_0**: @JimMack Not sure what you mean by target?  
> **username_2**: The frame rate of the final output i.e. edited movie  

---

## 1 answers

### Answer by username_3 on 2015-11-03. Score: 1 | Accepted answer

29.97 is the NTSC compromise for 30 fps. 23.976 is the NTSC compromise for 24 fps. 29.976 is a framerate that results from confusing these two numbers into a single bit of nonsense.

The bottom line is that if you have a mix of 29.97fps and 30fps, then every 1000 frames (about every 33 seconds) there's going to be a glitch. Either you have to double up a frame of the 29.97fps stream to keep up with the 30fps stream, or you have to skip a frame of the 30fps stream so as not to overrun the 29.97fps stream.

If you never have to composite 1000 differently-timed frames in a row, then you can fudge the two as being equal. But unless you can read the source code of your video editor, you don't really know at what point the program is going to try to "correct" the glitch. It might be uppity and try to do it half-way through the 1000 sequence to minimize the average divergence, rather than waiting until the divergence is indisputable. In that case, best to output your generated frames to match the frame rate of the rest of your content.

> **Comments:**
> **username_4**: None of those decimals are exact.  The real values are `30/1.001` and `24/1.001`.  (or with integer ratios, `30000/1001`).  They're good enough for almost everything, though: 29.97 is extremely close to `29.97002997`  (with infinite repeating blocks of ...002997), and 23.976 is also very close to `23.976023976`  
> **username_5**: Where does the 1001 divisor come from?  

---

