single precision MVTools plugin (stable)

[Quadratic]

Yes, no problems.

import vapoursynth as vs
import vsutil
core = vs.core

clip = core.lsmas.LWLibavSource()
clip = vsutil.depth(clip, 32)
clip = core.grain.Add(clip, var=10, uvar=3, seed=444)
ref = clip

sup = core.mvsf.Super(clip)
vec = core.mvsf.Analyze(sup, radius=1, overlap=4)
vec = core.mvsf.Recalculate(sup, vec, blksize=4, overlap=2)
clip = core.mvsf.Degrain(clip, sup, vec, thsad=400)

ref.set_output(1)
clip.set_output(2)

[poisondeathray]

Last commit was Aug 18,2020 "various bug fixes "
https://github.com/IFeelBloated/vapo...c455587173630b

CK your binary from post 131 predates that commit (May 20,2020)

[ChaosKing]

Can we have a bug fix release then?

[poisondeathray]

Originally Posted by ChaosKing

Can we have a bug fix reelase then?

I was going to ask the same thing

[feisty2]

you need a binary compiled after this: https://github.com/IFeelBloated/vapo...569603bb85bb2e

[MysteryX]

When I try to load libmvtools_sf_em64t.dll, it gives this error, why?

Avisynth open failure:
Python exception: Failed to load libmvtools_sf_em64t.dll. GetLastError() returned 126. The file you tried to load or one of its dependencies is probably missing.

[ChaosKing]

Dependencies are:
- msvcrt.dll
- libfftw3-3.dll

[MysteryX]

OK installed libfftw3-3 and it loads.

If I load r9, Degrain doesn't exist. If I load r10 pre-release, it says that Analyse doesn't exist

mvsf.Analyse is removed, type "Analyze" instead

How do I reference Analyse? ah dang -- change 's' with 'z'

Now Degrain has too many unnamed arguments specified.

clean = core.mvsf.Degrain(c if chroma else cy, super2, bvec1, fvec1, bvec2, fvec2, bvec3, fvec3, bvec4, fvec4, thsad=thSAD)

The complete lack of documentation is a bit frustrating.

[MysteryX]

xClean will support r9 of mvtools-sf and not r10-prerelease. This is meant to be a swap-in replacement for the regular library. Adding new API features is fine, but removing features and changing names, that's not good, because it breaks API compatibility.

This will also cause serious versioning issues. Some scripts will be written for mvtools-sf r9 and some for mvtools-sf r10. For a program like StaxRip, which of the 2 versions should it bundle then? Backwards compatibility is important.

[StainlessS]

Could implement both Analyse and Analyze, and avoid confusion/breakage [as for GreyScale/GrayScale in Avisynth].