Participating Frequently

Question

Premiere Media Start timecode issue MXF

Forum|Forum|7 years ago
October 22, 2018
12 replies
9717 views

We are having big trouble with some Sony Venice MXF footage.

Premiere is misinterpreting the Media Start timecode across several days worth of shoots.

The problem reproduces in both Premiere 2018 and 2019, on multiple machines, in old and new project files, and even after clearing the cache and aggressively deleting XMP and other sidecar files.

Please see the graphic below for more description.

Since the text on that graphic isn't web searchable, here's a summary of the issue:

We received a drive from our DP and copied it onto our NAS, as we have successfully done dozens of times before.

We ran the footage through Adobe Media Encoder to make smaller MP4s with burned in timecode for the producers to review, as well as WAVs for transcription.

As we started editing using selects notes with TC from the producers, it became clear that the timecode was off.

Upon investigation, we ascertained that Premiere had the Media Start timecode screwed up.

Nothing we've done has been able to get the timecode correct, short of manually going clip by clip and using Interpret Footage/Timecode to set the correct timecode as an Alternate Start Timecode, which is not an acceptable solution in a busy post-production studio.

Anybody been having similar experiences, or have a solution?

Thanks in advance,

John

San Francisco, CA

This topic has been closed for replies.

John_W_PilgrimAuthor

Participating Frequently

This error was resolved in 13.1

Kevin-Monahan

Community Manager

Is this issue solved for you now, John?

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

noahg64558676

Participant

Kevin -

This issue is NOT resolved.

J

Jan_Berlin

Known Participant

Hey folks. I am not sure about this Issue, but I have a similar Problem: I want to create a 24fps H264 File with Timecode Overlay form a ProRes Mov Source. AME (using the Timecode Overlay Effect) and Premiere (using the Timecode Effect on a adjustment Layer) will cause in a wrong Timecode Overlay. AME reads the TC correctly (on the In-Out-Timeline) but displays another one.

Another big Issue with an uptodate Adobe product.

Btw: CC2017 is fine with that!

E

Elliott_Sound

Participant

@Daniel Hoover The 13.0.2 update seems to have fixed the timecode problem for me, at least for the Canon c300 MkII I use at my work.

Daniel Hoover

Inspiring

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

K

KS-Andre

Participant

This issue is still present.

Has Adobe still not recognized there is an issue with how it's misinterpreting timecode?!?! This is not the only place mentioned this issue.

It keeps me from bouncing into Davinci for Color without performing a Render and Replace action first which is a kill in Drive space.

If this isn't cleared I will take it as my reason to jump to Resolve for my work entirely. I know a post house who have done so and are not hurting for it.

AB_BTK

Participant

Same problem with Sony FS7 footage. This is a major problem. I hope Adobe fixes it PDQ.

E

Elliott_Sound

Participant

Just wanted to chime in and say that I am also experiencing this issue bringing in Canon MXF OP1a wrapped files from the Canon C300 MkII at my work. Hoping for a bug fix soon! Thank you for the thread @John W Pilgrim

ChrisZ590

Participant

I have just discovered this problem with the MXF files from the Sony PXW-Z190 as well.

Compared the media timecode start time with the Media Info app vs Adobe Premiere Pro. Premiere Pro is reporting incorrect timecode. Also tried to transcode/rewrap to MP4 file in Media Encoder. It also read and created new file with incorrect timecode.

Frustrating to say the least. Hopefully a fix is coming from Adobe very soon.

Cool_Hand

Participating Frequently

I have been suffering from this problem as well, with a Sony F55. Two shoots with a Sony F55 and a Canon C300 MKII, since the 2019 update, the F55 shows the wrong source timecode, the C300 and backup audio match perfect. I even tested it on another computer running Premiere 2019 and the same issue appeared.

After trying to export to Resolve, and only getting the C300 footage to work, I discovered that the timecode for the F55 in Resolve was different then Premiere, and correct. I have now been modifying the start timecodes in the source clips that i need to sync up with the C300.

It's a pain, but until there is a fix I have on other solution.

John_W_PilgrimAuthor

Participating Frequently

Thanks Cool-Hand.
If you would, please click the "I have the same question" flag at the bottom of my original post above.

I have been told that the Premiere "Formats" team is aware of this bug and is currently working on it.

Resolve correctly read the MXF start timecode, where as Premiere 2019 has a bug reading it, so it's not surprising that XML generated by Premiere 2019 does not accurately re-conform in Resolve.

How are you fixing the Media Start timecode in Premiere? Are you using Modify Clip / Timecode to set a new Alternate Timecode for the Start of File for each clip?

Once you did that, did the XML successfully translate from Premiere to Resolve?

Cool_Hand

Participating Frequently

Hi John,

Yes, once I Modify Clip / Timecode and changed the Timecode to my correct new Alternate code. Resolve was happy with my new AFF and XML.

This doesn't work in old projects, I found I could cut in CC 2019 - then set a new Alternate Timecode. In old project the Timecode is off like it is in Resolve throughout the sequences. I had to reinstall Premiere 12.2, I do think it's a Drop frame issue now.

Thanks for the info I am glad the team knows.

Cheers,

Lucas

John_W_PilgrimAuthor

Participating Frequently

RameezKhan or Kevin-Monahan - From what I can see in other posts you seem to be the timecode experts. Any insight on this issue?

Thanks in advance....

Kevin-Monahan

Community Manager

John,

I'll make sure the bug is filed internally. I truly apologize for this problem. I think others on user voice have noticed it. Several copies of the same issue seem to be reporting it. This one has the most upvotes. I'll upvote it, as well: Bug: timecode is not accurate upon import – Adobe video & audio apps

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

D

DoyleTX

Participating Frequently

I am also having this problem with MP4 clips recorded by a Sony A7Riii. "Lucky" for me, I'm also recording to an Odyssey 7Q+ with camera trigger, which means that the camera footage TC is always 1 frame behind the 7Q+. But this is sort of a silly issue.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded