[Dexter Huizenga]

Hi all, I’ve had a major victory with this issue and I feel that it is my duty to humanity to share my solve. Not sure it’s exactly the same issue as the original poster, but this is the closest thread I can find. The issue was as follows:

– Several times in the past we have been given xmls from editorial which reference footage with different frame rates in the same timeline.
– The davinci timeline is set to 23.976 but some of the footage is 24fps
– the 24fps footage is all off by several frames from the cutting copy, and double clicking it to reveal in the preview window shows that the timecode has in fact shifted.
– comparing the same frame in the media pool and in the timeline shows that the clip in the timeline no longer has the original timecode, the clip I will use an example originally had a start frame of 15:09:37:17, which had been shifted to 15:10:32:06
– my theory was that it was shifting the 24fps timecode so it played at 23.976—essentially multiplying the timecode value by 1.001001001001001, (the difference between 23.976 and 24)
– upon testing this theory, I learned that this is exactly what was happening, but the value was off by three frames—which could be exactly what was happening under the hood in davinci to cause the 24fps shots to all be off by a couple frames.

THE SOLVE:

– Before importing any clips (it wont let you change after), I changed the mixed frame range format from “final cut pro 7” to “resolve”.
– you can find this option in project settings/general/conform options, or in the xml import dialogue.
– the clips which were off by a couple of frames when I imported previously were now lining up perfectly, and the timecode was proper when I double clicked the shot in the timeline.

Hope this helps anyone with a similar issue! I’ve spent way too long brute-force conforming timelines where almost every shot is lining up wrong, and too long researching this issue to no avail. Victory at last!

Cheers!
Dexter