Timecode Doesn't Match

doubleJ wrote on 9/7/2018, 8:46 AM

Hello...
With my big "put timecode in my files" project, I found some irregularities.
I started out conforming all my videos to 30fps using 00:00:00:00 timecode.
Then, I realized that bulk of my sources were 29.97 (or, at least, closer to 29.97 than 30), so I used 29.97 and 00:00:00:00 timecode.
Then, I realized that NLEs (Vegas Pro and Premiere Pro) were showing the length longer than the actual length.
Finally, I realized that I needed to encode at 29.97 and use 00:00:00;00 (semicolon).

So, all of my footage should be matching framerates and timecode formats.
Premiere Pro shows everything correctly.

But, Vegas Pro has multiple problems.

The file properties show that the first clip should be 37 minutes and 26 seconds.

Vegas Pro is showing 37 minutes and 24 seconds.

Also, the timecode should be formatted 00:00:00;00 (semicolon).
Not only is the file's timecode in drop-frame, but the project's settings are for drop-frame.

Finally, the timecode should match the timestamp in the filename (my script used the same date/time information for all variables).
It's as though Vegas Pro is interpreting the framerate or the timecode incorrectly.

Is this a bug, am I doing something incorrectly, or what?
My brain works in 30p and 00:00:00.00 format, so I'm still getting a grasp on 29.97.
I think I did everything correctly, though.
Hehehe...
JJ

 

 

 

 

Comments

Former user wrote on 9/7/2018, 10:32 AM

The length difference you are seeing is the difference between non-drop math and drop math. Premiere is reading it as drop frame (actual time) and Vegas is reading it as non-drop.

doubleJ wrote on 9/7/2018, 5:52 PM

The length difference you are seeing is the difference between non-drop math and drop math. Premiere is reading it as drop frame (actual time) and Vegas is reading it as non-drop.

But why is Vegas reading it as non-drop?

JJ

Tim L wrote on 9/7/2018, 11:19 PM

In your Vegas screenshot, the medial pool details have it wrong (37:23:28) but the "Video" details at the bottom of the window have it right (37:26;06).

Each clip can have customized timecode details.  Right click on the clip's filename, select properties, and check out the "Media" tab.  Is it set for 29.970 and "SMPTE Drop"?

doubleJ wrote on 9/8/2018, 9:16 PM

In your Vegas screenshot, the medial pool details have it wrong (37:23:28) but the "Video" details at the bottom of the window have it right (37:26;06).

Each clip can have customized timecode details.  Right click on the clip's filename, select properties, and check out the "Media" tab.  Is it set for 29.970 and "SMPTE Drop"?

The file's properties are set to the file's timecode (which should be drop-frame).

The project's properties are set to 29.97 and drop-frame.

If I select multiple files (all or just videos), the option to specify custom timecode is greyed out.
JJ

doubleJ wrote on 9/8/2018, 9:21 PM

Interestingly enough...
When I did the custom timecode, changed to drop-frame, clicked ok, then changed back to the file's timecode, everything is the way it should have been to begin with.

I seriously hope I don't have to go through all my videos (395) and correct what should already be correct.
JJ

doubleJ wrote on 9/8/2018, 9:26 PM

At least it doesn't seem to affect the timeline.
I changed one file and didn't change the other.
Both files seem to end at the correct place, on the timeline, even though the length is incorrect, on the second one.
It may just be a visual error, but it seems like a fairly large one.
JJ