Stabilize (green flashes in DePan bug?)

[StainlessS]

??? Is the brew affecting your memory, or maybe mine ???

Mine probably :)

EDIT: To below, Good one Fizzy :D

[Fizick]

StainlessS, Do you know (remember) my topic about "the best" at http://forum.doom9.org/showthread.php?t=114582
:)
but let's be on "green" topic here :D

[pwnsweet]

It seems my question got lost in the fray, but I'm wondering:

When I stabilize, should it be done on a clip with no black borders or is it OK to have small borders around the image?

[StainlessS]

Nice one Fizzy :D

pwnsweet, maybe try


function Padding(clip c, int left, int top, int right, int bottom) {
# Didee: http://forum.doom9.org/showthread.php?p=1596804#post1596804
# eg, Padding(32,32,0,0).Padding(0,0,32,32)
w = c.width()
h = c.height()
c.pointresize( w+left+right, h+top+bottom, -left, -top, w+left+right, h+top+bottom )
}

after crop borders. [EDIT: Then stabilize, then crop off padding]

[VS_Fan]

Has anyone else had problems using DepanEstabilize (v1.13.1, April 6, 2016) with globaldata generated with MDepan function from mvtools2?

If I use DepanEstabilize version 1.10.1, from January 27, 2008, I get no problems: a consistent, smooth stabilized result as expected, based on globaldata gererated with both DepanEstimate and MDepan.

DepanEstabilize v1.13.1 works as expected if I use globaldata generated with the old and newest versions of DepanEstimate, but if I generate globaldata with MDepan function from mvtools2, the adjustments from DepanEstimate v1.13.1 seam to obey to random dx, dy, rot and zoom.

I’m using avisynth 2.60, and tried different versions of mvtools2: 2.5.11.3 (19.09.2011 by Fizick) and 2.5.11.22 (26.04.2016 by Fizick) and the results are the same.

Any clue to what’s going on here?