Deshaker settings

Simes wrote on 6/14/2012, 5:43 AM

Really glad to be getting into using deshaker. Have got the frameserver method setup with Deshaker 3 (THANKS AGAIN WWAAG!!!).

After some help with the settings under pass 1. I'm wanting to make the movement detection far more sensitive (am using top & side borders only), but I'm not yet able to get my head around the meanings of the settings under:

1. Discard motions blocks that
a) Max pixel value dif <
b) Match value <
c) 2nd best >
d) move > (wrong dir)
e) move > absolute

2: Discarded areas
a) Deep analysis <
b) Skip if <
c) Detect scenes

I've read the detailed manual, but because I'm not clear what each setting actually does, I'm not actually sure which way I should be moving it to make detection more accurate. I'm tending to still get a jittering/fast seesawing along the x-axis.

Comments

Simes wrote on 6/14/2012, 5:48 AM

Here is the detailed settings page I've been using to try & work out how to set:
http://www.guthspot.se/video/deshaker.htm

JJKizak wrote on 6/14/2012, 6:23 AM

There are many older threads on the pros/cons of shifting away from the defaults in the latest Deshaker app. with comparisons of Mercali also.

JJK

Simes wrote on 6/19/2012, 11:11 AM

Been doing a lot of deshaking!
Amazing program.

Essentially, the footage I had was the equivalent of a studio interview situation with a fixed but single coloured background. I presumed deshaker v3 would find it a piece of cake to lock onto a fixed background, but it didn't find it so easy with the standard settings - & Gunnar explained me that in such a situation, a pattern on the background is what is needed for deshaker to lock on.

Anyway, in case it's useful, Gunnar suggested trying out the following setting adjustments - and they did make a big difference. This is the gist of what he wrote me:

===
You could try decreasing "Discard motion of blocks that have 2nd best match > best - X", maybe all the way to 0. And if the video has very little noise you could try and decrease "Discard motion of blocks that have max pixel value diff < X" a little too, but not too much. If the vectors don't show any motion when there is motion, that setting is too low. Also, if the camera isn't moving around too much, you might want to decrease the value of "Discard motion of blocks that move > X pixels in wrong direction", to 1 or so. That way deshaker will try to ignore even objects that move very slowly.
===