Skip to main content
Participant
October 18, 2018
Answered

Mismatched media timecode in and out points Premiere 13.0

  • October 18, 2018
  • 13 replies
  • 6182 views

Anyone else experiencing Premiere 13.0 mismatching timecode? I had a project done in Premiere 12 that needed its media reconnected. I opened in 13, and when it reconnected, in and out points were all over the map. Went back to 12, it reconnected just fine. No big deal, I think, it's the whole "don't open old projects in new releases".

Well, now I'm trying to send a different edit via XML to Davinci Resolve for color grading. All the in and out points are incredibly off in Resolve - have NEVER had an import issue before like this. Some clips are just flat out offline because, according to Resolve, the XML calls for selections outside of the clip runtimes.

So, I think to myself, let's have 12 be the middle man between 13 and Resolve. Go to 12, import XML - it freezes up. Every time. Now, unfortunately, I must go back and redo my recut of the last edit, as there is no way to get it out of Premiere 13 reliably, even to last year's Premiere.

13 was not ready for prime time, this is a HUGE problem.

This topic has been closed for replies.
Correct answer Kevin-Monahan

This was a bug, Brandon Freeman. Very sorry! It is fixed in Premiere Pro 13.1, however. Please update Premiere Pro and check out this issue once more.

Regards,

Kevin

13 replies

Participant
February 14, 2020

Having this exact same issue with a file I got a project from an editor made in Premiere 2019 and I have the latest version. It asked for conversion when I opened it. When I opened the sequence about 50% of the clips where offset or simply offline. Been struggling with this all day, CMO is expecting my edit in an hour. I am not having the best time :).

Novel_MP
Participating Frequently
April 16, 2019

Yeah this is a MAJOR bug. I hope Adobe has bumped this one to the top of the list. A bug like this is a show stopper.

I did find a workaround for now. Make a new project and import your project instead of trying to open your old project in the new version of Premiere. That seemed to work for me.

Kevin-Monahan
Community Manager
Community Manager
April 16, 2019

Hi Ben, this should be fixed in 13.1. If you have not updated yet, please check that out. Thanks also to @Chad Baker

for filing the bug and to the devs for the fix.

Ben, if the update does not fix the issue, please report that here.

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participating Frequently
March 19, 2019

Unchecking align to time code in the link media dialogue box worked for me!

Chad Baker
Adobe Employee
Adobe Employee
March 19, 2019

Enterprise Support here. Just leaving a quick note to say that I've submitted this issue for investigation.

mikewutheflash
Participant
March 9, 2019

So I had this same problem with my sony a7sii footage.  fixed it by creating a new project and importing the old project file, rather than opening the old project file.  hope that helps!

Participating Frequently
March 6, 2019

I have this same problem when working with past project version but now it is happening with 2019 project files. premiere is just importing it incorrectly.

Participant
February 11, 2019

I found a solution, at least for now. I have this issue every time someone sends me a project and I open it on my computer. When I relink the media, if I uncheck "align timecode" this seems to fix the issue.

Participant
February 26, 2019

Thanks a lot! This worked here!

andrek60248433
Participant
January 8, 2019

Does anyone know what actually causes this? We've got a few projects that were originated in version 13 and we're too far in to restart them in version 12. It'll be annoying, but we can retime, and slip the shots that got shifted. If I fix these errors manually, and then save the project, am I at risk of this happening again to the same project?

Participant
December 19, 2018

I'm having the same issue. For me the issue started when I updated to Premiere 12.0 and has continued with Premiere 13.0. I don't understand how this has not been fixed yet. Updating to 13.0.2 did not fix the issue yet for me. There have been so many bugs with adobe premiere since 11.0, it's completely ridiculous.

Here's a description:

Sony footage timecode is off whenever I open a project that someone else has worked on on a different computer (even if we're both on the exact same version of premiere 13.0.1) or when I open a project from an older version of Premiere.

When I update premiere and open a project for the first time on my computer, the timecode issue fixes itself. This happened when I updated to 13.0.1 and when I updated to 13.0.2 so it doesn't seem to be a specific update.

When timecode is off in a project and I update premiere and open the project in the updated version of Premiere, the timecode issue is not fixed.

Daniel Hoover
Inspiring
December 17, 2018

Some people on UserVoice are reporting that this MXF timecode bug has been fixed in Premiere 13.0.2 - has anyone else tried the new update?

Bug: timecode is not accurate upon import – Adobe video & audio apps