VapourSynth Editor

[Mystery Keeper]

I present you a cross-platform editor for VapourSynth scripts.

VapourSynth Editor r19 64bit (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/VapourSynthEditor-r19-64bit.7z)
Source code (https://bitbucket.org/mystery_keeper/vapoursynth-editor)
OSX distribution by l33tmeatwad (https://bitbucket.org/l33tmeatwad/vapoursynth-editor/downloads)

I would really appreciate if you contribute icons for the project. That includes application icon (SVG which scales well to 16x16) and buttons/menu icons (16x16 PNG).

I also encourage users to explore the settings. If you keep plugins in non-standard paths - add the paths to have syntax highlighting and autocompletion. Take a look at the settable hotkeys, adjust them as you like and use them - they're really handy for switching preview modes and such.

[zerowalker]

Wow, just searched for this like 2 days ago or something, will try it out, thanks

[Mystery Keeper]

R2 is out, fixing some minor files handling issues.

[lansing]

I played around with it a little, the design seem pretty neat, it's good to have handy functions as a buttons.

A few requests I can think of right now, can you add a bookmark function on the timeline, as well as a live feedback of the color value of the pixel where the mouse cursor points to. And the font size on the timeline is too small. The seeking cursor is too small too.

[jmac698]

Totally second that, I requested the same feature for AvsP and it was implemented. Basically, AvsP represents all the common requested features so I'd copy that.

[Mystery Keeper]

I played around with it a little, the design seem pretty neat, it's good to have handy functions as a buttons.

A few requests I can think of right now, can you add a bookmark function on the timeline, as well as a live feedback of the color value of the pixel where the mouse cursor points to. And the font size on the timeline is too small. The seeking cursor is too small too.
I'll think about bookmarks, but likely not before I implement some other features. Timeline font size will be customizable in future. As will be editor styles. Seeking cursor is too small for what? You don't need to aim for it to drag it. You can just click anywhere on the timeline. You won't jump to another frame until you release the mouse key. Now color under cursor is something I don't know how to approach. Most times the video you're working on is YUV with chroma subsampled. So, what value should be displayed?

[Myrsloik]

Here are two screenshots of the awesomeness:
http://www.vapoursynth.com/wp-content/uploads/2014/08/vsedit1.png
http://www.vapoursynth.com/wp-content/uploads/2014/08/vsedit2.png

[Mystery Keeper]

I also encourage users to explore the settings. If you keep plugins in non-standard paths - add the paths to have syntax highlighting and autocompletion. Take a look at the settable hotkeys, adjust them as you like and use them - they're really handy for switching preview modes and such.

[jmac698]

This was solved in AvsP with customizable tags that output to a status area, %rgb to convert anything to rgb, %auto to display in the native values of whatever colourspace the video is in, and %yuv to display as yuv values. Conversion is a bit of a problem so you could use the convention Avisynth does, like pc.601 or pc.709 etc.

But if you could do just one thing now - I'd say auto would work for me. If I need to see a value in rgb, I can convert the video itself temporarily.

[Mr Alpha]

Looks nice!

Bug report: If you drag the window from one screen to the other it crashes.

[Mystery Keeper]

Looks nice!

Bug report: If you drag the window from one screen to the other it crashes.

It shouldn't, and it doesn't for me. What is your OS? Your video drivers? Are you using any GPU filters?

[Mr Alpha]

It shouldn't, and it doesn't for me. What is your OS? Your video drivers? Are you using any GPU filters?
Windows 8.1 Pro 64bit
GeForce 340.52
No filters.

[Mystery Keeper]

Windows 8.1 Pro 64bit
GeForce 340.52
No filters.

My specs are the same, I have two monitors, and can't reproduce it. Please describe all your steps from the start of program to the crash and give me your script.
Update: Works perfectly well on dual-screen clean virtual machine too.

[Mr Alpha]

Steps to reproduce:


Double-click vsedit.exe to start the editor
Drag to secondary screen
Crash


The only script I have are the two lines it starts with.

EDIT: I am also using the 64 bit version of the editor if that makes a difference.

[Mystery Keeper]

Sorry, but I can not reproduce it.

[Mystery Keeper]

R3 is out:
-Fixed zoom ratio changed to real number.
-New line autoindentation.

[RTW47]

auto-indentation don't seem to work in r3 (maybe it is also possible to show white spaces and TAB's)

[Mystery Keeper]

auto-indentation don't seem to work in r3 (maybe it is also possible to show white spaces and TAB's)Autoindentation only indents new line to match the previous. It won't really indent lines on its own according to Python syntax. Are new lines inserted with the same indentation as previous one for you?

Dear users, please understand that this editor will not have any serious Python code analysis in near future.

[RTW47]

#EDIT:. Confirmed. Auto-indentation works, but in a manner user did not initially expected (blush)

[digitall.h]

Sorry me for these very basic questione.
:o
Binaries are just for windows systems, aren't they?.

Can VS Editor be built under Linux?. Dependencies?.
As it is using QT5 I hope it is cross platform, isn't it?.
In source I don't find any make file.
There's an VS version in src folder, does VS Editor installation also install VS?.
:)

[Mystery Keeper]

Sorry me for these very basic questione.
:o
Binaries are just for windows systems, aren't they?.

Can VS Editor be built under Linux?. Dependencies?.
As it is using QT5 I hope it is cross platform, isn't it?.
In source I don't find any make file.
There's an VS version in src folder, does VS Editor installation also install VS?.
:)

Yes, you can build it in Linux with installed developer's packages of Qt5. You simply do:
cd <pro directory>
qmake
make
The program will be built in "build" directory.
You do need to build and install VapourSynth before that. The editor itself doesn't require installation.
The directory "src/vapoursynth" IS NOT VapourSynth source code, but collection of classes in the editor used for direct interaction with VapourSynth. So no, the editor does not build or install VapourSynth.

[digitall.h]

:thanks:

I'm not very good in working with source, I prefer binaries...
:eek::rolleyes:

With the help of users in this forum I managed to install Vapoursynth.
I'll try with VS Editor.

[lansing]

I'll think about bookmarks, but likely not before I implement some other features. Timeline font size will be customizable in future. As will be editor styles. Seeking cursor is too small for what? You don't need to aim for it to drag it. You can just click anywhere on the timeline. You won't jump to another frame until you release the mouse key. Now color under cursor is something I don't know how to approach. Most times the video you're working on is YUV with chroma subsampled. So, what value should be displayed?


the color value format to be display can be rgb like "rgb(20,128,40)" and in hex like "#ccccc".

As for the seek bar, right now you have to click inside that tiny white bar in order to trigger the seek, in which 2 out of 5 times I would miss it.

[Mystery Keeper]

the color value format to be display can be rgb like "rgb(20,128,40)" and in hex like "#ccccc".

As for the seek bar, right now you have to click inside that tiny white bar in order to trigger the seek, in which 2 out of 5 times I would miss it.
Click on the preview area. It effectively steals the focus from any widget that hijacks the keyboard input and allows seeking.
The color question is not how to display it, but "how would you retrieve the pixel color when chroma is subsampled?"

[Myrsloik]

Click on the preview area. It effectively steals the focus from any widget that hijacks the keyboard input and allows seeking.
The color question is not how to display it, but "how would you retrieve the pixel color when chroma is subsampled?"

Grab it from the clip converted to the closest not subsampled format? Very easy to do and then show both raw and rgb values.

[Mystery Keeper]

Grab it from the clip converted to the closest not subsampled format? Very easy to do and then show both raw and rgb values.
Oh. That would do. Thanks for idea.

[dontrythisathome]

Hi all,

i've been looking for an alternative to Avisynth on Linux so, i run into vapoursynth.

I've immediately searched for a suitable editor and here i am.

I've tried to build vapoursynth-editor with the instruction above: cd <pro directory>
qmake
make

but after typing make, the command output stop at this:

/usr/lib/x86_64-linux-gnu/qt5/bin/uic ../src/settings/settingsdialog.ui -o ../generated/ui/ui_settingsdialog.h
/usr/lib/x86_64-linux-gnu/qt5/bin/uic ../src/preview/previewdialog.ui -o ../generated/ui/ui_previewdialog.h
/usr/lib/x86_64-linux-gnu/qt5/bin/uic ../src/mainwindow.ui -o ../generated/ui/ui_mainwindow.h
g++ -c -m64 -pipe -O2 -fexpensive-optimizations -funit-at-a-time -std=c++11 -O2 -w -D_REENTRANT -fPIE -DNDEBUG -DQT_NO_DEBUG
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/share/qt5/mkspecs/linux-g++-64 -I. -I/usr/include/qt5 -I/usr/include/qt5/QtWidgets
-I/usr/include/qt5/QtGui -I/usr/include/qt5/QtCore -I../generated/moc -I../generated/ui -o ../generated/obj/helpers.o
../src/common/helpers.cpp

g++ -c -m64 -pipe -O2 -fexpensive-optimizations -funit-at-a-time -std=c++11 -O2 -w -D_REENTRANT -fPIE -DNDEBUG -DQT_NO_DEBUG
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/share/qt5/mkspecs/linux-g++-64 -I. -I/usr/include/qt5 -I/usr/include/qt5/QtWidgets
-I/usr/include/qt5/QtGui -I/usr/include/qt5/QtCore -I../generated/moc -I../generated/ui -o ../generated/obj/settingsmanager.o
../src/settings/settingsmanager.cpp

../src/settings/settingsmanager.cpp: In constructor ‘SettingsManager::SettingsManager(QObject*)’:

../src/settings/settingsmanager.cpp:101:4: error: ‘GenericConfigLocation’ is not a member of ‘QStandardPaths’

QStandardPaths::GenericConfigLocation) + SETTINGS_FILE_NAME;
^
../src/settings/settingsmanager.cpp: In member function ‘bool SettingsManager::setPortableMode(bool)’:
../src/settings/settingsmanager.cpp:132:3: error: ‘GenericConfigLocation’ is not a member of ‘QStandardPaths’
QStandardPaths::GenericConfigLocation);
^
make: *** [../generated/obj/settingsmanager.o] Errore 1

[Mystery Keeper]

Weird. Maybe "GenericConfigLocation" was introduced in newer Qt5 version than the one you've got? Can you upgrade it? If not - replace "GenericConfigLocation" with "ConfigLocation".

[dontrythisathome]

Weird. Maybe "GenericConfigLocation" was introduced in newer Qt5 version than the one you've got? Can you upgrade it? If not - replace "GenericConfigLocation" with "ConfigLocation".

i used this ppa to install Qt5 on my Ubuntu 12.04 LTS because there is no official repository for Qt5 library on 12.04 LTS. I didn't find it on synaptic.

https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/ppa

and they say Qt5 is partially supported in version 12.04 LTS. Could be this the problem ?

Anyway i've change what you tell me to change and now it prompt me this:

../src/settings/itemdelegateforhotkey.cpp:1:28: fatal error: QKeySequenceEdit: File o directory non esistente
#include <QKeySequenceEdit>
^
compilation terminated.
make: *** [../generated/obj/itemdelegateforhotkey.o] Errore 1

Could this also be a problem because Qt5 is not fully supported on 12.04 LTS so they've change some include directories ?

[Mystery Keeper]

No idea, honestly. To me it seems that your version of Qt5 is incomplete. You could try and build it from the sources. What "Qt5 is partially supported in version 12.04 LTS" means is a mystery to me. QKeySequenceEdit was introduced in Qt5.2.

[dontrythisathome]

No idea, honestly. To me it seems that your version of Qt5 is incomplete. You could try and build it from the sources. What "Qt5 is partially supported in version 12.04 LTS" means is a mystery to me. QKeySequenceEdit was introduced in Qt5.2.

I'll try to compile QT5 from source then and remove the ppa, that, after all, i discover install Qt 5.0.2 only on Ubuntu 12.04 LTS and not Qt 5.2 and later.

EDIT [18.08.2014]: I've manage to build vapoursynth-editor. Now, i run it and it prompt me this error: VapourSynth plugins manager: Failed to load vapoursynth library!
Please set up the library search paths in settings.

http://111.imagebam.com/download/ioSujP8COMlRA2wW6G-e6Q/34585/345844428/snap-1.png

and when i do not use any plugin it prompt me this:

Failed to initialize VapourSynth

I don't understand where i fail.
I followed this post to build vapoursynth and FFMS2: LINK (https://forum.doom9.org/showpost.php?p=1643069&postcount=947)

Then i build vapoursynth-editor.
Since from vapoursynth ./waf configure the PREFIX is set to " /usr/local/ ", LIBDIR to " PREFIX/lib " and PLUGINDIR to "LIBDIR/vapoursynth", i don't understand why it can't load them. I also set the vapoursynth.conf file as it explain here: LINK (http://www.vapoursynth.com/doc/autoloading.html) since XDG_CONFIG_HOME is not defined.

Any suggestion ?

[foxyshadis]

Can you test 14.04 LTS, perhaps in a VM? It might be time to transition toward that, if it works.

[Mystery Keeper]

I'll try. I tested it in Mint 17 so far.

[Are_]

Any suggestion ?

The search path for "vapoursynth library" is wrong in the screenshot you posted, it should be "/usr/local/lib".

[dontrythisathome]

The search path for "vapoursynth library" is wrong in the screenshot you posted, it should be "/usr/local/lib".

oh, yes, my mistake.

Here's the change, but it still doesn't recognize the vapoursynth plugin path.

http://109.imagebam.com/download/ny5RW5yN5baBw3BZXVeWoA/34603/346028068/snap-2.png

[Mystery Keeper]

You mean you don't get syntax highlighting and autocompletion for the plugins you've got in the path?

[dontrythisathome]

You mean you don't get syntax highlighting and autocompletion for the plugins you've got in the path?

yes.
This is the output it gives me

VapourSynth plugins manager: Failed to load vapoursynth library!
Please set up the library search paths in settings.

Although i set the correct path, didn't I ?

[Mystery Keeper]

The truth is you shouldn't need to set the library search path in Linux at all. In Windows too since I've added autodetection. For some reason vsedit can not find VapourSynth library. What name does it have in your build?

[dontrythisathome]

The truth is you shouldn't need to set the library search path in Linux at all. In Windows too since I've added autodetection. For some reason vsedit can not find VapourSynth library. What name does it have in your build?


This is the build name of vapoursynth

vapoursynth_24R-r1079-1_amd64

Is this what you're talking about, isn't it ?

[Mystery Keeper]

Woah! No wonder it can not find the library. Its name in Linux is expected to be libvapoursynth.so. Must be some of Myrsloik's recent changes.

[Myrsloik]

Woah! No wonder it can not find the library. Its name in Linux is expected to be libvapoursynth.so. Must be some of Myrsloik's recent changes.

I didn't change anything. That sounds more like a package name.

[dontrythisathome]

Woah! No wonder it can not find the library. Its name in Linux is expected to be libvapoursynth.so. Must be some of Myrsloik's recent changes.

Wait, you mean the build name of the package or the name of the library .so ; because if it is .so file what you are intending, is the same as you said, that is libvapoursynth.so

EDIT: i tried to launch vspipe from terminal and prompt me this: vspipe: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/local/lib/libvapoursynth.so)

Could be this the problem ?

[Mystery Keeper]

i tried to launch vspipe from terminal and prompt me this: vspipe: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/local/lib/libvapoursynth.so)

Could be this the problem ?
Yes, definitely.

[dontrythisathome]

Yes, definitely.

ok. correct LD_LIBRARY_PATH and now vspipe works from terminal and i also rebuilt vapoursynth-editor but it still not working.

Should i rebuild vapoursynth too ?

[Mystery Keeper]

What exactly is not working?

[dontrythisathome]

What exactly is not working?

I just write down in the editor this simple script:

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

and it prompt me this again:

VapourSynth plugins manager: Failed to load vapoursynth library!
Please set up the library search paths in settings.

[Mystery Keeper]

It still can't load the library. Do try to rebuild VapourSynth. There's an error in your script. No variable c. It should be "print(core.version())". It still will not print you anything. The editor doesn't redirect stdout. It expects the script to have ouput video node.

[dontrythisathome]

It still can't load the library. Do try to rebuild VapourSynth. There's an error in your script. No variable c. It should be "print(core.version())". It still will not print you anything. The editor doesn't redirect stdout. It expects the script to have ouput video node.

I rebulit VapourSynth and then i rebuilt vapoursynth-editor.

Still don't load the library and syntax highlighting and autocompletion works only with existing variable though.

[Mystery Keeper]

If syntax highlighting works with "std" namespace plugins - then library is successfully loaded. Does it still give you the message that it couldn't be loaded?

[dontrythisathome]

If syntax highlighting works with "std" namespace plugins - then library is successfully loaded. Does it still give you the message that it couldn't be loaded?

Yes, i discover another personal issue.

To correct this error: vspipe: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/local/lib/libvapoursynth.so)

I had to update LD_LIBRARY_PATH with the PATH where is located GCC library since i've installed latest GCC.

After updated the LD_LIBRARY_PATH, trough the terminal vspipe worked.
But when i close the terminal and open a new one, it's like the previous command was cancelled; so, i re-exported the PATH and launched vsedit from terminal, trying to run the simple script, but a new error prompted in vseditor

Failed to get the script output node.

This instead, is what i had from ubuntu terminal



QWidget::insertAction: Attempt to insert null action [ WHEN I OPEN VSEDIT FROM TERMINAL ]

VapourSynth Video Processing Library
Copyright (c) 2012-2014 Fredrik Mellbin
Core r24
API r3 [WHEN I TRIED TO RUN THE SCRIPT]