Premiere is one frame off in cuts from DR

Recently a Premiere cutter told me that he was under the impression there was something wrong with rough cuts coming from Resolve. I tested carefully with a recording of an electronic clapper, and this is what I found:

The recordings were .MP4 originals from a Sony A6000 in XAVC-S, which are read just fine (including sound) into Resolve. We did an edit in Resolve and moved it into Premiere Pro by XML. Every cut turned out one frame early (like 00:02:17:24 instead of 00:02:18:00).

This happens with XAVC-S from the A7S too, which has timecode, other than the A6000. After correction in Premiere and handing the XML back to Resolve (importing the files with it) into a new project, there was no difference. Who may be the culprit here?

Were the footage drop or none drop frame rate? There could be a mismatch in how the timecode is interpreted in Premiere vs Resolve.

If you shot at 29.97 and sent the edited XML from resolve to Premiere which might identify the timecode as 30FPS as a default timecode setting, then this could be the issue.

I've had similar issues with footage shot at 23.976 edited in Premier at 24FPS and when brought in to Resolve, each shot started either 1 frame before or after. Ofcourse this is the vice versa of your situation.

I'm not sure if you have a similar issue but that is where I believe the problem might be located. A timecode interpret issue.

Thanks for the info, but I'm on 25 fps.

that sound like a silly thing like one software start to assign the arbitrary tc from 00.00.00.00 and the other from 00.00.00.01....

This is yet another good reason for avoiding cameras that don't embed real timecode during production. Hour 0 timecode ain't happening.

Some of the footage has timecode from the A7S.

+1
Yes, you definitely weren't imagining it... Unfortunately for the thread (and fortunately for me) I haven't had to deal with this since last year, when a key client switched from a DSLR to FS7 with big boys timecode.

But I'm bumping this to hear if this is still happening in Premiere 2017.0.2 and Resolve 12.5.5? Would be good to know.

Happened to me with a7s footage. Make sure you transcode all footage via Resolve first.


Sent from my iPad using Tapatalk