Skip to main content
Participant
June 26, 2023

Program TC overlay displays incorrect timecode

  • June 26, 2023
  • 45 replies
  • 5029 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

Henrique - TMMW
Participating Frequently
January 20, 2025

I'm also able to reproduce the bug here.

 

Our integration relies on timecode for syncing, and the same way Premiere displays

the wrong timecode it also deliveres that timecode when we get a project item timecode

from it's metadata.

 

Would be really nice to have a fix for this soon seen that it first resported over 18 months ago.

 

Many thanks!!

 

Henrique \\ TMMW

Henrique \ TMMW
Participating Frequently
January 17, 2025

@Kevin-Monahan I'm also facing the same problem. Everything was fine until I started on my first 23.976 fps project and now this bug is messing everything up. My AE has given up and gone to use another NLE for syncing and binning. 

Kevin-Monahan
Community Manager
Community Manager
January 17, 2025

Sorry to hear that, @Kevin Chop Chop. If your AE is unhappy, then I am unhappy too. We need to fix this ASAP. Let me see if @jamieclarke or @Rach McIntire might be able to investigate. I apologize for the issue. Take care.

 

Thanks,
Kevin

 

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Participating Frequently
December 12, 2024

Same problem here, 25.0.0 (build 61).

 

Premiere displays one timecode in the folder (that is the correct one), but when dropped onto the timeline it alters the TC.

The IN point is different from the original file. The same problem occurs when trying to create a Multi-Cam.

 

Participant
November 19, 2024

We are also still experiencing this bug. And we just updated to Premiere v25.

Known Participant
October 4, 2024

I'm on a PC windows 10 using Premiere version 24.6.1 and am still running into this issue. I tried the 'Use default time display' trick but it doesn't resolve the discrepancy.  For fun, I tried importing the same .mxf & .wav into BMD Resolve and it reads and displays everything correctly.

R Neil Haugen
Legend
August 28, 2024

Great catch, and thanks so much for posting back the fix!

 

Now "we" should be able to help others because you were so thorough and thoughtful. Thanks again!

Everyone's mileage always varies ...
Collin K
Participating Frequently
August 28, 2024

I just downloaded and opened PP 24.6.1 (Build 2) to do a quick trial.

 

I imported one .R3D file and one separate sound file that syncs together nicely for an interview. When I did a manual sound sync by matching the timecodes of both files, I was able to replicate the SAME PROBLEM I had in the previous Premiere version where the timecode from the sound file in the Source Monitor did not match the timecode shown in the TC Overlays of this same file.

 

I did figure out a fix, though. When I right-clicked the sound file in the Project, I went to 'Timecode' to see what the file was showing. Time Display Format was showing '23.976 fps Timecode' (without me changing anything) which should have been correct. I changed this setting over to 'Use Default Time Display'. Upon changing from 23.976 to Default, the timecode "fixed" itself and the TC Overlays were now correct and matching the Source Monitor.

 

Hope this helps anyone running into this. I've attached a bunch of screenshots for reference.

Kevin-Monahan
Community Manager
Community Manager
August 28, 2024

Great, @mcx#5000 - I appreciate the news. I will share it with the team.

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Kevin-Monahan
Community Manager
Community Manager
August 28, 2024

Cool, @Collin K - let me know!

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Collin K
Participating Frequently
August 27, 2024

I need to recheck this later this evening. As of last week, I was still seeing the wrong Audio file TC in Overlays versus what the actual file time code in my current project.