That's what I thought. The problem with that approach is that step 1 will result in a slight amount of upsampling, then with step 2 you still don't end up with the native resolution you desire.
Let's say you start with 1080p video. Applying image stabilization will trim a few pixels off the borders (who knows how many), resulting in slightly lower than 1920x1080 native resolution. You can't simply save the video file(s) as-is (without producing) or produce at whatever the existing resolution actually is, you have to select the output resolution (say 1080p again); hence the result is upsampled to a degree to get back to 1920x1080 when you produce.
Then once you import this slightly upsampled video and apply a crop, there's no way to achieve, say, exactly 1280x720 of the
original video pixels. The end result will always result in some amount of up/down sampling to achieve the production resolution (720p in this case).
Why can't we just tell PD what our end-goal is (in terms of pixel dimensions) and let it figure out how to optimally apply the cropping and stabilizing?
Another idea would be to have a stabilizer tool embedded in the crop tool, such that when you crop the video you can select an option to apply stabilization as well, but outside of the cropped frame instead of inside.
A third idea would be an option to set the number of pixels that are removed during stabilizing, so that you know exactly what the resolution is after the stabilization, and you could then adjust for this. I don't like this idea as much however because with PD there's also no way to set the number of pixels that are removed during cropping.
This message was edited 12 times. Last update was at May 26. 2016 11:33