VapourSynth Editor

[Mystery Keeper]

"Failed to get the script output node." - this is an expected error, which I described before. Your script has no output node.
"QWidget::insertAction: Attempt to insert null action" - this is more interesting. Probably a harmless bug in recent files management. I'll look into it.

[dontrythisathome]

"Failed to get the script output node." - this is an expected error, which I described before. Your script has no output node.
"QWidget::insertAction: Attempt to insert null action" - this is more interesting. Probably a harmless bug in recent files management. I'll look into it.

So, what can i do for now ?

[Mystery Keeper]

Write a script that actually outputs something?

[dontrythisathome]

YEAHHHHH !!! FINALLY WORKED !!!
THANKS FOR THE HUGE SUPPORT !!!

Here the snapshot:
<removed>

[lansing]

requesting a drag and drop to open file function, right now the drag and drop function only act as if the user is adding the file to the script.

[Mystery Keeper]

Ugh. I didn't even know drag and drop worked with files. I'm planning to implement a snippets system. There will be snippets for files dropping too. But what kind of drag and drop do you mean?

[lansing]

Ugh. I didn't even know drag and drop worked with files. I'm planning to implement a snippets system. There will be snippets for files dropping too. But what kind of drag and drop do you mean?

Like drag and drop to open a new vpy file

[Mystery Keeper]

Sure. Though double-clicking is faster. But considering how we have to use two versions for now, I see how it can be useful.

[Are_]

Hi there,

Could you please add a shortcut for comment/uncomment lines and make it accessible through Hotkeys page to this awesome editor? :)

[Mystery Keeper]

Yes, sure. Also, we need a line duplication hotkey.
But not until I finally solve the chroma upsampling issues >_< *bangs his head on the table*

Meanwhile everyone feel free to suggest code editing features. It might the the next thing I concentrate on.

[Mystery Keeper]

Could you please make the editor show the call tips as well when the users type any character within the filter's parenthesis?
:thanks:
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 (http://forum.doom9.org/showthread.php?t=171334) 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]

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]

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]

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]

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

[Myrsloik]

It's a bug in vapoursynth. I forgot that stof() is locale dependent. The next version will correctly always use a point as the decimal separator.

[Are_]

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

Ouch, yes sir. Launching it with "LANG=C vsedit" makes it work as expected.

But should be a better workaround for this, right? :/

EDIT: Ok, you beat me to it, nice to know. :)

[Myrsloik]

Here are updated binaries (https://www.dropbox.com/s/n3svolmpvqogwiy/vsedit_R27_fix.7z?dl=1) with a small fix to work with VapourSynth R27.

Simply overwrite the exe files in the official packages.

[metyo]

vsedit :
VapourSynth plugins manager: Failed to get pointer to the plugin Plugin1!

problem solved with recompile the latest git

ArchLinux 64bit

thanks Myrsloik sl1pkn07 and everyone

metyo

[~ VEGETA ~]

I have this issue for quite a long time:

Failed to evaluate the script:
Python exception: No attribute with the name ffms2 exists. Did you mistype a plugin namespace?
Traceback (most recent call last):
File "vapoursynth.pyx", line 1467, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:24719)
File "C:/Users/VEGETA/Desktop/Untitled.vpy", line 5, in <module>
File "vapoursynth.pyx", line 1088, in vapoursynth.Core.__getattr__ (src\cython\vapoursynth.c:18921)
AttributeError: No attribute with the name ffms2 exists. Did you mistype a plugin namespace?

I am using Windows 7 x64 on a dedi server. I installed VS-R27 from the official binaries. Looks like it doesn't auto-load anything.

I've put ffms2.dll (and index..) in plugins32 and in core32/plugins but still doesn't get it. I also tried loading it manually but didn't work! it says it can not load it.

However, before that... I tried to print the version but didn't work on the editor while worked well in the shell itself. it wrote that it couldn't detect plugins1,2,3,4... I guess this is the main problem.

I tried putting the plugins' directory manually into the editor but still no use.

I hope you can help.

thanks

[sneaker_ger]

Are you using the 32 bit versions of everything, including the editor, player, etc.? Which ffms2 version are you using? (Try this one (http://forum.doom9.org/showpost.php?p=1724748&postcount=2088).)

[~ VEGETA ~]

I am using 32 bit of everything including ffms2. I tried the one you posted but no use. maybe it is a python issue.

[~ VEGETA ~]

Just tried it on my laptop, Windows 7 x86... Same issue.

I use this script:

import vapoursynth as vs
core = vs.get_core()
a= core.std.blankclip()
a.set_output()

This is the result:

Failed to evaluate the script:
Python exception: There is no function named blankclip
Traceback (most recent call last):
File "vapoursynth.pyx", line 1467, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:24719)
File "", line 3, in <module>
File "vapoursynth.pyx", line 1247, in vapoursynth.Plugin.__getattr__ (src\cython\vapoursynth.c:21557)
AttributeError: There is no function named blankclip


when using the Python shell IDE itself, all goes right until I write:

a=core.std.blankclip()


it outputs:

Traceback (most recent call last):
File "<pyshell#9>", line 1, in <module>
a = core.std.blankclip()
File "vapoursynth.pyx", line 1247, in vapoursynth.Plugin.__getattr__ (src\cython\vapoursynth.c:21557)
AttributeError: There is no function named blankclip

Now, when I put this in the editor:

import vapoursynth as vs
core = vs.get_core()
print(core.version())

I get:

Failed to get the script output node.

___

Observing that, my guess is:

1- It doesn't recognize/use the .std stuff, only core. (no libs loaded)?

2- Something is wrong with the editor as it can not even show the version (while the python IDE can).

looking forward to your help.

[colours]

core.std.BlankClip

[~ VEGETA ~]

I downloaded the fixed exe from previous post and it works now.

Still, another issue... which is: it doesn't load any native plugins like ffms2 and flash3kyuu. what to do?

here is my script:

import sys
import vapoursynth as vs
core = vs.get_core()
core.std.LoadPlugin('D:\\plugins32\\ffms2.dll')
core.std.LoadPlugin('D:\\plugins32\\flash3kyuu_deband.dll')
last = core.std.BlankClip()
last = core.f3kdb.F3kdb(last, y=49, output_depth=10, dither_algo=2)[:10]


last.set_output()

[Are_]

last = core.f3kdb.Deband(last, y=49, output_depth=10, dither_algo=2)[:10]

Maybe you should read the documentation more carefully.

[~ VEGETA ~]

last = core.f3kdb.Deband(last, y=49, output_depth=10, dither_algo=2)[:10]

Maybe you should read the documentation more carefully.

OK, but this is not really an issue as the plugin itself can not be loaded as a native plugin. If it is about syntacs, it would be easy.

TL;DR: I have a problem of loading native plugins such as ffms2 and f3kdb. They work nice when loading them as avs plugins not native.

[foxyshadis]

Your script shows you loading them natively, though; avisynth loading is core.avs.LoadPlugin(). Ohhhh, I get it, you assume you're loading an avisynth plugin... both of those plugins include both avisynth and vapoursynth in one dll. You're already done!

Just remember that VapourSynth is case sensitive from here out and you'll be ok.

[~ VEGETA ~]

Your script shows you loading them natively, though; avisynth loading is core.avs.LoadPlugin(). Ohhhh, I get it, you assume you're loading an avisynth plugin... both of those plugins include both avisynth and vapoursynth in one dll. You're already done!

Just remember that VapourSynth is case sensitive from here out and you'll be ok.

I know how to load natively and load them as avs. I know too that they are the same dll. I just stated that loading them natively fails while loading them as avs succeeds.

[dontrythisathome]

I'm using Manjaro Linux 3.18.20-1, vapoursynth from git and just after the last update of Manjaro it prompts me this error when I try to check or preview the script. Sometimes it doesn't do anything at all and sometimes does only one of the two operation above ( check or preview ), otherwise it crashes with any sort of script, from the simplest to the one more complex.

Here is what gdb prompted me ( i'm not a computer programmer so I surely didn't debug it correctly )

(gdb) start
Temporary breakpoint 1 at 0x415610
Starting program: /home/Vapoursynth/vap-editor/build/release-64bit-gcc/vsedit
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Temporary breakpoint 1, 0x0000000000415610 in main ()
(gdb) continue
Continuing.
QWidget::insertAction: Attempt to insert null action
[New Thread 0x7fffea8e1700 (LWP 6738)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7de4045 in do_lookup_x () from /lib64/ld-linux-x86-64.so.2
(gdb) continue
Continuing.
[Thread 0x7fffea8e1700 (LWP 6738) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists

Should I report the problem to Manjaro devs also ?

[jackoneill]

Compile a debug build and then try to reproduce the crash with that. After the segmentation fault, type 'bt full' and paste the output.

[dontrythisathome]

Sorry for being late, the debug version was built in another directory and I couldn't find it at first ! So stupid I am.

Anyway, here is the output.

gdb vs*
Excess command line arguments ignored. (vsedit.svg)
GNU gdb (GDB) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from vsedit-debug-64bit-gcc...done.
"/home/Vapoursynth/vap-editor/build/debug-64bit-gcc/vsedit.ico" is not a core dump: File format not recognized

(gdb) start
Temporary breakpoint 1 at 0x46bab2: file ../src/main.cpp, line 7.
Starting program: /home/Vapoursynth/vap-editor/build/debug-64bit-gcc/vsedit-debug-64bit-gcc
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffe768) at ../src/main.cpp:7
7 QApplication application(argc, argv);
(gdb) continue
Continuing.
QWidget::insertAction: Attempt to insert null action
[New Thread 0x7fffea8e1700 (LWP 11972)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7de4045 in do_lookup_x () from /lib64/ld-linux-x86-64.so.2
(gdb) bt full
#0 0x00007ffff7de4045 in do_lookup_x () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#1 0x00007ffff7de4d3f in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#2 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#3 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#4 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#5 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#6 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#7 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
---Type <return> to continue, or q <return> to quit---
#8 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#9 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#10 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#11 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#12 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#13 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#14 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#15 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#16 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#17 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#18 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#19 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#20 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#21 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#22 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#23 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
---Type <return> to continue, or q <return> to quit---
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#24 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#25 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#26 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#27 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#28 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#29 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#30 0x00007ffff7de5213 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
---Type <return> to continue, or q <return> to quit---q
Quit
(gdb) continue
Continuing.
[Thread 0x7fffea8e1700 (LWP 11972) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.


Typeing <return> seemed to have no end and prompt the same error, so i cut short the output.

[jackoneill]

Typeing <return> seemed to have no end and prompt the same error, so i cut short the output.

You should probably keep at it until it stops asking.

[dontrythisathome]

Sorry, could check again only at this time of day.

The output was too long for Doom9's text box.

Here's the link on pastebin: link (http://pastebin.com/kymA4Kyr)

[foxyshadis]

Looking for that error I found one copy-paste bug in previewdialog.cpp:869 (m_pPreviewContextMenu->addAction(m_pActionSaveSnapshot); should be m_pPreviewContextMenu->addAction(m_pActionFrameToClipboard);). Try changing that and see if it works.