VapourSynth Editor

[Mystery Keeper]

Originally Posted by digitall.h

Sorry me for these very basic questione.

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]

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


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

[lansing]

Originally Posted by Mystery Keeper

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]

Originally Posted by lansing

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]

Originally Posted by Mystery Keeper

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]

Originally Posted by Myrsloik

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]

Originally Posted by 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".

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-te...ive/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]

Originally Posted by 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.

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.

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

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 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_]

Originally Posted by dontrythisathome

Any suggestion ?

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

[dontrythisathome]

Originally Posted by Are_

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.

[Mystery Keeper]

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

[dontrythisathome]

Originally Posted by Mystery Keeper

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]

Originally Posted by 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?

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.