Skip to main content
Participant
June 26, 2023

Program TC overlay displays incorrect timecode

  • June 26, 2023
  • 45 replies
  • 5028 views

I imported shots with double-system audio recorded 32-bit float having jammed an FX6 from a MixPre6ii.  I can sync camera (with guide track) and audio clips in the timeline via TC with no problem.  Here's the oddity: Suddenly the TC overlay in the Program window displays incorrect TC for only the audio clips (up to a minute off), but PPro seems to read the proper TC because I can still sync clips using TC in the timeline.  Also, I had TC properly displayed in a couple of timelines, but when I went to another timeline and then back to the timelines that had correctly displayed the TC, they now also displayed incorrect TC, i.e. the display went bad in seconds.  I had correct TC displayed in these timelines for weeks until this anomaly occurred.  I know because I did a test shot shooting the display of the MixPre, which displayed the same TC as the PPro Program overlay.   I uninstalled and reinstalled PPro: same problem.  On another computer: same problem.  Is this PPro having problems with 32-bit float?  Something else?  [I'm on a trashcan Mac Pro, OS 12.6.6, PPro v23.5]  Thoughts?  Thanks

45 replies

Participant
October 19, 2025

I have moved to a Mac Mini M4 (Tahoe 26.0.1) and am on Premiere Pro 25.5.0 (build 13) AND STILL audio clips display incorrect timecode in the program window overlay (though if I match frame the audio clip to the source window the correct timecode appears there).  This is a real hassle, requiring constant selection of the audio clip and match framing it every time I need the audio TC in the program window.  It would be fabulous to have this fixed;  it's been going on in my experience for well over a year.  If there's a workaround I'd very much appreciate hearing about it.  Thanks, Kris

Known Participant
September 10, 2025

This is still broken in 25.4.1 and so is modifying the timecode of any video clip, that ROYALY breaks the timecode of each clip to the point that not even creating a new project and importing the media there will show the correct timecode of the clip. What have you guys done?

Participant
August 10, 2025

I am having this issue in Premiere v25.3 -  running MacOS 14.6.1 on M1 laptop.  TC overlay in Program monitor is incorrect for audio layers but correct for video layers. When I match back to the audio files the TC in the source monitor is correct. Any suggestions would be much appreciated. 

R Neil Haugen
Legend
August 9, 2025

Thanks for posting those details ... and yea, Premiere's time code options need to be built a lot bigger & more flexible. No question there.

Everyone's mileage always varies ...
Participant
August 9, 2025

Hi, Old story: When jamming an FX6, FX3, and MixPre6ii (recording 32-bit float) with two synched Tentacles and a Denecke JB-1, synching via TC in the timeline works fine (though the MixPre is always a frame late-- another story) except, as before, and as many have reported, the overlay display in the program window shows incorrect TC for the MixPre audio clip, though if I match frame the audio clip into the source window I get correct TC.  Since I'm on a 2013 trashcan MacPro, I'm on PPro 23.6.9 build 4.  I'd sure love this long-standing flaw to be corrected.  Thanks

Known Participant
February 13, 2025

In my case, I'm having this problem with the Metadata and Timecode Display effect, where I need to burn in audio timecode for hundreds of files. I feel that, if I was able to set "Time Display" to 23.976 rather than 24, I might be able to solve my issue. However, 23.976 is not one of the options in the dropdown. Is there a reason that there is no 23.976 option on this list? Or is this a different issue, and I should be posting about this in a different thread?

Known Participant
February 13, 2025

@wesley_d2s_Unfortunately, this same workaround doesn't seem to work for me. My timecode readout doesn't change when I set the "Indeterminate Timebase" preference to "23.976" and leave all of my 23.976 WAV files set to "Default". Just for fun, I then tried changing "Default" to "23.976", but this made no change to the timecode. Even if this worked though, I would have to do this one by one for hundreds of files in my case, which I'm not sure would save me any time.

Participant
February 13, 2025

Using the Version 25.1.0 (Build 73) in 2025 and still having this bug. The micahyo's tips worked with me! Thank you so much, Micahyo!


"The workaround is two-part:

Set the "Indeterminate Timebase" preference to "23.976"

Leave all of your 23.976 WAV files set to "Default" under "Timebase Display Format". DO NOT FORCE TO 23.976. Even though that's the appropriate setting, this triggers the bug."

Known Participant
February 13, 2025

I am still experiencing this bug in Premiere 2025.1, and I was experiencing it last year consistently through all versions of 2024 as far as I can recall.

Tried the 'Use Default Time Display' trick, but no dice, still having the same issue.

I'm an AE here trying to sync a huge number of files and burn in separate video and audio timecode. However, I can't actually burn in any audio timecode because none of the tools are spitting out the correct timecode for these separate audio files. I'm currently having to "generate timecode" manually and paste in the timecode of each audio file, but there are hundreds of files so this is an untenable solution in the long run and is already cutting severely into the budget.

Let me know if there is any further information I can provide to help developers try and track down this bug!

Participating Frequently
January 20, 2025

It appears that the display issue in Premiere Pro may be related to the 32-bit float audio format or how it handles timecode overlays for mixed frame rates or formats. Since sync still works fine in the timeline, the issue is likely limited to the TC display in the application window. Try resetting the settings or using a different sequence setting, as this can sometimes resolve display inconsistencies. If the issue persists, check for updates or revert to a previous version of PPro that may work better with timecode overlays.