VapourSynth Editor

[Mystery Keeper]

Originally Posted by HolyWu

Could you please make the editor show the call tips as well when the users type any character within the filter's parenthesis?

Yes, I can. Just realized that's the way I should have done it from the beginning. Autocompletion for function name only and a tooltip for the arguments.

[Mystery Keeper]

r4 is finally out with few fundamental changes.
Custom font is not embedded.
Preview is now done completely internally. ALL formats recognized by VapourSynth are supported.
Chroma upsampling is done using zimg library, which adds some little quirks.
Make sure you explore the new settings in preview window and use the right colorspace conversion matrix for each script.

Also, I think this thread deserves to be sticky.

[lansing]

the 32bit version crash on start, and where should we install the zimg library? The original post didn't say anything.

[Mystery Keeper]

Originally Posted by lansing

the 32bit version crash on start, and where should we install the zimg library? The original post didn't say anything.

zimg library code is integrated, so you don't need to install it for the editor. It doesn't crash for me. I'll test 32bit version in virtual machine again.
Upd: Test works perfectly fine. Try to download and install VapourSynth R25 again. There were versions that made the editor crash.

[lansing]

Originally Posted by Mystery Keeper

zimg library code is integrated, so you don't need to install it for the editor. It doesn't crash for me. I'll test 32bit version in virtual machine again.
Upd: Test works perfectly fine. Try to download and install VapourSynth R25 again. There were versions that made the editor crash.

Yup I just found that out, installed r25 and the problems went away. You may want to modify the error message to inform the users to use the correct vapoursynth version.

[Mystery Keeper]

Modify which error message? It doesn't really care for what VS library it uses as long as API is compatible. The crash was caused by "tcmalloc" library that VS now uses overriding standard functions.

[lansing]

When I was using the outdated vapoursynth version before, there's a warning message saying that I need to set up the library folder path.

[Mystery Keeper]

That happened because it couldn't load vapoursynth.dll, which used dynamically linked tcmalloc. That breaks autocompletion and syntax highlighting, but not preview. That error means "I could not find an instance of vapoursynth.dll that I could load".

[Myrsloik]

Originally Posted by lansing

When I was using the outdated vapoursynth version before, there's a warning message saying that I need to set up the library folder path.

The experimental builds don't get their own version so it can't be detected. Experimental versions are so because they may be very broken.

[Are_]

Ok, now I have kind of a problem and I don't know exactly who is the culprit, so I'm going to throw it here.

Whenever I try to preview a script with finesharp on vsedit, it tells me something like:

Failed to evaluate the script:
Python exception: Expr: Failed to convert '9.9' to float
Traceback (most recent call last):
  File "vapoursynth.pyx", line 1480, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:25191)
  File "/home/dani/rule6/stuff/_stuff.py", line 21, in <module>
    f = finesharp.sharpen(clip=src, mode=1, sstr=2)
  File "/usr/lib64/python3.4/site-packages/finesharp.py", line 153, in sharpen
    xyshrp = core.std.Expr(clips=[shrp, core.rgvs.RemoveGrain(clip=shrp, mode=[20])], expr=expr)
  File "vapoursynth.pyx", line 1379, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:23686)
vapoursynth.Error: Expr: Failed to convert '9.9' to float

But I can't see why the code is wrong.

This only happens when Expr is used, it looks like strings get screwed somehow.

vspipe/mpv don't complain about anything, only vsedit does.

Does this make any sense? :/

[Mystery Keeper]

That's a Python error. Something with your expression.

[Are_]

Tell me how this is wrong:

            expr   = 'x x y - 9.9 * +'
            xyshrp = core.std.Expr(clips=[shrp, core.rgvs.RemoveGrain(clip=shrp, mode=[20])], expr=expr)

Also, I have already said it, vspipe and mpv don't throw any error and proces de video correctly.

[Mystery Keeper]

Sorry, missed the part about vspipe not complaining. I really don't know. I'll try to test expr with vsedit.

[Are_]

import vapoursynth as vs

core = vs.get_core()

src = core.std.BlankClip()

def stuff(clip):
    r = core.std.Expr(clips=clip, expr='x 9.9 +')
    return r

r = stuff(src)

r.set_output()

This will fail in vsedit.

[Mystery Keeper]

It doesn't fail for me.

[Are_]

Mmh... then it has something to do with my box (make sure the thing you tested ended with "r.set_output()" because I ninja edited that part ^^U). :/

[Are_]

Well, don't worry, it also works for me on windows, something should be wrong in my end.

[sl1pkn07]

Originally Posted by Are_

import vapoursynth as vs

core = vs.get_core()

src = core.std.BlankClip()

def stuff(clip):
    r = core.std.Expr(clips=clip, expr='x 9.9 +')
    return r

r = stuff(src)

r.set_output()

This will fail in vsedit.

fail for me in linux 64bits, VS 54b97e1

Failed to evaluate the script:
Python exception: Expr: Failed to convert '9.9' to float
Traceback (most recent call last):
  File "vapoursynth.pyx", line 1480, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:25089)
  File "", line 11, in <module>
  File "", line 8, in stuff
  File "vapoursynth.pyx", line 1379, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:23584)
vapoursynth.Error: Expr: Failed to convert '9.9' to float

[Myrsloik]

Are you using a locale where the decimal separator isn't a point?

[sl1pkn07]

I believe is a ','

edit:
oh, yes, change 9.9 with 9,9 now works

thanks for the point

greetings