VapourSynth Editor

[VS_Fan]

And I have a potential bug... When I start the editor the first time and hit F5, the preview loads with no problems. Then I close the preview window and hit F5 again.
Your problem has nothing to do with VS-editor. It´s the way you call get_core() (http://www.vapoursynth.com/doc/apireference.html#vsscript-python)

[Mystery Keeper]

Indeed. You should put core = vs.get_core() in the beginning of your function instead of module.

[Boulder]

I've got an HEVC file I'm trying to open with ffms2 but the preview gives me an error "Resize error 3074: unrecognized transfer characteristics". Is this a Vapoursynth issue or related to the editor?

[Mystery Keeper]

I've got an HEVC file I'm trying to open with ffms2 but the preview gives me an error "Resize error 3074: unrecognized transfer characteristics". Is this a Vapoursynth issue or related to the editor?It is the VapourSynth resize plugin issue. Your HEVC file has transfer characteristics that resize doesn't know, so it can not properly convert the video to RGB for preview.
What you can do:
1) manually set the transfer characteristics property to one resize recognizes; that's a hack, not proper solution;
2) add a resize line in your script that converts the output to CompatRGB format and specify the input transfer characteristics; before encoding - comment out that line;

[l33tmeatwad]

Garbled output in the preview window on OSX is still happening. Last working revision is r10 :-\...

[Boulder]

I tried removing the hotkeys for previous and next bookmark (CTRL + Left, Right) by emptying the field. After clicking on Apply, the program freezes for some time and then after clicking OK, it seems to forget the changes I made.

[Mystery Keeper]

I tried removing the hotkeys for previous and next bookmark (CTRL + Left, Right) by emptying the field. After clicking on Apply, the program freezes for some time and then after clicking OK, it seems to forget the changes I made.The freeze is the result of every setting being saved one by one. But not remembering is a bug. I'll get on that.

[Sm3n]

Now I could make an update of VS, VSE won't load library:

Failed to load vapoursynth script library!
Please set up the library search paths in settings.

I checked but I don't remember what path I used before (if I added any)
Can you please help me to fix it?

[Mystery Keeper]

Now I could make an update of VS, VSE won't load library:

Failed to load vapoursynth script library!
Please set up the library search paths in settings.

I checked but I don't remember what path I used before (if I added any)
Can you please help me to fix it?

Update Python to 3.6, then re-install VS.

[Sm3n]

Update Python to 3.6, then re-install VS.

thx. I did update, re-install VS and VSE and I still get those lines:

Failed to load vapoursynth script library!
Please set up the library search paths in settings.
Failed to evaluate the script.

Why the hell I tried to install HAvsFunc and update VS? I should never touched anything at something working! :/ Especially when linux and english is not your friend...

Edit: after doing "python3.6 setup.py install" I get
Traceback (most recent call last):
File "setup.py", line 7, in <module>
from Cython.Distutils import Extension, build_ext
ModuleNotFoundError: No module named 'Cython'

Can't work, right?

[Are_]

I don't know but, what about the output of these commands?
$ which vspipe
# updatedb & locate libvapoursynth-script.so.0.0.0
Because maybe something is installed in a really wired place, or something is not installed or only god knows what you did there.

[Sm3n]

Cython wasn't install. It is now. Previous version of vapoursynth didn't need it I guess...

I could run "python3.6 setup.py install" properly. and still same error in VSE.

"which vspipe" returns:
/usr/local/bin/vspipe

"updatedb & locate libvapoursynth-script.so.0.0.0" returns:
[1] 57873
/root/vapoursynth/.libs/libvapoursynth-script.so.0.0.0
/usr/local/lib/libvapoursynth-script.so.0.0.0

Is there any path I must add to VSE path settings? under plugins and/or library?

[Are_]

Give it a try with /usr/local/lib/
I never installed vapoursynth to local so I don't know if you need something special set up.

[Mystery Keeper]

thx. I did update, re-install VS and VSE and I still get those lines:

Failed to load vapoursynth script library!
Please set up the library search paths in settings.
Failed to evaluate the script.

Why the hell I tried to install HAvsFunc and update VS? I should never touched anything at something working! :/ Especially when linux and english is not your friend...

Edit: after doing "python3.6 setup.py install" I get
Traceback (most recent call last):
File "setup.py", line 7, in <module>
from Cython.Distutils import Extension, build_ext
ModuleNotFoundError: No module named 'Cython'

Can't work, right?

You should have said you were on Linux.
Have you tried this instruction (http://www.l33tmeatwad.com/vapoursynth101/software-setup)?

[jackoneill]

Cython is only needed when compiling VapourSynth.

You have no need to use setup.py in Linux or OS X. "./autogen.sh; ./configure; make; make install" will compile and install everything. (Add parameters to each step as needed.)

[Sm3n]

Cython is only needed when compiling VapourSynth.

You have no need to use setup.py in Linux or OS X. "./autogen.sh; ./configure; make; make install" will compile and install everything. (Add parameters to each step as needed.)

You should have said you were on Linux.
Have you tried this instruction (http://www.l33tmeatwad.com/vapoursynth101/software-setup)?

Thx guys! Your link helped me a lot.
I've only reinstalled VS & VSE.

By the way, have you a tuto and/or a more recent link for installing this? https://forum.doom9.org/showthread.php?p=1753688#post1753688

[Mystery Keeper]

Thx guys! Your link helped me a lot.
I've only reinstalled VS & VSE.

By the way, have you a tuto and/or a more recent link for installing this? https://forum.doom9.org/showthread.php?p=1753688#post1753688Ask questions in appropriate thread please.

[thetrueavatar]

Hello,
I'm trying to build vapoursynth-editor on my ubuntu 14.0.4LT 32bit.
I have followed the steps defined here:
http://www.l33tmeatwad.com/vapoursynth101/software-setup
I had some problems but achieved to the editor compilation.
However I keep having failure while building the editor:
../src/preview/preview_dialog.cpp: In member function ‘void PreviewDialog::slotPreviewAreaMouseOverPoint(float, float)’:
../src/preview/preview_dialog.cpp:1063:6: warning: declaration of ‘width’ shadows a member of 'this' [-Wshadow]
int width = m_cpVSAPI->getFrameWidth(m_cpFrameRef, 0);
^
../src/preview/preview_dialog.cpp:1064:6: warning: declaration of ‘height’ shadows a member of 'this' [-Wshadow]
int height = m_cpVSAPI->getFrameHeight(m_cpFrameRef, 0);
^
../src/preview/preview_dialog.cpp:1082:10: warning: declaration of ‘x’ shadows a member of 'this' [-Wshadow]
size_t x = frameX >> 1;
^
../src/preview/preview_dialog.cpp: In member function ‘void PreviewDialog::slotProcessPlayQueue()’:
../src/preview/preview_dialog.cpp:1270:25: error: no matching function for call to ‘std::list<Frame>::erase(std::list<Frame>::const_iterator&)’
m_framesCache.erase(it);
^
../src/preview/preview_dialog.cpp:1270:25: note: candidates are:
In file included from /usr/include/c++/4.8/list:64:0,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/tools/qlist.h:50,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/qlist.h:1,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/kernel/qvariant.h:45,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/qvariant.h:1,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/QVariant:1,
from ../generated/ui/ui_preview_dialog.h:12,
from ../src/preview/preview_dialog.h:4,
from ../src/preview/preview_dialog.cpp:1:
/usr/include/c++/4.8/bits/list.tcc:108:5: note: std::list<_Tp, _Alloc>::iterator std::list<_Tp, _Alloc>::erase(std::list<_Tp, _Alloc>::iterator) [with _Tp = Frame; _Alloc = std::allocator<Frame>; std::list<_Tp, _Alloc>::iterator = std::_List_iterator<Frame>]
list<_Tp, _Alloc>::
^
/usr/include/c++/4.8/bits/list.tcc:108:5: note: no known conversion for argument 1 from ‘std::list<Frame>::const_iterator {aka std::_List_const_iterator<Frame>}’ to ‘std::list<Frame>::iterator {aka std::_List_iterator<Frame>}’
In file included from /usr/include/c++/4.8/list:63:0,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/tools/qlist.h:50,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/qlist.h:1,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/kernel/qvariant.h:45,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/qvariant.h:1,
from /opt/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/QVariant:1,
from ../generated/ui/ui_preview_dialog.h:12,
from ../src/preview/preview_dialog.h:4,
from ../src/preview/preview_dialog.cpp:1:
/usr/include/c++/4.8/bits/stl_list.h:1193:7: note: std::list<_Tp, _Alloc>::iterator std::list<_Tp, _Alloc>::erase(std::list<_Tp, _Alloc>::iterator, std::list<_Tp, _Alloc>::iterator) [with _Tp = Frame; _Alloc = std::allocator<Frame>; std::list<_Tp, _Alloc>::iterator = std::_List_iterator<Frame>]
erase(iterator __first, iterator __last)
^
/usr/include/c++/4.8/bits/stl_list.h:1193:7: note: candidate expects 2 arguments, 1 provided
../src/preview/preview_dialog.cpp: In member function ‘void PreviewDialog::slotClearBookmarks()’:
../src/preview/preview_dialog.cpp:1297:30: warning: declaration of ‘result’ shadows a member of 'this' [-Wshadow]
QMessageBox::StandardButton result = QMessageBox::question(this,
^
../src/preview/preview_dialog.cpp: In member function ‘double PreviewDialog::valueAtPoint(size_t, size_t, int)’:
../src/preview/preview_dialog.cpp:1904:9: warning: declaration of ‘x’ shadows a member of 'this' [-Wshadow]
size_t x = a_x;
^
../src/preview/preview_dialog.cpp:1905:9: warning: declaration of ‘y’ shadows a member of 'this' [-Wshadow]
size_t y = a_y;
^
../src/preview/preview_dialog.cpp: In member function ‘QPixmap PreviewDialog::pixmapFromCompatBGR32(const VSFrameRef*)’:
../src/preview/preview_dialog.cpp:1964:6: warning: declaration of ‘width’ shadows a member of 'this' [-Wshadow]
int width = m_cpVSAPI->getFrameWidth(a_cpFrameRef, 0);
^
../src/preview/preview_dialog.cpp:1965:6: warning: declaration of ‘height’ shadows a member of 'this' [-Wshadow]
int height = m_cpVSAPI->getFrameHeight(a_cpFrameRef, 0);
^
make: *** [../generated/obj-release-32bit-gcc/preview_dialog.o] Erreur 1

I'm using Qt 5.8 that I had to build from source. I'm not sure qt is backwardcompatible so maybe it's just a question of version but which one ?
Any help please ? Feel free to ask me any configuration I could provide you.

I have taken source from the git repository and try to build either master or the tag r15

[sl1pkn07]

Try with GCC 6.x.x

[thetrueavatar]

Ok thanks that fixed the problem. I'm a java developper so not used to read c++ compiler version problem :p
Hourra. Will be able to use avsfilter like plugin with editor+preview !

[thetrueavatar]

I have a question that might already been asked but didn't find any response in the search. Is there to open multiple preview so I can compare the result with and without a filter been applied ?

[Are_]

Nope, use std.Interleave or std.StackXXX in your script.

[blaze077]

Is there a setting to enable/disable call tips? It does not seem to provide them on my end. (http://i.imgur.com/6WbDhKn.png)

Thank you.

[Mystery Keeper]

Is there a setting to enable/disable call tips? It does not seem to provide them on my end. (http://i.imgur.com/6WbDhKn.png)

Thank you.Call tips work when you type the function name. You can force the tip by pressing CTRL+SPACE. I know the call tips are awkward and barely useful now. I'll get to them right after I finish a larger and more important feature. Not very soon, sadly.

[blaze077]

Call tips work when you type the function name. You can force the tip by pressing CTRL+SPACE. I know the call tips are awkward and barely useful now. I'll get to them right after I finish a larger and more important feature. Not very soon, sadly.
Ah, I see. I thought the call tips were supposed to be something like in IDLE or AvsPMod. Will be waiting for that release.

Thank you.

[ChaosKing]

Instant crash with vapoursynth R37 when I click on preview. "check script" F6 and benchmarks works.

EDIT
Myrsloik:
The R37 binaries have now been updated. The released ones were unfortunately miscompiled which caused a pile of issues.

works now

[l33tmeatwad]

Still having issues with the latest builds of both this and VapourSynth displaying hte preview window correctly. Anything past VapourSynth r33 output all screenshots with a shade of blue, and any version of VapourSynth Editor past r10 includes visual artifacts in the live previous (however the output screenshots are fine except for being blue...). What can I do to further test this to see exactly what conflict is going on to cause these issues?

Edit: Actual scripts that are encoded from the latest VapourSynth revisions are fine and look normal, I am ONLY experiencing issues with VapourSynth editor.

[Mystery Keeper]

Still having issues with the latest builds of both this and VapourSynth displaying hte preview window correctly. Anything past VapourSynth r33 output all screenshots with a shade of blue, and any version of VapourSynth Editor past r10 includes visual artifacts in the live previous (however the output screenshots are fine except for being blue...). What can I do to further test this to see exactly what conflict is going on to cause these issues?

Edit: Actual scripts that are encoded from the latest VapourSynth revisions are fine and look normal, I am ONLY experiencing issues with VapourSynth editor.Preview image forming is done internally in VapourSynth by invoking "resize" plugin. I set it up to respect colorimetry information in output clip. And that's all I can do about it.

[Myrsloik]

Still having issues with the latest builds of both this and VapourSynth displaying hte preview window correctly. Anything past VapourSynth r33 output all screenshots with a shade of blue, and any version of VapourSynth Editor past r10 includes visual artifacts in the live previous (however the output screenshots are fine except for being blue...). What can I do to further test this to see exactly what conflict is going on to cause these issues?

Edit: Actual scripts that are encoded from the latest VapourSynth revisions are fine and look normal, I am ONLY experiencing issues with VapourSynth editor.

"Being blue"? How blue are we talking about? A light tint or really, really blue?

[l33tmeatwad]

"Being blue"? How blue are we talking about? A light tint or really, really blue?
Really, really blue.

Edit: Images added, the r10 image is what r10 looks like AND is what screenshots output as in later versions too. The r15 image is what the screen looks like in the preview window with r12+

Images: r10 (http://imgur.com/PB9ZUVH) & r15 (http://imgur.com/LVKe4po)

[l33tmeatwad]

Just checking back to see if there is anything I can do or test to possibly get this working again on OSX. I'm not really sure where to start.

[jackoneill]

Just checking back to see if there is anything I can do or test to possibly get this working again on OSX. I'm not really sure where to start.

Start with a simple script containing only BlankClip with a known colour.

[l33tmeatwad]

Start with a simple script containing only BlankClip with a known colour.
I supposed I could have shared that too...solid black comes out royal blue (basically every color comes out with a shade of blue over it, although white is white).

[jackoneill]

I supposed I could have shared that too...solid black comes out royal blue (basically every color comes out with a shade of blue over it, although white is white).

Does it make a difference if the black BlankClip is RGB or YUV?

[l33tmeatwad]

Does it make a difference if the black BlankClip is RGB or YUV?
Depends on the color, but black shows up as blue for both (some other colors vary drastically, for example, 194,40,60 is light blue for RGB and bright pink for YUV).

Edit: I'm using r10 to see the colors, r12+ still have a weird issue on top of the color problem all of them have since VapourSynth r34+.

[jackoneill]

By the way, what happens if you save one of these blue frames as png? Is the png blue as well?

[l33tmeatwad]

By the way, what happens if you save one of these blue frames as png? Is the png blue as well?
Yes, for versions r10 and lower, they preview blue and save as PNG as blue. For versions r12 and above (r11 never compiled, known issue that was patched with r12 iirc) it will preview garbled but export frames blue.

Edit: Side note that i've mentioned before, scripts encode fine through vspipe and ffmpeg, just VSE is doing wonky stuff.

[Mystery Keeper]

Zimg problem. Every preview problem is zimg problem.

[l33tmeatwad]

Zimg problem. Every preview problem is zimg problem.
I'm going to look back at VapourSynth revisions and see what broke the older versions (by checking each revision to find the last working one and look at changes).

Edit: I've found some revisions in VS that have drastically changed how zimg is working and it does relate to the visual problems in past versions. I'm going to move over to that thread to see if that can get resolve and hopefully if it is, it may also resolve the weird issues that later versions of VSE are having as well.

[Myrsloik]

I'm going to look back at VapourSynth revisions and see what broke the older versions (by checking each revision to find the last working one and look at changes).

Edit: I've found some revisions in VS that have drastically changed how zimg is working and it does relate to the visual problems in past versions. I'm going to move over to that thread to see if that can get resolve and hopefully if it is, it may also resolve the weird issues that later versions of VSE are having as well.

Can't reproduce on osx. I used grey blankclip and it looked good.

[l33tmeatwad]

Can't reproduce on osx. I used grey blankclip and it looked good.
So weird, I have 2x Macbook Pros I've tried it on (2010 & 2011), one with OSX 10.12 and the other with 10.11 and both do it. It's clear after testing that the revision after VapourSynth r35 broke everything for these two Macbooks. I have updated zimg to the latest revison and have also tried using the VapourSynth revision through brew as well as doing compiles myself.

[Myrsloik]

So weird, I have 2x Macbooks I've tried it on (2010 & 2011), one with OSX 10.12 and the other with 10.11 and both do it.

Tested on a macbook air 2012 with 10.12. Compiled everything myself when testing.

[l33tmeatwad]

Tested on a macbook air 2012 with 10.12. Compiled everything myself when testing.
Well, I suppose it's about time I formatted one of these machines to see if the problem still persists after that...

[l33tmeatwad]

Update: While working on rebuilding the other machine, I started looking around and testing some things, looks like the monitor display profiles affect with the previews look, particular ones will show the image appear with the blue shade, but others will cause random corruption in the preview.

[cwk]

I'm getting the following message 4 times when loading vsedit on Ubuntu 16.04, which prevents me from using the preview, check script, etc.:

Failed to load vapoursynth script library!
Please set up the library search path in settings.

Based on previous conversations in this thread, my settings are:

VapourSynth library search paths:
/usr/lib/x86_64-linux-gnu
/usr/lib/python3/dist-packages

VapourSynth plugins paths:
/usr/lib/x86_64-linux-gnu/vapoursynth
/usr/share/vsscripts

based on the following:

$ locate vapoursynth
/usr/lib/python3/dist-packages/vapoursynth.so
/usr/lib/x86_64-linux-gnu/libvapoursynth-script.so.0
/usr/lib/x86_64-linux-gnu/libvapoursynth-script.so.0.0.0
/usr/lib/x86_64-linux-gnu/libvapoursynth.so
/usr/lib/x86_64-linux-gnu/vapoursynth

$ locate temporalsoften
/usr/lib/x86_64-linux-gnu/vapoursynth/temporalsoften.so
/usr/lib/x86_64-linux-gnu/vapoursynth/temporalsoften2.so
/usr/share/vsscripts/temporalsoften2.py

I installed using the ppa over the last week.

$ vspipe -v
VapourSynth Video Processing Library
Copyright (c) 2012-2017 Fredrik Mellbin
Core R37
API R3.4
Options: -

Do you have any suggestions for where my config is wrong?

[Mystery Keeper]

I'm getting the following message 4 times when loading vsedit on Ubuntu 16.04, which prevents me from using the preview, check script, etc.:

Failed to load vapoursynth script library!
Please set up the library search path in settings.

Based on previous conversations in this thread, my settings are:

VapourSynth library search paths:
/usr/lib/x86_64-linux-gnu
/usr/lib/python3/dist-packages

VapourSynth plugins paths:
/usr/lib/x86_64-linux-gnu/vapoursynth
/usr/share/vsscripts

based on the following:

$ locate vapoursynth
/usr/lib/python3/dist-packages/vapoursynth.so
/usr/lib/x86_64-linux-gnu/libvapoursynth-script.so.0
/usr/lib/x86_64-linux-gnu/libvapoursynth-script.so.0.0.0
/usr/lib/x86_64-linux-gnu/libvapoursynth.so
/usr/lib/x86_64-linux-gnu/vapoursynth

$ locate temporalsoften
/usr/lib/x86_64-linux-gnu/vapoursynth/temporalsoften.so
/usr/lib/x86_64-linux-gnu/vapoursynth/temporalsoften2.so
/usr/share/vsscripts/temporalsoften2.py

I installed using the ppa over the last week.

$ vspipe -v
VapourSynth Video Processing Library
Copyright (c) 2012-2017 Fredrik Mellbin
Core R37
API R3.4
Options: -

Do you have any suggestions for where my config is wrong?
Try this. (http://www.l33tmeatwad.com/vapoursynth101/software-setup)

[l33tmeatwad]

Okay, so since I only have a few machines to test with and others have been unable to replicate my issue, I figured the easiest way would just to create a framework that can easily be tested. In the zip file (link below) is a copy of vsedit.app, VapourSynth.framework, setuplinks, undolinks, 8bit Sample.mp4, 8bit Sample.vpy, and copies of all the source codes. Place VapourSynth.framework in /Library/Frameworks and run setuplinks in terminal (or run the commands manually if you like ;)!). Then try running vsedit and open the script provided and try to preview the sample. I will point out that this does have the issues for me on my 15" Macbook Pros (2010 running 10.12 & 2011 running 10.11). If this works for other hardware then apparently it is specific to those hardware models.

Error Image (http://imgur.com/n7KwLhu)

Framework & Sample Download (http://www.mediafire.com/file/ep4ib8ugm1j538y/VStest.zip)

[cwk]

Is there a particular section you want me to try or is the general idea that I should build from source?

Have others had success using vsedit on Ubuntu when installing from the PPAs?

cwk

[l33tmeatwad]

Is there a particular section you want me to try or is the general idea that I should build from source?

Have others had success using vsedit on Ubuntu when installing from the PPAs?

cwk
vsedit tends to want to find things in the usual library paths of /usr/local/lib or /usr/lib so creating symbolic links to libvapoursynth & libvapoursynth-script (as well as vspipe) to one of those may fix your issues.

[Mystery Keeper]

vsedit tends to want to find things in the usual library paths of /usr/local/lib or /usr/lib so creating symbolic links to libvapoursynth & libvapoursynth-script (as well as vspipe) to one of those may fix your issues.There's more to it. You can tell vsedit where libvapoursynth-script is, but on Ubuntu and derivatives like Mint it would still fail to initialize Python environment. Something in your instruction fixes it.