-
Speed Change vs Premiere Pro
Over the years I have struggled with conforms between PP and Resolve as it relates to simple speed changes. (Edit in PP and colorist uses Resolve.)
When I would get graded clips back (with 1 second heads and tails) I would put them into PP but sometimes I could never get the speed change to match frame for frame. I would do a difference matte when online as normal workflow and some of the speed changes would flash a bit showing that there are intermittent frame differences.
Recently I moved a project from PP via XML to Resolve myself so I could prep the project for the colorist. When I did an offline difference comparison I could see what I have see over the years, a difference on how each program calculates which frame to drop. During the length of the clip there are one or two frame differences.
As I am moving completely to Resolve this point is moot, but I have always wondered what the problem is.
My guess is that Premiere starts it counting of frames (so it knows which ones to drop/duplicate) from the beginning of the clip. And Resolve starts its counting from the in point of the clip.
Or maybe it is the other way around.
So in the color grade example, the original footage might be 10:23 but the grade might be 2:22.
-
2 Replies
-
Can you tell the difference without a difference matte? Are you also taking into account things like frame blend, vs optical flow etc. I would hope both systems did their calculations based on timecode so the in frame for both should be identical.
I should add you might have to interrogate the xml from PP and the return xml from Resolve to see if the correct timecode match is an xml problem and where that error is generated
-
No optical flow or frame blend. Just a simple speed change (no ramp). Timecode at edit point matches, and several frames match within the clip, just not everyone.
Noticeable without difference matte? Depends.
Reply to this Discussion! Login or Sign Up