Skill Level: Intermediate / Views: 79
/ System Requirements: Windows Vista or 7, XP ok too., .Net framework 4
Here's another look at using Motion Estimation with the Motion Prediction Module from PD Pro 7, as applicable to videos and to rendered animations of 3D logos in this case. This shows a comparison of a traditional frame blending approach vs. the motion prediction approach.It may take a few tries to tweak the parameters, and get a good combination, but in the end it could be worth the effort, especially if the rendering of the frames took a long time and you can't re-render them with the added frames, economically speaking.Generally speaking, you'll want to consider this option if you have a short animation that needs to last longer, and thus you want to time-stretch it without going through re-rendering the whole lot in the 3D side, i.e. when it took hours to render and you can't afford to take even longer to render, say, 10x that many frames for a 10x timelapse.In this example, the 3D logo was rendered at high (but not highest) settings, took a minute or two per frame to render. This is not a typical case. You'll be more interested in this technique when it takes an hour per frame to render :-)The last clip was done with 60 frames per second and with global illumination enabled, adding significant rendering time to it all. In cases like these it will definitely be a time saver to use motion prediction. Even if it takes a few minutes to get the parameters right, in the end it's much shorter than rendering it in 3D over 300+ frames if you can get away with rendering just 30-60 frames and fill in the missing frames through motion estimated interpolation.
staigermanus on 9:01AM Thu, 26 April 2012