Doom9's Forum - View Single Post

wonkey_monkey · 27th September 2009, 19:02

Hi Gunnar,

Something I noticed a long time ago is that Deshaker takes longer and longer to do the actual "Deshaking..." part with higher values of motion smoothness. For example (10000 frames):

Motion smoothness=100, <1s
Motion smoothness=1000, 11s
Motion smoothness=10000, >200s

I assume these values decide how many frames' worth of parameters either side are averaged to decide how to move that frame, and that it might be a Gaussian distribution to give a smooth effect. Have you considered optimizing this step? For instance, you can approximate a Gaussian "blur" of parameters like this with multiple simple box blurs, which will only take longer as the number of frames increases, not (or not much) with the width of the "blur".

I know most people won't find this a problem but if you do want to use a high value of motion smoothness, it can take a while.

David

27th September 2009, 19:02	#182 \| Link
wonkey_monkey Formerly davidh***** Join Date: Jan 2004 Posts: 2,496	Hi Gunnar, Something I noticed a long time ago is that Deshaker takes longer and longer to do the actual "Deshaking..." part with higher values of motion smoothness. For example (10000 frames): Motion smoothness=100, <1s Motion smoothness=1000, 11s Motion smoothness=10000, >200s I assume these values decide how many frames' worth of parameters either side are averaged to decide how to move that frame, and that it might be a Gaussian distribution to give a smooth effect. Have you considered optimizing this step? For instance, you can approximate a Gaussian "blur" of parameters like this with multiple simple box blurs, which will only take longer as the number of frames increases, not (or not much) with the width of the "blur". I know most people won't find this a problem but if you do want to use a high value of motion smoothness, it can take a while. David