Vapoursynth

[Julek]

Originally Posted by lansing

I have a problem with the R59 installer. I have both Python 3.8 and 3.9 installed with 3.9 being the default. But the installer is only able to detect 3.8. I tested R57 and it is able to see both python versions.

Since R58 VS supports only 3.8 OR 3.10.
3.8 is still kept because it is the latest version available for windows 7.

More info: https://github.com/vapoursynth/vapoursynth/issues/858

[lansing]

Originally Posted by Julek

Since R58 VS supports only 3.8 OR 3.10.
3.8 is still kept because it is the latest version available for windows 7.

More info: https://github.com/vapoursynth/vapoursynth/issues/858

The documentation should be updated, as it is still stating 3.9 to be the supported version.

http://www.vapoursynth.com/doc/insta...s-installation

[Julek]

Originally Posted by lansing

The documentation should be updated, as it is still stating 3.9 to be the supported version.

http://www.vapoursynth.com/doc/insta...s-installation

Yes, the site usually takes longer to update, even though it is already updated on GitHub.

[Myrsloik]

R60 RC1

r60:
fixed blankclip crashing when fpsnum or fpsden is 0 despite it being allowed
fixed invalid format ids sometimes being treated as api3 values when passed to resize 
fixed error message frame generation in vfw
fixed writing beyond end out output buffer for audio in vfw
blankaudio now takes an array of channel constants since this better matches how most other functions work
fixed splitchannels crash on certain channel configurations (YomikoR)
added makefulldiff and mergefulldiff, these are versions of makediff and mergediff that don't clamp the difference to half range and instead use a higher precision diff clip
better error messages when filters get unsupported input formats or combinations thereof
freezeframes now accepts empty arrays and simply passes through the source clip
you can directly assign to frame-props
removed all deprecated (and replaced by better versions) functions in python: get_frame_async_raw, get_plugins, get_functions, list_functions, get_format, register_format
fixed convolution output for 9-15 bit material

Note that MakeFullDiff and MergeFullDiff are experimental functions that may be killed off if nobody does fun things with them. That's all.

[Greenhorn]

What's the difference between Make/MergeDiff and Make/MergeFullDiff when using float format? Was that also clamped?

[Myrsloik]

Originally Posted by Greenhorn

What's the difference between Make/MergeDiff and Make/MergeFullDiff when using float format? Was that also clamped?

It's the same for float.

[mastrboy]

Originally Posted by vapoursynth doc

ColorYUV std.Lut/std.Expr Do the adjustment yourself
https://github.com/amichaelt/vapours...isynthcomp.rst

Honestly, this is just too complicated to figure out for me, is there any helper functions available for this?

I tried to understand the code here: https://github.com/AviSynth/AviSynth...ters/color.cpp

But can not figure out how the Lut/expression for off_v is built from those functions...

I'm just trying to do the avisynth equivalent to "coloryuv(off_v=0.5)"

[Myrsloik]

Originally Posted by mastrboy

Honestly, this is just too complicated to figure out for me, is there any helper functions available for this?

I tried to understand the code here: https://github.com/AviSynth/AviSynth...ters/color.cpp

But can not figure out how the Lut/expression for off_v is built from those functions...

I'm just trying to do the avisynth equivalent to "coloryuv(off_v=0.5)"

Add .5 to the third plane of a float format?

Expr(clip, ["", "", "x 0.5 +"])

[mastrboy]

Originally Posted by Myrsloik

Add .5 to the third plane of a float format?

Expr(clip, ["", "", "x 0.5 +"])

Thanks, that works... I have a difficult time properly understanding lut/expr, is there any decent documentation freely available that is recommended for beginners that want to learn?

That only works for 8bit though, I guess ColorYUV scales input values internally... So what is the math to convert 8bit Expr to 16bit?

Edit: nevermind, found a helper function for scaling values between bitdepths: https://github.com/Irrational-Encodi...l/info.py#L129

[Selur]

R60 is released.

fixed blankclip crashing when fpsnum or fpsden is 0 despite it being allowed
fixed invalid format ids sometimes being treated as api3 values when passed to resize
fixed error message frame generation in vfw
fixed writing beyond end out output buffer for audio in vfw
blankaudio now takes an array of channel constants since this better matches how most other functions work
fixed splitchannels crash on certain channel configurations (YomikoR)
added makefulldiff and mergefulldiff, these are versions of makediff and mergediff that don't clamp the difference to half range and instead use a higher precision diff clip
better error messages when filters get unsupported input formats or combinations thereof
freezeframes now accepts empty arrays and simply passes through the source clip
you can directly assign to frame-props
removed all deprecated (and replaced by better versions) functions in python: get_frame_async_raw, get_plugins, get_functions, list_functions, get_format, register_format
fixed convolution output for 9-15 bit material

source: https://github.com/vapoursynth/vapoursynth/releases

Thanks!

Cu Selur

[Yomiko]

Is there a way (with API4) to tell if a clip has "valid" variable format?

[Myrsloik]

Originally Posted by Yomiko

Is there a way (with API4) to tell if a clip has "valid" variable format?

What do you mean by "valid"? If you get an input clip that's variable format it'll always be valid. If a filter returns a frame that doesn't fit the description things will error out.

[Yomiko]

I was thinking about the recently fixed resize issue, where a clip with "dynamic" format might be mistakenly made. Although previewers actually can handle such output nodes, I hope users can be well informed.

[Yomiko]

In the C headers of API 3, VideoFormat is provided as a pointer in VSVideoInfo, effectively preventing me from creating a var format clip in a filter. Since API 4 it has been changed in the C header, but in python it remains to be None when the clip format is variable. Do you have any plan to also change in python?

[Myrsloik]

Originally Posted by Yomiko

In the C headers of API 3, VideoFormat is provided as a pointer in VSVideoInfo, effectively preventing me from creating a var format clip in a filter. Since API 4 it has been changed in the C header, but in python it remains to be None when the clip format is variable. Do you have any plan to also change in python?

Change it to what? I don't understand the question.

[Txico]

Hello there,
As with any new Ubuntu release, I compile VapouSynth and plug-in from scratch. That's a new compiler versions used so it might help (or not).
With a newly installed Ubuntu 22.10 and after compiling VapourSynth and plug-ins I get an error every time I try a vpy script:
Script evaluation failed:
Python exception: attempted relative import with no known parent package

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 2819, in vapoursynth._vpy_evaluate
File "src/cython/vapoursynth.pyx", line 2820, in vapoursynth._vpy_evaluate
File "example.mp4.vpy", line 2, in <module>
import havsfunc as haf
File "/usr/local/lib/python3.10/site-packages/havsfunc.py", line 69, in <module>
import mvsfunc as mvf
File "/usr/local/lib/python3.10/site-packages/mvsfunc.py", line 59, in <module>
from ._metadata import __version__
ImportError: attempted relative import with no known parent package

I know, I know. It suck to be me but, can anyone at least point me in the correct direction?

[Selur]

Have you installed mvsfunc like mentioned over at https://github.com/HomeOfVapourSynthEvolution/mvsfunc or did you just copy the mvsfunc.py file?
If you did the latter, it would explain the issue. (since _metadata.py is missing which includes the __version__-variable)

Cu Selur

[Txico]

Originally Posted by Selur

Have you installed mvsfunc like mentioned over at https://github.com/HomeOfVapourSynthEvolution/mvsfunc or did you just copy the mvsfunc.py file?
If you did the latter, it would explain the issue. (since _metadata.py is missing which includes the __version__-variable)

Cu Selur

I have uninstalled mvsfunc with pip3 uninstall mvsfunc and after that pip3 install git+https://github.com/HomeOfVapourSynthEvolution/mvsfunc as specified in the Git Hub page.
Perhaps there some reboot needed in between? Any cache that needs to be redone? Any other package that needs to be installed like this that I need to know?

Thank you for your quick answer Selur.
Txico

[Txico]

Hello again,

After you pointed me to the mvsfunc issue I have uninstalled it again and then searched for any other mvsfunc file in my filesystem, and guess what... I found one where there should be none.
After deleting it and looking for it again without results this time, installing mvsfunc using pip again gets everything working. Flabbergasted.

Thank you, Cu Selur. That solved the issue.

Txico

[Selur]

Can someone tell me how to translate:

clip.Mt_Convolution(Horizontal=" 1 1 1 ", vertical = " 1 ", u=1, v=1)

my guess atm. is 'clip.std.Convolution(matrix=[ 1 1 1 ], planes= [ 0 ])'
and

MT_Luts(Diff, Diff, mode="med", pixels = " 0 0 1 0 -1 0 " ,  expr = " X Y - X Y - X Y - abs 1 + * X Y - abs 1 + "+THR+" 1 >= "+THR+" 0.5 ^ "+THR+" ? + / - 128 +", u=1,v=1)

(no clue)
and

Mt_AddDiff(Blurred, ReconstructedMedian)

to Vapoursynth? (Diff, Blurred, ReconstructedMedian are vs.Videonode and THR is a string-representation of an int)

Thanks!

Cu Selur