Vapoursynth

[feisty2]

Okay...
Where's test5?

[Selur]

@myrsloik: any chance for a portable version of the test6 ?

[Myrsloik]

Originally Posted by Selur

@myrsloik: any chance for a portable version of the test6 ?

Maybe when I reach RC stage. Still have to test so many things. But at least I'm done with all new features for R33... I think.

QTGMC (and other complex scripts) speed comparisons with R32 are also welcome. I'm curious how bug different it makes. Just remember to replace the relevant removegrainmodes first.

[~SimpleX~]

Myrsloik, could you please fix PlaneStats (average/diff)? I'd like to use it in SmartFade function (which compares average luma of top/bottom fields).

[Myrsloik]

Originally Posted by ~SimpleX~

Myrsloik, could you please fix PlaneStats (average/diff)? I'd like to use it in SmartFade function (which compares average luma of top/bottom fields).

Fix what? It's correct. Or you at least have to describe why you think it sin't correct.

[~SimpleX~]

Why abs(f[0].props.PlaneStatsAverage - f[1].props.PlaneStatsAverage) is not the same with the PlaneStatsDiff generated by core.std.PlaneStats(clip1, clip2, plane=0)?
I've asked that one page ago.

[Myrsloik]

Originally Posted by ~SimpleX~

Why abs(f[0].props.PlaneStatsAverage - f[1].props.PlaneStatsAverage) is not the same with the PlaneStatsDiff generated by core.std.PlaneStats(clip1, clip2, plane=0)?
I've asked that one page ago.

Because that's not how a per pixel difference is calculated

[jackoneill]

Originally Posted by ~SimpleX~

Myrsloik, could you please fix PlaneStats (average/diff)? I'd like to use it in SmartFade function (which compares average luma of top/bottom fields).

Maybe this helps: https://github.com/dubhater/Wobbly/b...lyJob.cpp#L280

[~SimpleX~]

Originally Posted by Myrsloik

Only planestats gives the correct value. The planeaverage way is wrong. I think I brainfarted when I wrote that lpng ago.

Then I didn't understand what you meant here. Sorry.

Originally Posted by jackoneill

Maybe this helps: https://github.com/dubhater/Wobbly/b...lyJob.cpp#L280

Yup, thanks. That's close to my function, but I like the code.

[aculnaig]

VapourSynth latest git.
zimg latest git.

Give me this.

CXX      src/core/libvapoursynth_la-vsresize.lo
src/core/vsresize.cpp: In constructor ‘{anonymous}::vszimg::vszimg(const VSMap*, void*, VSCore*, const VSAPI*)’:
src/core/vsresize.cpp:747:69: error: ‘NAN’ was not declared in this scope
                 src_left = propGetScalarDef<double>(in, "src_left", NAN, vsapi);
                                                                     ^~~
make: *** [Makefile:1457: src/core/libvapoursynth_la-vsresize.lo] Error 1

GCC info

gcc --version


gcc (GCC) 6.1.1 20160802
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

EDIT --> Rolling back to commit f96db59 compile fine

[feisty2]

@Myrsloik
http://forum.doom9.org/showthread.php?t=173470
http://forum.doom9.org/showthread.php?t=173703
these 2 modules I wrote are well documented and seem to be bug free for now after series of different tests..
can you add them to the plugin list?

[Myrsloik]

It's time for the glorious R33 RC1!

It's now mostly compiled with clang-cl which should give slightly better performance and hopefully no new bugs either. Note that the internal resizers now have reached feature parity with fmtconv apart from a few of the more exotic dithering methods.

And remember to STOP USING REMOVE GRAIN (sometimes)

Changes:

r33:
added autoadjust to prefetch list
the resizers can now have the active image region specified to do things like subpixel shifts and cropping
genericfilters is no longer included with the installer and has been deprecated for a long time, if you for some reason miss canny simply use the tcanny plugin instead for a better implementation
assvapour was renamed to subtext and now supports bitmap subtitles as well (jackoneill)
alternative python installations can now be selected when installing on windows, note that there many pitfalls when not using python from python.org
the rshift argument of sobel/prewitt is now deprecated because it's pointless, simply scale the min and max args as appropriate
optimized minimum, maximum, median, deflate, inflate, convolution (1x3, 3x1 and 3x3) on x86 cpus
added float support to minimum, maximum, median, deflate, inflate, convolution, prewitt, sobel, invert, limiter, binarize and levels functions, note that most of the arguments have been changed from int to float
the whole project can now be compiled with clang-cl under windows
directshowsource from recent avs+ can now be used
fixed swapped uv planes with yuv411 output in vsvfw and avfs
merged vsfs with the latest version of avfs, avfs now work for both vapoursynth and avisynth scripts and no longer has shell integration
avisource can now open all formats vsvfw can output plus b48r
fixed corrupted output in vfm when clip2 isn't 8 bit
fixed crash due to stack overflow if an extremely long filter graph is freed
now installs the vs2015 update 3 runtimes on windows
vsvfw will now automatically convert rgb24 to packed bgra for convenience
added b64a and P416 output to vsvfw
updated to zimg v2.2 branch
mixed imwri fixes
fixed rare access violation in expr when ternary operator is used (jackoneill)

As usual speed comparisons with R32 are welcome. Especially with scripts with fmtconv and removegrain replaced.

[Myrsloik]

Originally Posted by feisty2

@Myrsloik
http://forum.doom9.org/showthread.php?t=173470
http://forum.doom9.org/showthread.php?t=173703
these 2 modules I wrote are well documented and seem to be bug free for now after series of different tests..
can you add them to the plugin list?

Vine I'll add but something that even calls itself placebo is something I'm not so sure would be useful to others...

[feisty2]

Originally Posted by Myrsloik

Vine I'll add but something that even calls itself placebo is something I'm not so sure would be useful to others...

I found that performance boost without serious quality degradation is possible for Oyster recently, so keeping the temporal radius 6 for Oyster.Basic and setting a smaller radius like 3 or 2 in other functions gave me at least 10x speed boost! speed could be further revved by using 0.5 pixel precision motion estimation instead of 0.25 pixel precision stuff, and MVTools' internal resampling function instead of NNEDI

and besides, it could also be useful if someone has some short and precious footage that suffers from compression artifacts, in this case people care much less about performance and much more about quality, like movies that were shot mostly on 35mm but a few scenes on 70mm IMAX because those scenes are valuable and deserve better

or maybe someone like me finds it interesting and would like to toy or experiment with it...

[Selur]

It's time for the glorious R33 RC1!

Portable version too ?

[Myrsloik]

Originally Posted by Selur

Portable version too ?

32bit

64bit

[Selur]

Thanks!

[feisty2]

https://github.com/IFeelBloated/vapo...eleases/tag/r4
windows binaries(x86+x64 with no extension) for spatialsoften and temporalsoften
I messed around with LLVM a while ago and the binary it generated was slower than msvc binary...

[Myrsloik]

R33 RC2

Possibly fixes some newly introduced resizing issues

Will post a portable version after things are confirmed to actually be fixed

[Selur]

Portable version too ?