24.08.2020, 21:00
No, that's Avisynth syntax.
And event then I would not recommend write it this way in Avisynth.
In Avisynth I would use something like:
instead.
Vapoursynth is different, Vapoursynth is based on Python and MergeChroma isn't one of the functions that comes with Vapoursynth out of the box.
source: http://www.vapoursynth.com/doc/functions/boxblur.html
source: https://github.com/WolframRhodium/muvsfu...uvsfunc.py
-> Why would you want to use that anyways?
And event then I would not recommend write it this way in Avisynth.
In Avisynth I would use something like:
clip=last
filteredClip = clip
filteredClip = filteredClip.Blur(0, 1.0)
filteredClip = filteredClip.Sharpen(0.7)
MergeChroma(clip, filteredClip)Vapoursynth is different, Vapoursynth is based on Python and MergeChroma isn't one of the functions that comes with Vapoursynth out of the box.
std.BoxBlur(clip clip[, int[] planes, int hradius = 1, int hpasses = 1, int vradius = 1, int vpasses = 1])
Performs a box blur which is fast even for large radius values. Using multiple passes can be used to fairly cheaply approximate a gaussian blur. A radius of 0 means no processing is performed.def MergeChroma(clip1: vs.VideoNode, clip2: vs.VideoNode, weight: float = 1.0) -> vs.VideoNode:
"""Merges the chroma from one videoclip into another. Port from Avisynth's equivalent.
There is an optional weighting, so a percentage between the two clips can be specified.
Args:
clip1: The clip that has the chroma pixels merged into (the base clip).
clip2: The clip from which the chroma pixel data is taken (the overlay clip).
weight: (float) Defines how much influence the new clip should have. Range is 0.0–1.0.
"""-> Why would you want to use that anyways?