VapourSynth Editor

[Joachim Buambeki]

Thanks for the VS editor, Mystery Keeper!
I tried to find this in the thread, so please excuse if it has been asked before but is there a chance to get user sliders functionality in the editor like AVSP (http://www.avisynth.nl/users/qwerpoi/UserSliders.html) has?

TIA!

[Mystery Keeper]

Thanks for the VS editor, Mystery Keeper!
I tried to find this in the thread, so please excuse if it has been asked before but is there a chance to get user sliders functionality in the editor like AVSP (http://www.avisynth.nl/users/qwerpoi/UserSliders.html) has?

TIA!You're welcome.
So far I'm not planning to add sliders. Plugins don't expose their valid argument values.
I think interactive preview with sliders is a generally bad idea. With a slow script you'll have to wait on each update. With a fast script such frequent updating would make VS leak memory.

[jackoneill]

With a fast script such frequent updating would make VS leak memory.

How? Where?

[Joachim Buambeki]

So far I'm not planning to add sliders. Plugins don't expose their valid argument values.
I think interactive preview with sliders is a generally bad idea. With a slow script you'll have to wait on each update. With a fast script such frequent updating would make VS leak memory.Got it, makes sense. Thanks nevertheless.

[Mystery Keeper]

How? Where?It always leaks a tiny amount on preview update. Been like that forever. Python, probably.

[Mystery Keeper]

R16 is out with a new major feature - jobs queue.

-BUGFIX: Default hotkey forced when trying to save an empty hotkey.
-BUGFIX: Inactive actions in the log context menu.
-Jobs queue with dependencies tracking.
-Adjustable jobs table.
-Pausable CLI encoding jobs.
-Pausable process run jobs.
-Shell command execute jobs.
-Removed framebuffer monitoring.
-Move text block up action.
-Move text block down action.
-Toggle comment action.

It is still a bit crude. Please report any unexpected behavior and improvement suggestions.
Be very careful to not run jobs from two simultaneously running instances of vsedit.
It won't be an issue in the next release. I'm planning to move the jobs to a separate server, accessible both locally and through the network.
Running jobs in parallel is technically possible, but I need to conceive a proper management logic for that.

To admins: does this thread deserve a sticky status yet?

[ChaosKing]

I get this msg on start with R16: VapourSynth plugins manager: Failed to get VapourSynth API!

The editor is in its own folder in a portable python/vapoursynth "installation".


I have set Lib search path to ../
and plugins path to ../vapoursynth64/plugins

Preview and everything else ist working, but I get this message in R16. No msg in R15 with the same settings.

Edit: could you please add a simple search functionality? STRG+F ?

[Mystery Keeper]

I get this msg on start with R16: VapourSynth plugins manager: Failed to get VapourSynth API!

The editor is in its own folder in a portable python/vapoursynth "installation".


I have set Lib search path to ../
and plugins path to ../vapoursynth64/plugins

Preview and everything else ist working, but I get this message in R16. No msg in R15 with the same settings.That's strange. Last changes in libraries loading were made in R14.

Edit: could you please add a simple search functionality? STRG+F ?Eventually. Not a high priority.

[Boulder]

I get the same error as ChaosKing.

I also get this after opening the settings menu:


Qt warning: QWindowsWindow::setGeometry: Unable to set geometry 411x517+435+240 on QWidgetWindow/'SettingsDialogWindow'. Resulting geometry: 411x542+435+240 (frame: 4, 23, 4, 4, custom margin: 0, 0, 0, 0, minimum size: 291x364, maximum size: 16777215x16777215).
Qt warning: QWindowsWindow::setGeometry: Unable to set geometry 411x517+435+240 on QWidgetWindow/'SettingsDialogWindow'. Resulting geometry: 411x542+435+240 (frame: 4, 23, 4, 4, custom margin: 0, 0, 0, 0, minimum size: 291x364, maximum size: 16777215x16777215).

[Mystery Keeper]

Aha. It is happening because R16 was built using VS R38 header, which has higher API version defined. vsedit R16 is requesting VS API of version that VS R37 can't provide. I'll look into proper solution.

[Mystery Keeper]

Fixed. Re-download R16.

[ChaosKing]

Yep, working now. Thx!

[TalasNetrag]

Is there a way to start the encoding with a different priority? (/Idle etc.)

[Mystery Keeper]

Is there a way to start the encoding with a different priority? (/Idle etc.)
No. Might do it in the next release. Or not.

[TalasNetrag]

I get these warnings with R16 and I dont know what they mean:
Qt warning: QObject::connect: No such signal vsedit::Job::signalCoreInfoChanged()
Qt warning: QObject::connect: No such signal VapourSynthScriptProcessor::signalCoreFramebufferUsedBytes(int64_t)

Also (maybe related to that?) the new Job feature seems to slow down the encoding. The encoding FPS keep on decreasing and the ETA stays the same. The Jobs window is getting more unresponsive over time. The CPU utilisation also seems to drop over time.

I tested the same script using vspipe, whithout VSEdit, and the encoding finished after 3h20m with around 3fps, while with VSEdit after 2h the ETA still says 3h to go and the fps dropped below 2.

I didnt get this behavior with R10 (the version I hab before). Using the latest Python, VapourSynth and VSEdit as portable installation.

[Mystery Keeper]

I get these warnings with R16 and I dont know what they mean:


Also (maybe related to that?) the new Job feature seems to slow down the encoding. The encoding FPS keep on decreasing and the ETA stays the same. The Jobs window is getting more unresponsive over time. The CPU utilisation also seems to drop over time.

I tested the same script using vspipe, whithout VSEdit, and the encoding finished after 3h20m with around 3fps, while with VSEdit after 2h the ETA still says 3h to go and the fps dropped below 2.

I didnt get this behavior with R10 (the version I hab before). Using the latest Python, VapourSynth and VSEdit as portable installation.
Don't mind these messages. They are harmless. Strange that I don't get them. The slowdown is also strange. Do you use encoding settings that print out progress? That can slow down the encoding and bloat the log. Next release should be faster due to separation of worker and GUI.

[TalasNetrag]

... Do you use encoding settings that print out progress? That can slow down the encoding and bloat the log. Next release should be faster due to separation of worker and GUI.

Yes I did. Disabling the progress output solved this issue.

[lansing]

Hi for the zooming control, can you add a setting for user custom interval control? Clicking zoom out on 100% will give me 0% view, which makes no sense.

[Mystery Keeper]

Hi for the zooming control, can you add a setting for user custom interval control? Clicking zoom out on 100% will give me 0% view, which makes no sense.I can, but it is tricky. Might do in future. You still can edit the value with keyboard.

[l33tmeatwad]

All of the macOS versions that were not compiled and uploaded before have now been added to the Mac download site.

[Mystery Keeper]

All of the macOS versions that were not compiled and uploaded before have now been added to the Mac download site.Thank you!

[l33tmeatwad]

Quick update, after looking through the compiles from last night I noticed R9 (that I had not compiled before) was giving the same artifacts bug as R11+ gave me...turns out I had upgraded Qt since I had compiled R10 and that was causing the bug (thank goodness I document just about everything...). Compiling and using Qt 5.8 or 5.9 will not display the preview properly, however I used 5.6 and it works just fine (I did not test 5.7). I have recompiled them all and they should be working properly now. If you could add to the documentation to use Qt 5.6 on macOS that would be great!

Side Note: This fix for VapourSynth Editor does NOT fix the blue screen bug I had mentioned before, I will continue to see what I can find out about that.

[feisty2]

I recently updated my vsedit to r16 and... I can no longer preview my videos
http://i.imgur.com/6MCLLuI.png
can you make a new option to ignore transfer and primaries checking?

[Mystery Keeper]

I recently updated my vsedit to r16 and... I can no longer preview my videos
http://i.imgur.com/6MCLLuI.png
can you make a new option to ignore transfer and primaries checking?
It is not me doing the checking, but core.std.resize. I set it up to prioritize the clip properties. Try erasing the matrix and transfer characteristics properties from your grayscale clip.

[feisty2]

maybe...
we could do

clp = core.std.SetFrameProp(clp,prop="_Matrix",delete=True)
clp = core.std.SetFrameProp(clp,prop="_Transfer",delete=True)
clp = core.std.SetFrameProp(clp,prop="_Primaries",delete=True)

implicitly for previewing...

[george84]

When using Color Panel one would expect it to show the values of the actual colors displayed in preview.

But it seems that Matrix of video is not used. In a code snippet as:
...
x = core.std.SetFrameProp(x, prop="_Matrix", intval=5)
x.set_output()

you can vary the Matrix value, but Color Panel will always show the same YUV values. It would be nice to show also actual color value.

[Mystery Keeper]

When using Color Panel one would expect it to show the values of the actual colors displayed in preview.

But it seems that Matrix of video is not used. In a code snippet as:
...
x = core.std.SetFrameProp(x, prop="_Matrix", intval=5)
x.set_output()

you can vary the Matrix value, but Color Panel will always show the same YUV values. It would be nice to show also actual color value.The colour panel shows the actual values from the video. To show the displayed colour I would need to convert. I'll see about adding the converted colour output.

[george84]

The error log doesn't correctly log the source statement. See attachment.

In the saved source code on line 24 there was referenced a jpeg file "2013...". Then the source code was modfied to what it shows in source, and a preview was done (without save script)

But in log this change isn't reflected.

[george84]

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

Have you ever had success? I also installed from ppa and vsedit doesn't find libraries.

[Mystery Keeper]

Have you ever had success? I also installed from ppa and vsedit doesn't find libraries.Never installed from repos. Used this instruction (http://www.l33tmeatwad.com/vapoursynth101/software-setup).

[george84]

Never installed from repos. Used this instruction (http://www.l33tmeatwad.com/vapoursynth101/software-setup).

Thank you. This instruction is outdated, my system has no python3.4. Also I am not willing to use software I have to build myself (as long as there are alternatives). I fear that this will only result in more problems..

[l33tmeatwad]

Thank you. This instruction is outdated, my system has no python3.4. Also I am not willing to use software I have to build myself (as long as there are alternatives). I fear that this will only result in more problems..
You can just change the 3.4 to whatever version you have or want to install...that said, in terms of compiling vsedit that part shouldn't even matter as long as VapourSynth itself works. Compiling yourself will not lead to more problems, if it compiles at all it will work fine.

[george84]

Vapoursynth itself seems to work. Starting python and doing import vapoursynth .... gives no error message. Only vsedit complains about missing script library.

Maybe the problem is because there are at least 4 python versions in system.
Also I have 32 bit ubuntu and instructions are only for 64 bit ubuntu.

[l33tmeatwad]

Vapoursynth itself seems to work. Starting python and doing import vapoursynth .... gives no error message. Only vsedit complains about missing script library.

Maybe the problem is because there are at least 4 python versions in system.
Also I have 32 bit ubuntu and instructions are only for 64 bit ubuntu.
The instructions should work the same for both x86 and x64 Ubuntu.

[george84]

I think that in Linux Software setup instructions there is missing a cd $HOME/.installs in PART A. Dependencies

By the way: make of zimg from sources failed (confirms my fear) in

resize_impl_avx512.cpp:589:27: error: invalid conversion from int to _MM_PERM_ENUM....

I have xenial 16.1.

[l33tmeatwad]

I think that in Linux Software setup instructions there is missing a cd $HOME/.installs in PART A. Dependencies

By the way: make of zimg from sources failed (confirms my fear) in

resize_impl_avx512.cpp:589:27: error: invalid conversion from int to _MM_PERM_ENUM....

I have xenial 16.1.
Try using one of the releases if you are using the most recent changes in the repository.

[cwk]

Hi George,

Have you ever had success? I also installed from ppa and vsedit doesn't find libraries.

Sorry for the late reply. Yes, I was able to get the editor to work using PPAs by adding the following link:

$ sudo ln -s /usr/lib/x86_64-linux-gnu/libvapoursynth-script.so.0.0.0 /usr/lib/x86_64-linux-gnu/libvapoursynth-script.so

[george84]

Hi cwk

Thank you. I will try.

[cwk]

I should mention that I'm using Ubuntu 16.04. Let me know if you run into any issues.

[george84]

I should mention that I'm using Ubuntu 16.04. Let me know if you run into any issues.

Excellent advice for setting symbolic link. I have 32 bit system so I had to use i386-linux-gnu instead of x64.
Now vsedit works (inclusive script preview) loaded only from ppa

Maybe I should also mention that in settings paths are set to /usr/lib/i386-linux-gnu and /usr/lib/i386-linux-gnu/vapoursynth

[blaze077]

When I try to preview a clip with variable frame dimensions, the preview simply gives me a blank screen:

http://i.imgur.com/ngB7zbP.png

I've tried r14-16 and all of them create the same problem.
import vapoursynth as vs
core = vs.core
src = core.std.BlankClip()
src2 = core.std.BlankClip(width=480, height=360)
final = core.std.Splice([src, src2], True)
final.set_output()

Also, clips with varying formats make VSEdit crash when previewing. The script check works fine.

[Mystery Keeper]

When I try to preview a clip with variable frame dimensions, the preview simply gives me a blank screen:

http://i.imgur.com/ngB7zbP.png

I've tried r14-16 and all of them create the same problem.
import vapoursynth as vs
core = vs.core
src = core.std.BlankClip()
src2 = core.std.BlankClip(width=480, height=360)
final = core.std.Splice([src, src2], True)
final.set_output()

Also, clips with varying formats make VSEdit crash when previewing. The script check works fine.
Could you please upload your video so I could debug with it?

[blaze077]

The piece of code included in my post is what I'm using. It happens with all clips with varying dimensions. I'm pretty sure it is a problem on my side as I was able to view everything correctly a few weeks back. Sorry for not being clear.
EDIT: Fixed it. My fault. Zoom was at fixed ratio.

The variable format clip, however, still crashes it.
src = core.std.Splice([core.std.BlankClip(format=vs.YUV420P8), core.std.BlankClip(format=vs.YUV444P8)], True)
src.set_output()

[lansing]

Hi I ran into a bug, when I highlight a word and right click, it deselect the selection instead of letting me copy/cut.

[Mystery Keeper]

Hi I ran into a bug, when I highlight a word and right click, it deselect the selection instead of letting me copy/cut. Partially confirmed. I do get the wrong menu. No deselection though.

[lansing]

Hi can you add an option to export the video as image sequence? Because I made my video with changing resolution but Virtualdub couldn't open it

[VS_Fan]

Hi can you add an option to export the video as image sequence? Because I made my video with changing resolution but Virtualdub couldn't open it
To export image sequences you could try VapourSynth's ImageMagick Writer (http://www.vapoursynth.com/doc/plugins/imwri.html).

Also, instead of VirtualDub, have you tried VirtualDub FilterMod (https://forum.doom9.org/showthread.php?t=172021)?

[Mystery Keeper]

Hi can you add an option to export the video as image sequence? Because I made my video with changing resolution but Virtualdub couldn't open it Exporting video is a work of encoder. Ffmpeg can encode as APNG or animated GIF. Don't know about image sequence. But yes, imwri plugin is an option.

I'll look into variable size preview not working.

[lansing]

@VS_Fan

I am using Virtualdub FilterMod, it doesn't support changing resolution, it just returns an error.
And for the imwri filter, the program just tell me that it doesn't exist, I check the vapousynth site and it said it should be included.

@Mystery Keeper

My sole purpose is to make a video with changing resolution and output it as image sequence, I don't want to encode it or make a gif.

[VS_Fan]

I think this (https://forum.doom9.org/showthread.php?p=1807833#post1807833) is the latest IMWRI test build available from Myrsloik