New toy: MVTools version with true motion compensation

[Fizick]

Didйe,
1. edges processing is not implemented. I never used "padding" command. Will look later.

2. MVCompensate use same (sharp) interpolation (reckognizing some flag in the vector clip) in mode=1 and mode=0.

3. your suggestion is interesting, but it may produce some blocking.
One of aims of my current overlapped procesing is deblocking.
Will try strives for perfection later. :)


drio49,
MFlowblur?
But please post your "usage" questions to "usage" forum:
http://forum.doom9.org/showthread.php?t=84770

[Fizick]

Didйe,
I disabled external "Padding" function since MVTools v.1.1.1.
We do not need in external double-sided padding (but only bottom and right).
Now I simply fill it by source pixels.
Try use addborders or mirrorborders as a workaround now.
May be I will implement better padding internally some time.

[Chainmax]

Would there be any way to make MVTools work with tsp's multithreaded version of Avisynth?

[Pookie]

Only if you buy Fizick a dual core system to debug the new code with....:D

Have you looked at Motion by mg262/clouded? It isn't as sophisticated, but it might work with MT Avisynth.

[Didée]

Use 2 PCs to process 1st/2nd half of the source. Very stable solution, and available right now.

If short of a 2nd PC, you can simulate it like this: first do the 1st-PC's part, then do the 2nd-PC's part, and join both parts afterwards. :p :D
[*running man*]

[Fizick]

You also may try run two AVS (two part of file) in separate threads :)

Seriously, some time I will look to it. I am afraid I firstly must remove all IDX, but it will run slower. :)

[Chainmax]

That's good to hear, and your suggestion is actually a pretty good idea. Take your time, good things do tend to take lots of time :).

[Revgen]

@Chainmax,

If you really want to run MVtools in Dual-CPU, make sure to get a big HDD and encode 2 avs files to lossless. I always do this with MVBOB. I then encode after I'm done. The process is alot faster. The speed increase for me is about 70%.

[TSchniede]

But it is not that straight-forward, mvbob for example can only be used in one encoding at a time unless you specify different idx values for every thread. With the new 1.5 mvtools and the 2x-clip it's probably easier.
Most of the time it works using different idx-values for each thread, but avisynth tends to mix different values of the same variable name, so better no reuses of the same name. Tracking these bugs is very difficult (only sporadically visible).