23.98 time code window burn issue

[Phil Glau]

I’m showing the same flaw as Elijah indicates:

Source footage is 23.98 on a self contained MOV file with QT metadata timecode.

Take that footage into Compressor and use the Timecode overlay and the resulting file with the TC burn-in does not match the timecode embedded in the original source file.

For example:

First Frame of Source file: 12:38:05:11
First Frame as represented by the Burn-In from compressor: 12:38:51:00

WTF?

[John Dobrich]

Just to add another 2 cents to Matt’s reply:

The Timecode 23.98 means the “film” plays back at a speed of 23.976 – just a little slower than 24 fps.

The same way that normal video TC of 29.97 plays back at the speed of 29.97 – just slightly slower than 30 fps.

The reason for the slow down is complicated – just know that it is slowed down. But in both cases, even though it’s running at 23.98, it still has a full set of 24 frames that make up 1 second – they’re just played at the speed of 23.98.

Same story with 29.97 – still has the full set of 30 frames per second. Played at the speed of 29.97.

So yes, you select 24fps.

The Compressor mismatching TCs issue has been an annoyance from the start and why it still is a major bug in FS3 is a mystery to me.