VapourSource: vapoursynth script importer for avisynth

[Chikuzen]

VapourSource is a source filter of avisynth2.6 to import vapoursynth script.
You could treat vpy more easily than AVISource and HBVFWSource, since this does not use Video for Windows.

binary: VapourSource-0.0.4.zip
sourcecode: https://github.com/chikuzen/VapourSource/

requirements:
-avisynth2.6/Avisynth+r1569 or greater
-vapoursynth r30 or later
-Microsoft Visual C++ 2015 Redistributable Package
-Windows Vista sp2 or later



EDIT: 2016-05-07 update to 0.0.4

[sneaker_ger]

Thx.

P.S.: you'd usually want to put fmtc.bitdepth at the end of your script (referring to your screenshot)

[pbristow]

OOH! What a clever idea! Allows us to combine the best of both worlds (in a limited but still bound-to-be-useful fashion), and provides an easy way to start tinkering with VS for us old-fashioned folks who haven't quite dared tackle it yet.

[Chikuzen]

update to 0.0.2

* fix vertical flip issue on COMPATBGR32.
* allow to input RGB24 clip.

[Chikuzen]

update to 0.0.4

- VS2010 to VS2015
- update avisynth.h, VapourSynth.h and VSScript.h
- add 64bit binary

[MysteryX]

Does this allow to load a x64 Vapoursynth script within a x86 Avisynth script?

[jackoneill]

Originally Posted by MysteryX

Does this allow to load a x64 Vapoursynth script within a x86 Avisynth script?

Nope.

32 bit Avisynth -> 32 bit VapourSynth
64 bit Avisynth -> 64 bit VapourSynth

(It links to VSScript.dll.)

[Boulder]

Is it possible to use Vapoursource so that the Vapoursynth part gets the video data from the Avisynth part?

Something like this:

DGSource("C:\Share\av2004.dgi",cb=12,cl=8,cr=8)
clp = QTGMC("very slow")
vs = """
from vapoursynth import core
clp = core.cas.CAS(clp, sharpness=0.25)
"""
VSEval(source=vs)

[DJATOM]

Not really. But you can use avsw.Eval inside vapoursynth to process something by avs script (declaring inputs from vapoursynth that can be used inside avisynth block of code) and then output result into vapoursynth.
clip = core.your.Source(file)
avs_script_part = """
clip
your avs code here
"""
clip2 = core.avsw.Eval(avs_script_part, clips=[clip], clip_names=["clip"])
clip2.set_output()

[Myrsloik]

Originally Posted by Boulder

Is it possible to use Vapoursource so that the Vapoursynth part gets the video data from the Avisynth part?

Something like this:

DGSource("C:\Share\av2004.dgi",cb=12,cl=8,cr=8)
clp = QTGMC("very slow")
vs = """
from vapoursynth import core
clp = core.cas.CAS(clp, sharpness=0.25)
"""
VSEval(source=vs)

Now I'm curious why you want to mix things. Why not abandon the avisynth peasants?

[videoh]

DGSource() has native Vapoursynth support so I wonder the same thing.

[Boulder]

MVTools in Avisynth is slightly ahead of the Vapoursynth port, in particular the ability to use a low bitdepth analysis clip for the vectors and process in high bitdepth is a big plus performance-wise. Also the SAD calculation with different chroma weighting is useful.
Are there any caveats in using avsproxy with MVTools (other than that I would have to install the x86 version of Avisynth+ and necessary plugins)?

[ChaosKing]

avsproxy only supports 8bit video, so you'll need to use stacked format for 10, 16, 32 bit video etc. x86 + 8bit only are the only "restrictions" I'm aware of.

EDIT
With avsproxy I mean avsw.Eval()

[Boulder]

Originally Posted by ChaosKing

avsproxy only supports 8bit video

Ah, of course, thank you. That would make things a bit complicated as well.

[ChaosKing]

Well its just 2-3 commands more

In VS you'd use fmtc.stack16tonative() and maybe fmtc.nativetostack16() if you go back to avs
In avs ConvertToStacked()

[Milardo]

Hi, so does this allow one use a vapoursynth script within avisynth? Or is it the other way?

[Reel.Deel]

Originally Posted by Milardo

Hi, so does this allow one use a vapoursynth script within avisynth? Or is it the other way?

VapourSource is for AviSynth and lets you import a VS script. Latest version is here:https://github.com/Beatrice-Raws/VapourSource/releases

VS_AvsReader is the other way around; import an AVS script in VapourSynth. Since VS is able to load AVS plugins, I would think that this plugin is obsolete.