<p>Vegas is not showing you the actual framerate based measurement. Instead, it is showing you 30 fps <a href="https://en.wikipedia.org/wiki/SMPTE_timecode#Drop-frame_timecode" rel="nofollow noreferrer">Drop Frame Timecode</a>, which exists for compatibility reasons and does have to do with NTSC video.</p>

<p>For purposes of alignment with ffmpeg, switch your display to SS.mmm i.e. fractional seconds rather than SMPTE timecode. No need to change the project framerate.</p>

<p>Right click on one of the times at the top of the timeline and you will see that SMPTE Drop is selected. You can change that to "Time" or "Seconds" for a convention that FFmpeg will naturally understand.</p>

<p><a href="https://i.sstatic.net/4y2ju.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/4y2ju.png" alt="Change Vegas Pro timeline timecode display"></a></p>

CC BY-SA 4.0
2019-05-10T19:04:48.263Z
2019-05-11T04:59:25.943Z
2019-05-11T04:59:25.943Z
Gyan
<p>I found the weirdest thing in Vegas Pro 13. I was trying to verify the exact frames of a generated file, so was looking for a zero number frame to drop it into the timeline. I was surprised to find that two frames in the Vegas Pro timeline are missing. The timeline goes from <code>00:13:59;29</code> to <code>00:14:00;02</code>. There should be a <code>;00</code> and <code>;01</code> entry there as well, but it's not present. See in the image below, zoomed in so that each vertical line is a frame. The two frames missing are between the blue line.</p>

<p><a href="https://i.sstatic.net/fvpnE.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/fvpnE.png" alt="Missing frames in Vegas Pro timeline"></a></p>

<p>My first thought was something to do with NTSC 29.97 framerate vs actual 30 framerate. I figured if that's the case, the issue should repeat at regular intervals. I checked between other values and determined that the issue repeats every minute, except at 10 minute marks (it may be more nuanced than that).</p>

<p>How can I make it not do this?</p>

<hr>

<p>Why, you ask? I edit in Vegas Pro like any other vidiot, but then I use the events window to extract all the timeline data then render in ffmpeg. This means that If I try to target a specific frame, I may actually be off by several frames. This is an issue because some of my process is creating separate video and audio files, but they play simultaneously, so I can't tolerate more than 1 frame off for the lip sync.</p>

<p>My thought is that I need to record in true 30 fps, then everything will fall in line. Is that the only solution? How can I account for this in my ffmpeg scripts? For example, if I see <code>00:14:00;02</code> in Vegas Pro, do I need to tell ffmpeg that the actual frame to target is less than that? If I have a 10 hour clip, 2 frames difference every minute adds up to a lot of frames. Almost a minute! I haven't looked closely at any of my renders to see if I notice a subjective lip sync issue.</p>

<framerate><vegas-pro>
Why are there missing frames in the Vegas Pro editing timeline?
user3643
# Why are there missing frames in the Vegas Pro editing timeline?

(Asked by: username_0 on 2019-05-10)

I found the weirdest thing in Vegas Pro 13. I was trying to verify the exact frames of a generated file, so was looking for a zero number frame to drop it into the timeline. I was surprised to find that two frames in the Vegas Pro timeline are missing. The timeline goes from `00:13:59;29` to `00:14:00;02`. There should be a `;00` and `;01` entry there as well, but it's not present. See in the image below, zoomed in so that each vertical line is a frame. The two frames missing are between the blue line.

[![Missing frames in Vegas Pro timeline](https://i.sstatic.net/fvpnE.png)](https://i.sstatic.net/fvpnE.png)

My first thought was something to do with NTSC 29.97 framerate vs actual 30 framerate. I figured if that's the case, the issue should repeat at regular intervals. I checked between other values and determined that the issue repeats every minute, except at 10 minute marks (it may be more nuanced than that).

How can I make it not do this?

---

Why, you ask? I edit in Vegas Pro like any other vidiot, but then I use the events window to extract all the timeline data then render in ffmpeg. This means that If I try to target a specific frame, I may actually be off by several frames. This is an issue because some of my process is creating separate video and audio files, but they play simultaneously, so I can't tolerate more than 1 frame off for the lip sync.

My thought is that I need to record in true 30 fps, then everything will fall in line. Is that the only solution? How can I account for this in my ffmpeg scripts? For example, if I see `00:14:00;02` in Vegas Pro, do I need to tell ffmpeg that the actual frame to target is less than that? If I have a 10 hour clip, 2 frames difference every minute adds up to a lot of frames. Almost a minute! I haven't looked closely at any of my renders to see if I notice a subjective lip sync issue.

**Tags:** framerate, vegas-pro


---

## 1 answers

### Answer by username_1 on 2019-05-10. Score: 1 | Accepted answer

Vegas is not showing you the actual framerate based measurement. Instead, it is showing you 30 fps [Drop Frame Timecode](https://en.wikipedia.org/wiki/SMPTE_timecode#Drop-frame_timecode), which exists for compatibility reasons and does have to do with NTSC video.

For purposes of alignment with ffmpeg, switch your display to SS.mmm i.e. fractional seconds rather than SMPTE timecode. No need to change the project framerate.

Right click on one of the times at the top of the timeline and you will see that SMPTE Drop is selected. You can change that to "Time" or "Seconds" for a convention that FFmpeg will naturally understand.

[![Change Vegas Pro timeline timecode display](https://i.sstatic.net/4y2ju.png)](https://i.sstatic.net/4y2ju.png)


---

