Mismatched media timecode in and out points Premiere 13.0

[Brandon Freeman]

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.

[kjbeditor]

Same problem here. It's absolutely killed my productivity. it also jacked with my ability to sync footage with audio from a recent shoot. All the timecode slipped a little even though we jammed the camera and the mixer/recorder on set. Now I can't export XML's and get them into Resolve, like you said none of the timecode translates.

Adobe what is going on?

[John_W_Pilgrim]

We are having a similar issue with Media Start (and Media End) time codes shifting in CC2019, specifically on MFX files. MOV and MP4 files are unaffected. See Premiere Media Start timecode issue MXF

[Brandon Freeman]

I just updated to 13.0.1. Same problem with XMLs on this project.

[Kevin-Monahan · Accepted solution]

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

[InceptionPost]

I'm running into this bug too, all XML out is affected, as well as relinking offline media in an upgraded project.

XML Scenario

Client sent over project file from 2019, XML sent to Resolve results in all timecode shifted.

I've had to hack the project back to 2018 version, XML works fine there, then re-upgrade the project to 2019 for my client.

Offline Media Scenario

Old project where media destination has changed from a local drive to network, results in all timeode shifted when reconnecting.

If you reconnect in 2018, then upgrade the project, everything is fine.

PLEASE don't release an application with a bug this bad!!

[tanyav162338]

For whatever good it does, I'd just like to add my voice to this forum. I too have the diagonals of death...

I'm sick of problem solving my MXF files what seems EVERY time there's a major update...if there are always MXF problems, then bug check MXF properly! C'mon guys...

Now I must re-install and use last year's version - this is not what I am paying for Adobe...free updates! Please read the fine-print in our contract...

[InceptionPost]

Then release a tool to translate projects down to previous versions.

I can't control what a client does before I begin working. I have started recommending they don't use the 2019 release, but they have an IT department which keeps things current so it's unlikely.

[althaua]

Kevin, this is not helpful until Adobe actually FIXES the bug. I've been dealing with this ever since premiere version 12.0 was released and the number of unfixed bugs has honestly made me start looking for a different NLE software even though I've been using adobe for years. It's really bad.

[Daniel Hoover]

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

[althaua]

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.

[andrek60248433]

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?

[althaua]

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.

[Vivi Brithy]

Thanks a lot! This worked here!

[goonch92]

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.

[mikewutheflash]

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!

[Chad Baker]

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

[goonch92]

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

[Novel_MP]

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]

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

[LuisMedrano]

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 :).