Skip to main content
Inspiring
May 1, 2025

Source Timecode incorrect in ProRes mov's

  • May 1, 2025
  • 13 replies
  • 920 views
Hi all. Having a source timecode issue that seems specific to the combination of the following:
1) ProRes codec
2) mov's that were originally exported from Premiere or After Effects
3) mov's that were made from a 30 fps timeline
Has anyone ever experienced this or know what might be going on?
The same mov's show the correct timecode in Quicktime and Davinci Resolve, but always show the incorrect source timecode when brought into Premiere or AE.
Also, if I export from Premiere as h.264 instead of ProRes, and reimport, the timecode is also correct.
Examples:
In all these examples my Timeline start TC is 1.00.00.00 and in all cases export metadata is checked:
1) Timeline is 23.976. Export ProRes422. TC is correct upon re-import
2) Timeline is 30fps (or 23.976). Export h.264 mp4. TC is correct upon re-import
3) Timeline is 30fps. Export ProRes422. TC is off every time
**also, if I import an ProRes mov that I know was not created recently (I'm now in Pr 25.1.0) the TC's are correct
and, if I import a ProRes mov that I know was not created in Pr/AE (like transcodes from a DIT from a shoot) the TC's are correct.
Any ideas??
•Adobe Premiere 25.1.0
•MacOS 12.6.7
•MacStudio (2022) M1 Ultra 128GB memory
 

13 replies

R Neil Haugen
Legend
May 1, 2025

That discrepancy looks like either a 29.97->30fps issue, or drop-frame->non-drop-frame.

 

I'm not a great expert on DF/non-DF issues, other than I've hit them a couple times and they were a major puzzlement to sort out.

 

I've also had to work over 29.97 to 30 "even" time issues.

 

So that's why my questions are as they are.

Everyone's mileage always varies ...
dmehalikAuthor
Inspiring
May 1, 2025

Thanks for the reply @R Neil Haugen .  Well, I can't imagine that it would be a drop frame issue because I'm working in a 30fps timeline and am exporting 30fps.---not 29.97, but maybe I don't have a thorough enough understanding. 

In terms of "how much" I had thought that everything was consistently off my 3sec17fr... but after doing a lot of tests today, it seems to be inconsistent.

One thing I did learn after posting this though:

If I "get info" on the file in Premiere, it shows the TC correctly--- even though the TC is incorrect in the source and record monitor overlays.

Attached is a screen grab from such a file.  ProRes mov with timecode burn exported from Premiere in a timeline set to start at the same time.  Resolve shows correct TC, Quicktime shows correct TC, even "get info" in Premiere shows correct TC, but the source/record monitor overlays are wrong... and if I throw a "metadata timecode effect" on, it's also wrong.

R Neil Haugen
Legend
May 1, 2025

A crucial data bit ... what is off, and by how much? Also, I'm wondering if this is a drop-frame/non-drop frame issue ... probably not, but maybe?

Everyone's mileage always varies ...