Adobe to Davinci Frame Rate Issue

ApexAV has really the best answer available at this time.

I deal a lot with colorists, and a standard complaint of their trade (based so much in Resolve) is about the things that DON'T normally conform 'naturally' that they have to manually set in Resolve. And while different NLEs have slightly different issues, they all have them.

One biggie from Premiere, is every freaking time someone uses "Scale to framesize" it's bonkers in Resolve ... in Premiere, if you use "Set to framsize" it normally translates perfectly between apps. So they either have to go into Premiere, re-set all those then export a new XML/EDL out themselves, or have the editor do it. So for many shops, that is a standard item on the list they send to all clients for "this is what YOU do before, during, and after creating the XML/EDL to send to us."

Time changes ... they're another normal hassle. Interpreted changes often make it ok ... but any time ramps or certain other time change effects ... are problematic. May be ok ... may look ok ... but when you line them up with the H.264 "sample" video on the track above, well ... no, it didn't come through correctly. And it's clearly visible.

And the colorist needs to then change that within Resolve. As ApexAV notes.

Neil

I always export an extra guidevideo from Premiere (a simple mp4). Overlay this video over the imported XML in Resolve and you can easily detect the differences between your Premiere timeline and the Resolve timeline. From there you can individually change the "wrong parts" of the Resolve Timeline by hand.

When you complete the roundtrip I use the same method to check my timelines.

Framerate changes ... speed ramps or interpreted time?

Neil