VapourSynth Editor

[lansing]

I decided against allowing tabs for stability reasons. Don't want to lose all my work if previewing one script crashes the editor.

I am going to implement comparison eventually. But among several output nodes rather than several scripts.

How are you going to organize the scripts without tab? For example, if I have three scripts that I wanted to compare, the original, denoised and denoised2, how would the layout look like. And what's your view on the layout for the preview windows?

[Mystery Keeper]

How are you going to organize the scripts without tab? For example, if I have three scripts that I wanted to compare, the original, denoised and denoised2, how would the layout look like. And what's your view on the layout for the preview windows?
Instead of 3 scripts you make one script with 3 output nodes - each with their own processing.
Comparison will have several options. Vertical, horizontal and rectangular alignment and some kind of switching for 3 and more nodes, plus swipeline for just 2 nodes.

[lansing]

Instead of 3 scripts you make one script with 3 output nodes - each with their own processing.
Comparison will have several options. Vertical, horizontal and rectangular alignment and some kind of switching for 3 and more nodes, plus swipeline for just 2 nodes.

How are they organize? Are they going to be managed by one main window like tab or all in their own windows?

As an experienced user, I found that all the split view comparison mode very little use, because that's not how people do video comparison. The images have to be stack on top of each other in order to better spot differences.

[Mystery Keeper]

How are they organize? Are they going to be managed by one main window like tab or all in their own windows?

As an experienced user, I found that all the split view comparison mode very little use, because that's not how people do video comparison. The images have to be stack on top of each other in order to better spot differences.That's why there will be several options. You'll see when it's done. I can't promise any timeframe for it to be done.

[tuanden0]

VSEditor crashed when call nnedi3_resample
I use nnedi3_resample here: https://github.com/mawen1250/VapourSynth-script
Here's my *.vpy:
import vapoursynth as vs
import fvsfunc as fvf
import nnedi3_resample as nnrs
core = vs.core
clip = core.ffms2.Source(r"E:\Download\Source\zzz\test.mkv")
clip = core.std.AssumeFPS(clip, fpsnum=24000, fpsden=1001)
clip = fvf.Depth(clip, bits=16)
clip = nnrs.nnedi3_resample(clip, 1280, 720)
clip.set_output()

First I checked and no error: https://i.imgur.com/KTbKRjd.png
But when I preview, VSEditor crashed: https://i.imgur.com/gAZMaUO.png
Then I tried to port this script to Avisynth to preview: https://i.imgur.com/rUNCJRf.png
And It's work: https://i.imgur.com/XE6fgOD.png

So, I think this is VSeditor problem.

[Myrsloik]

VSEditor crashed when call nnedi3_resample
I use nnedi3_resample here: https://github.com/mawen1250/VapourSynth-script
Here's my *.vpy:


First I checked and no error: https://i.imgur.com/KTbKRjd.png
But when I preview, VSEditor crashed: https://i.imgur.com/gAZMaUO.png
Then I tried to port this script to Avisynth to preview: https://i.imgur.com/rUNCJRf.png
And It's work: https://i.imgur.com/XE6fgOD.png

So, I think this is VSeditor problem.

Does it crash when you use vspipe?

[tuanden0]

Does it crash when you use vspipe?
No, it doesn't
I can encode with it but can't preview on VSEditor

[no1d]

VSEditor crashed when call nnedi3_resample

Had the same issue, it seems that fmtc.resample is the culprit. Works fine with internal resizers.

Does it crash when you use vspipe?

It does for me, but only sometimes..

[_Al_]

Using Ubuntu 18.04 and its Python 3.6, using opencv version3 and
simple:
import cv2
silently crashes VapourSynth Editor, not sure what's going on, other moduls are imported fine, like numpy and others and also opencv import and functions work fine using IDLE3 or Terminal. Vapoursynth 45 works also.

[lansing]

For some reason the textarea in my vs editor turns all black, the texts are still there when I highlight them. It was working normal before and I don't know how I triggered it. How do I restore the default display?

[Mystery Keeper]

For some reason the textarea in my vs editor turns all black, the texts are still there when I highlight them. It was working normal before and I don't know how I triggered it. How do I restore the default display?That's a bug in job server settings handling. You can fix it by finding the vsedit.config file (user/AppData/local on Windows, or vsedit path if in portable mode) and erasing the "theme" section. The bug is fixed in the repo, but with all I've been going through, it never made it into release. I'll try to make a release soon.

[lansing]

That's a bug in job server settings handling. You can fix it by finding the vsedit.config file (user/AppData/local on Windows, or vsedit path if in portable mode) and erasing the "theme" section. The bug is fixed in the repo, but with all I've been going through, it never made it into release. I'll try to make a release soon.

Thanks I got it.

[Mystery Keeper]

R19 is out. Not much, mostly bug fixes. Life's been hectic. Development is slow.

-BUGFIX: Rapid settings updating on windows geometry change.
-BUGFIX: Theme settings corruption when using job server.
-Color picker update with a still mouse cursor in play mode.
-Benchmark dialog remembers first and last frame for current script.

[lansing]

I found a bug in the preview window, if I click and hold on a spot in the timeline, the tool tip box will turn into a black box and keep on flashing.

There's a problem with benchmark too that it doesn't exit the script when it was done. I was doing benchmarks on short clips that output a log on time use to finish. The log wasn't created until I closed the benchmark window and the time being idle after the benchmark finished had also been counted toward the timing in the log.

[Mystery Keeper]

I found a bug in the preview window, if I click and hold on a spot in the timeline, the tool tip box will turn into a black box and keep on flashing. Can't reproduce. What system you're on and what user environment (GNOME, KDE, Cinnamon, etc) you're using?

There's a problem with benchmark too that it doesn't exit the script when it was done. I was doing benchmarks on short clips that output a log on time use to finish. The log wasn't created until I closed the benchmark window and the time being idle after the benchmark finished had also been counted toward the timing in the log.There are other problems with benchmark window too. I'll work on it. But if you wrote the plugins you use for logging - you might want to change their logic to do what you want more reliably. VapourSynth Editor is not made with individual plugins in mind.

[lansing]

Can't reproduce. What system you're on and what user environment (GNOME, KDE, Cinnamon, etc) you're using?


Windows 7

[Mystery Keeper]

Windows 7
Are you using Aero (the transparent glass windows)?

[lansing]

Are you using Aero (the transparent glass windows)?

Yes. r18 doesn't have this problem.

[F1nkster]

I'm on Win10 running vsedit r19.

I add a custom library search path into vsedit Settings. It works fine (meaning I can import library files in that path) when I run vsedit as Admin. It does not work when I run as my normal user account.

I also added the path to PYTHONPATH and it works fine at the Python CLI, as one would expect. Just not from within vsedit.

Running vsedit as my normal user account works fine for library files that I add to ..\Python37\Lib\site-packages\vapoursynth. So it is just failing on custom paths that I add into vsedit Settings.

Also, I gave my user account full rights to Python37 and everything in it, plus the VapourSynth install directory (and everything in it), and the VapourSynth Editor directory (and everything in it). None of that made any difference.

I also deleted the config file that shows up in my AppData\Local directory. That resets all settings, but it did not change behavior.

I'm out of ideas!

[Mystery Keeper]

I'm on Win10 running vsedit r19.

I add a custom library search path into vsedit Settings. It works fine (meaning I can import library files in that path) when I run vsedit as Admin. It does not work when I run as my normal user account.

I also added the path to PYTHONPATH and it works fine at the Python CLI, as one would expect. Just not from within vsedit.

Running vsedit as my normal user account works fine for library files that I add to ..\Python37\Lib\site-packages\vapoursynth. So it is just failing on custom paths that I add into vsedit Settings.

Also, I gave my user account full rights to Python37 and everything in it, plus the VapourSynth install directory (and everything in it), and the VapourSynth Editor directory (and everything in it). None of that made any difference.

I also deleted the config file that shows up in my AppData\Local directory. That resets all settings, but it did not change behavior.

I'm out of ideas!The only thing that comes to mind is registry. One of the things on my TODO list is to make custom paths take priority over registry. Maybe that would help. For now, try to reinstall Python "for all users".

I'm sorry to say that, but I'm NOT going to test on Windows 10. It's shit and should be avoided at any cost.

[F1nkster]

That was a good thought, but it didn't work. It's not a showstopper. I'm back to using the Python37\Lib\site-packages directory. I'll cope! Anyhow, thanks for writing this software. I am in the process of moving from Win10 to Ubuntu. And this is why I am starting to use VapourSynth. It will be a bit longer though before I can make the jump. I am starting with VS in the meantime on Windows.

Btw, this may not be a VSEdit issue. I found I have the same problem when I load a VPY script into VDub2. I have to run VDub2 as Admin when using the custom path. So it's a bother all around which is why I just went back to using the standard site-packages dir.

[ChaosKing]

On my windows 10 it is just in the PATH (for system, not user) var c:\python37 and everything works fine.

[l33tmeatwad]

Little behind on this, I'll get the new ones compiled for OSX as soon as I can.

[l33tmeatwad]

r19 is now on uploaded for macOS

[asarian]

I'm loving this piece of software! :) Found it very useful, recently, to get a quick preview of a movie I wanted to burn subs into.

One bit of annoyance, though. Whenever I start the preview (F5), I get a fatal error; something about fftw_make_planner_thread_safe entry point not found in the fft3dfilter library. The latter is actually, indeed, not present on my system, as I replaced it with libdfttest.dll recently (from another author). For the test, of course, I temporarily put fft3dfilter.dll back inside the plugins64 directory, but the same error still occured, oddly enough.

When I said 'fatal error', it's not actually so fatal, as I can just click it away, and the VapourSynth Editor will just continue as if nothing happened. Any particular reason, though, fft3dfilter is needed per se to start up the editor?!

[Mystery Keeper]

I'm loving this piece of software! :) Found it very useful, recently, to get a quick preview of a movie I wanted to burn subs into.

One bit of annoyance, though. Whenever I start the preview (F5), I get a fatal error; something about fftw_make_planner_thread_safe entry point not found in the fft3dfilter library. The latter is actually, indeed, not present on my system, as I replaced it with libdfttest.dll recently (from another author). For the test, of course, I temporarily put fft3dfilter.dll back inside the plugins64 directory, but the same error still occured, oddly enough.

When I said 'fatal error', it's not actually so fatal, as I can just click it away, and the VapourSynth Editor will just continue as if nothing happened. Any particular reason, though, fft3dfilter is needed per se to start up the editor?!

That's weird, because VapourSynth is supposed to report a fatal error right before it crashes.
It's happening somewhere in your script. Something is trying to load fft3dfilter.
fftw_make_planner_thread_safe is a function of FFTW library. It shouldn't be in fft3dfilter, unless FFTW was linked statically. But in that case the error should not occur.

So, all in all - no idea.
It is not related to the editor in any way. Editor just logs the errors VapourSynth reports.

[Myrsloik]

That's weird, because VapourSynth is supposed to report a fatal error right before it crashes.
It's happening somewhere in your script. Something is trying to load fft3dfilter.
fftw_make_planner_thread_safe is a function of FFTW library. It shouldn't be in fft3dfilter, unless FFTW was linked statically. But in that case the error should not occur.

So, all in all - no idea.
It is not related to the editor in any way. Editor just logs the errors VapourSynth reports.

Too old FFTW dll. The end. Not related to anything else.

[asarian]

That's weird, because VapourSynth is supposed to report a fatal error right before it crashes.
It's happening somewhere in your script. Something is trying to load fft3dfilter.

Except I'm not even using a script. :) Just the 2 default lines trigger it (upon pressing F5). See: VSEditor Error (https://1drv.ms/u/s!AhSxhQ9g_mrMlgYBgLsePzNAABr_)

fftw_make_planner_thread_safe is a function of FFTW library. It shouldn't be in fft3dfilter, unless FFTW was linked statically. But in that case the error should not occur.

That was my poiny exactly when I asked! I couldn't figure why the VS Editor would need fft3dfilter at startup to begin with.

[asarian]

^^ Turns out I had some very old .dll files, from a VS R32 install, copied over to the VS plugins64 directory once (not overwriting the ones already present from the new install: just extra old ones). Once I removed/updated those, VS Editor ran fine again. :) Guess all VS Editor did, was visualize the errors from the older 64-bit plugins initializing (which you normally don't see).

[Lypheo]

My VSEdit suddenly stopped rendering the preview and shows this warning in the log whenever I open the preview or try to seek in it: Qt warning: QImage: out of memory, returning null image

It happens with every script (even just a BlankClip) I’ve tried. I already tried reinstalling and downgrading, but it still shows the warning and refuses to render in every version. Any idea what I could be doing wrong?

[Mystery Keeper]

My VSEdit suddenly stopped rendering the preview and shows this warning in the log whenever I open the preview or try to seek in it: Qt warning: QImage: out of memory, returning null image

It happens with every script (even just a BlankClip) I’ve tried. I already tried reinstalling and downgrading, but it still shows the warning and refuses to render in every version. Any idea what I could be doing wrong?
Never had it. Are you running some processes that hog the memory? Images need large continuous chunks of memory.

[kypec]

Hi guys,

I tried to build this VapourSynth Editor from sources but didn't succeed on my Linux Mint 19.1 (Cinnamon)
Here are the steps I've done so far:

Fetched the latest source code
git clone https://bitbucket.org/mystery_keeper/vapoursynth-editor.git
Installed prerequisites
sudo apt install qt5-default qtbase5-dev qtbase5-private-dev libqt5websockets5-dev
Configured & compiled source files
cd vapoursynth-editor/pro/
qmake -norecursive pro.pro CONFIG+=release
make


which ends with error Project ERROR: Unknown module(s) in QT: websockets
Makefile:71: recipe for target 'sub-vsedit-job-server-vsedit-job-server-pro-make_first' failed
make: *** [sub-vsedit-job-server-vsedit-job-server-pro-make_first] Error 3

EDIT: I resolved the building by manually compiling QtWebSockets (https://github.com/qt/qtwebsockets). I used specific release 5.9.5 (https://github.com/qt/qtwebsockets/archive/v5.9.5.tar.gz) because this version matched with all other Qt components that were installed on my system from official repositories.
In order to build and install that component I had to install few more Qt packages from official repo (added in step 2 already). Once done VS Editor building finished successfully as well. Is there any way to make install it to system-wide path? I couldn't find anything in the BUILDING notes about that... ;)

[Mystery Keeper]

Hi guys,

I tried to build this VapourSynth Editor from sources but didn't succeed on my Linux Mint 19.1 (Cinnamon)
Here are the steps I've done so far:

Fetched the latest source code
git clone https://bitbucket.org/mystery_keeper/vapoursynth-editor.git
Installed prerequisites
sudo apt install qtbase5-dev qt5-default libqt5websockets5-dev
Configured & compiled source files
cd vapoursynth-editor/pro/
qmake -norecursive pro.pro CONFIG+=release
make


which ends with error Project ERROR: Unknown module(s) in QT: websockets
Makefile:71: recipe for target 'sub-vsedit-job-server-vsedit-job-server-pro-make_first' failed
make: *** [sub-vsedit-job-server-vsedit-job-server-pro-make_first] Error 3
Any ideas how to proceed further and eliminate that error? Obviously, sudo make install fails as well. :stupid:

Are there any .pro.user files from the QtCreator among the files? Try deleting those.

[kypec]

Are there any .pro.user files from the QtCreator among the files? Try deleting those.

Nope, but I managed to resolve the issue - see my edit in the post above. :thanks:

[Keiyakusha]

kypec
Any chance this build can be shared somehow?
Is there something compiled version depends on that Mint doesn't have by default? (Thinking off appimage)

[kypec]

Sure, here is my build (https://drive.google.com/file/d/1Fm4vTfTPzT73q7hK4G2l-76WxRkiFlPx/view?usp=drivesdk) but I would recommend to have it built on your own Mint system. I don't think there are any special non-default dependencies needed, just follow my instructions (https://forum.doom9.org/showthread.php?p=1874118#post1874118) and install any missing packages from official repositories.

[Keiyakusha]

kypec
Thanks. I probably should, but since I am using exact same OS I thought I'll try to go with easier route. I'll look into compiling it myself at some point.

Edit: on the other hand I think it would be best do make Travis build and share VapourSynth Editor, Including version for linux. Maybe even with the same appimage. But I have no idea how hard that would be.

[Mystery Keeper]

It would be the best to have it maintained in a Mint repository. Some repositories already do that. I've also found this.
https://www.deb-multimedia.org/dists/testing/main/binary-amd64/package/vapoursynth-editor

[Keiyakusha]

It would be the best to have it maintained in a Mint repository. Some repositories already do that. I've also found this.
https://www.deb-multimedia.org/dists/testing/main/binary-amd64/package/vapoursynth-editor

I think in the end this would be more work and people on other distributions would have to add mint's ppa and try their luck... appimage, on the other hand, is a portable version with all the dependencies included that works on any os with the same or newer kernel as the one software was compiled with. It might need some time investment to set up but it hardly needs any maintenance after that. Projects like mkvtoolnix, inkscape, avidemux use this method (though I am not sure they use travis specifically). Mkvtoolnix is also on QT so there should be no issues.

[~ VEGETA ~]

I installed vapoursynth version 46 the x64 bit on windows 10 pro, and I have latest x64 version of vs editor. However I get this:


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


I used VS repo GUI to get the path for scripts and plugins and put it in vs edit but still no use. Here are the paths:


C:\Users\myuser\AppData\Roaming\VapourSynth\plugins64
C:\Users\myuser\AppData\Roaming\Python\Python37\site-packages



first one for plugins and the other for scripts.

anything to solve it?

thanks!

UPDATE: I solved it by installing python in C:\ and for all users then installing VS for all users and in C.

[Mystery Keeper]

Probably broken by VapourSynth storing its settings in new registry paths.

[RTW47]

always getting Qt warning message that QPixmap::scaled: Pixmap is a null pixmap then previewing script. (r19 and r18),
for me r19 also do not highlight syntax, compared to r18. (but autocompletion and selection highlighting is working)
ps:. I have noticed the same preview problem (https://forum.doom9.org/showthread.php?p=1863341#post1863341) as lansing too. (r19 on windows 7)

[ChaosKing]

Have you tried resetting your config? I had some problems too bcs I kept my config from r18.

[RTW47]

Have you tried resetting your config? I had some problems too bcs I kept my config from r18.

thanks, I was not aware of config file.
resetting vsedit.config solved Syntax highlighting and Qt warning;

[cyaoeu]

Is VSEdit broken for newer VS versions when using per user installs for python and VS?

[Selur]

@cyaoeu: my guess is that "_vsscript_getVSApi@0" needs to be replaced with "_vsscript_getVSApi" for VSEdit to properly work with R47 (had to do this for vsViewer which is based on an older vsedit version)

[Myrsloik]

@cyaoeu: my guess is that "_vsscript_getVSApi@0" needs to be replaced with "_vsscript_getVSApi" for VSEdit to properly work with R47 (had to do this for vsViewer which is based on an older vsedit version)

Is this something that happened between R46 and R47? Nothing should have changed at all.

[cyaoeu]

@cyaoeu: my guess is that "_vsscript_getVSApi@0" needs to be replaced with "_vsscript_getVSApi" for VSEdit to properly work with R47 (had to do this for vsViewer which is based on an older vsedit version)

Thanks, it worked. :)
edit: actually the older one started working too (!) so may have been something else, missing reboot or something. Anyway it's working now again.

[Selur]

Is this something that happened between R46 and R47? Nothing should have changed at all.
messagehandler api changed and broke stuff, at least for me
m_cpVSAPI->setMessageHandler(::vsMessageHandler, static_cast<void *>(this));
which worked with with R36 doesn't work anymore,..
funny thing is, it does seem to work when using
m_cpVSAPI->setMessageHandler(::vsMessageHandler, (void)(this));
instead,...

[Myrsloik]

messagehandler api changed and broke stuff, at least for me
m_cpVSAPI->setMessageHandler(::vsMessageHandler, static_cast<void *>(this));
which worked with with R36 doesn't work anymore,..
funny thing is, it does seem to work when using
m_cpVSAPI->setMessageHandler(::vsMessageHandler, (void)(this));
instead,...

What do you mean by doesn't work? DESCRIBE WHAT HAPPENS. PASTE COMPILER ERRORS IF ANY.

VSEdit definitely needs to be updated for R47 as a lot of the registry entries were moved around as well but the logging should be completely backwards compatible.