

He did not use either “Set to Frame Size” or “Scale to Frame Size” from what I can tell.

The editor used Premiere Pro and scaled the clips manually.

This particular situation arose while conforming 2944×2160 anamorphic Alexa footage to a 1920x1080p XML timeline. I just wrapped a paying job today where this came into play for the entire timeline and I’m working on getting permission to show this in action you’re right, I zipped through that bit pretty quick.Īnamorphic footage adds an interesting layer to this conversation. So the number I should have entered in Resolve for the Input Sizing Scaling is 3.194 and that should give me the perfect zoom factor to offset the Premiere Pro’s Scale factor. The precise math is:ġ/(PrPro scale factor)=(Resolve Input sizing zoom number) In this case, the zoom number is: 3.13.īut that’s the rough math and I was off a bit in the video (I was wrong where I stated the mismatch in sizing was due to motion blur). It turns out the rough math is simple, just move PrPro’s decimal point one to the left and punch that as your zoom factor when creating your Input Sizing preset. To find that number we need to figure out how much to blow up the image. Using input sizing, we can assign every one of those oversized shots to be blown up so that when it is shrunk back down by that 31.3% factor, it’ll perfectly fit the 1080 frame. In the example in this video, it’s shrunk to 31.3% in Premeire for it to fit perfectly into a 1920 x 1080 frame. When two conditions are met: The oversized frame is ‘Set to Frame Size’ in Premiere Pro + Resolve is doing a ‘Center Crop with no Scaling’, the incoming footage will be shrunk in DaVinci Resolve. I hope you’ve enjoyed this series and found it useful.īe sure to use the comments to share thoughts, feedback or ask questions. But you want to repeat this tip for each of the oversized frame formats since each of them will require a different Input Scaling number. This Insight features me only apply this tip to one set of images, the 5k clips. In the process, I’ll show you a very handy trick using DaVinci Resolve’s ‘Input Sizing’ to help you handle tricky conforms. Let’s go back to that project, and re-do it with what we now know I didn’t follow the rules outlined in this series and wasted a ton of time. In that series, I ran into a ton of problems with resizes of 2.5K and larger images not properly importing in DaVinci Resolve. We are closing out this Premiere Pro Detective series by revisiting a short film from another series, ‘ Conforming Giants‘.
