Skip to main content
josiahtschetter
Participant
October 20, 2023
Question

Files seemingly randomly assigned new timecodes, breaking them in sequences

  • October 20, 2023
  • 2 replies
  • 209 views

This has happened to two projects so far.
My timeline had separate audio and video. The video file had a new timecode associated with it on opening. Going back to old saves did not resolve. The timecode started before original 00:00 and ended before original ending. It had slipped by ~ 3 minutes and some change. Once I figured that out, I batch slipped all of the affected clips back by the exact time. It happened on another video clip in a different timeline in the same project, this time it had slipped by ~ 6 some minuets and I applied the same fix. Insanely frustrating but fixable.
The next project was an audio track, it started about a minute in and ended two ish minutes before original ending. So even when bringing the entire audio file into the timeline, it didn't read as the full length as it did in finder. No in and out points were set. No subclips were made. The timeline did not indicate that it was the end of the clip, but there was nowhere in premiere that I could play past the new endpoint.
 
If this is a feature-not-a-bug situation, and I am woefully unaware, I would assume this is a newer future. I have never seen this kind of behavior in the past 9 years of being a Premiere user.
 
I am remaining on 23.6. I can not afford to upgrade my team in the middle of event season.
We are on Mac Pro Intell macOS Ventura builds.
 
Any and all help or feedback is appreciated.

This topic has been closed for replies.

2 replies

Kevin-Monahan
Community Manager
Community Manager
October 24, 2023

Hi @josiahtschetter,

I read your message. It sounds like you created the sequences in a version which exhibited a pretty bad bug, which has been fixed. 

 

What can happen is that if you update a project which contains a sequence from the version exhibiting that bug, it might still be having that trouble in the current version, or similar unexpected behavior. Could that be the problem? Try a brand new sequence in your project and note if it has the same problem. I hope that this issue subsides in your projects. New ones should not have this problem. 

 

Let us know if you need help with anything.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Community Manager
October 20, 2023

Moving it to Discussions