VapourSynth Editor 2 - Page 10

poisondeathray · 30th March 2021, 06:01

Actually, the color picker seems completely broken in R5.x. When testing 8bit solid color bars, the numbers change almost randomly as you mouse over a color (not dithering issue, solid single color). R4.x works ok

lansing · 30th March 2021, 14:34

Quote:

Originally Posted by poisondeathray

Actually, the color picker seems completely broken in R5.x. When testing 8bit solid color bars, the numbers change almost randomly as you mouse over a color (not dithering issue, solid single color). R4.x works ok

The color picker was probably broken by one of the filter in the preview filter chain. I'm planning to reimplement it next in my todo list because the current implementation will reload the entire script every time a filter in the chain was turned on/off. Instead I should be using video nodes so that filters that had ran shouldn't need to rerun again. This same workflow should also be use when comparing similar scripts but I don't know the logics yet.

After testing out the warning message logger for some time, I think I will be reverting it back because it basically does nothing beside logging the deprecation warning messages, which no regular users needed it. While the plugin developers will get those warnings anyway using any python ide in development. I will keep the logger filter though as people might need it as a print function for debugging.

fAy01 · 7th April 2021, 03:45

Thanks for working on this project. I tested it and found a few things maybe you could implement.

1 - Loading a script in vsedit without filepath and just the script name shows preview but currently vsedit2 doesn't have that feature.
2 - The preview doesn't load unless I press the F5 key or hit the preview button. What doesn't work is going to the 'Video' menu and selecting 'Play.'
3 - Is it possible for "Preview Advanced Settings" to fetch information from the d2v/m2ts/mkv/etc. file?
4 - Could you possibly add a search bar in the hotkeys menu?

Kind Regards

Tima · 9th April 2021, 23:20

A nasty bug: if I open some script and close VSEdit, and then delete this script, VSEdit crashes on all subsequent runs.

Mystery Keeper · 10th April 2021, 02:02

Quote:

Originally Posted by Tima

A nasty bug: if I open some script and close VSEdit, and then delete this script, VSEdit crashes on all subsequent runs.

No such bug in vsedit. Must be a vsedit 2 thing.

lansing · 10th April 2021, 06:06

Quote:

Originally Posted by Tima

A nasty bug: if I open some script and close VSEdit, and then delete this script, VSEdit crashes on all subsequent runs.

Cannot reproduce. The program will just warn on missing scripts on next startup and continue running.

lansing · 10th April 2021, 06:35

Quote:

Originally Posted by fAy01

Thanks for working on this project. I tested it and found a few things maybe you could implement.

1 - Loading a script in vsedit without filepath and just the script name shows preview but currently vsedit2 doesn't have that feature.
2 - The preview doesn't load unless I press the F5 key or hit the preview button. What doesn't work is going to the 'Video' menu and selecting 'Play.'
3 - Is it possible for "Preview Advanced Settings" to fetch information from the d2v/m2ts/mkv/etc. file?
4 - Could you possibly add a search bar in the hotkeys menu?

Kind Regards

1. Do you mean loading video file without file path in the source filter? I don't know if it's better to just get the file path with "os.path.dirname(os.path.realpath(__file__))" in the script or have the program do it implicitly. It's just one line of code.

2. Video won't play unless the script has been run. I can disable the button until the script was loaded if that causes confusion.

3. What information are you looking for?

4. I'll add that to the todo list.

fAy01 · 11th April 2021, 19:39

Quote:

Originally Posted by lansing

1. Do you mean loading video file without file path in the source filter? I don't know if it's better to just get the file path with "os.path.dirname(os.path.realpath(__file__))" in the script or have the program do it implicitly. It's just one line of code.

Yes, please. I move files around a lot. I like the convenience of loading the scripts from any storage device.

Quote:

Originally Posted by lansing

2. Video won't play unless the script has been run. I can disable the button until the script was loaded if that causes confusion.

Actually, I want the script to load and preview when I press the f5, play button, and video button. Maybe?

Quote:

Originally Posted by lansing

3. What information are you looking for?

Actually, nevermind. I think I've misunderstood what it does.

Tima · 11th April 2021, 23:53

Quote:

Originally Posted by lansing

Cannot reproduce. The program will just warn on missing scripts on next startup and continue running.

Reproduces for me in 100% cases -- it occurs next thing after the warning message.

Stacktrace for VSEdit 2 R5.3 (Win10 x64):

Code:

>	vsedit.exe!00000000004846b9()	Unknown
 	vsedit.exe!0000000000494509()	Unknown
 	Qt5Core.dll!0000000068b974bb()	Unknown
 	Qt5Widgets.dll!0000000000fe3ce6()	Unknown
 	vsedit.exe!0000000000487df4()	Unknown
 	vsedit.exe!000000000048a36c()	Unknown
 	vsedit.exe!000000000048d267()	Unknown
 	vsedit.exe!0000000000498b8d()	Unknown
 	vsedit.exe!00000000004013c7()	Unknown
 	vsedit.exe!00000000004014cb()	Unknown
 	kernel32.dll!00007ff8839d7974()	Unknown
 	ntdll.dll!00007ff8843ca2d1()	Unknown

vigan1 · 10th May 2021, 10:59

Hello.
I am trying to get vapoursynth up and running on Ubuntu 20.04. But I can't build and install vsedit (vapoursynth editor).

Can you help me getting Vapoursynth editor 2 running on my linux ?

Code:

git clone https://bitbucket.org/gundamftw/vapoursynth-editor-2
cd vapoursynth-editor-2/pro
qmake -norecursive pro.pro CONFIG+=release
make

Here is a justepastit of the errors I encounter : https://justpaste.it/23n0j

It seems that ‘splitCommand’ is not a member of ‘QProcess’

feisty2 · 1st June 2021, 17:42

vsedit doesn't seem to display the indentation of a multi-line string properly, that's kinda weird,,,

as you can see from the preview window, the string being displayed is indented and it doesn't appear so in the message box. this problem can be traced back to the original version of vsedit.

core.test.Test() simply prints and returns the string representation of the first frame of a video node

Code:

PluginInstantiator::RegisterFunction("Test(clip: vnode)", [](auto Arguments, auto Core) {
	auto clip = static_cast<Node>(Arguments["clip"]);
	Core.Print(clip[0]);
	return static_cast<std::string>(clip[0]);
});

lansing · 4th June 2021, 06:49

Quote:

Originally Posted by feisty2

vsedit doesn't seem to display the indentation of a multi-line string properly, that's kinda weird,,,

as you can see from the preview window, the string being displayed is indented and it doesn't appear so in the message box. this problem can be traced back to the original version of vsedit.

core.test.Test() simply prints and returns the string representation of the first frame of a video node

It probably has to do with styling. Do you have test script and the test filter? How do I print the info to the console?

feisty2 · 4th June 2021, 08:21

Quote:

Do you have test script and the test filter? How do I print the info to the console?

script is shown above.

the source code and compiled binary of core.test.Test is available here: https://gist.github.com/IFeelBloated...3e628e5166d7e1

lansing · 4th June 2021, 17:05

Quote:

Originally Posted by feisty2

script is shown above.

the source code and compiled binary of core.test.Test is available here: https://gist.github.com/IFeelBloated...3e628e5166d7e1

The script above is an image, I couldn't copy it.

feisty2 · 4th June 2021, 17:10

alright...

Code:

from vapoursynth import *

clp = core.std.BlankClip(width=640, height=480, format=YUV444PS)
clp = core.std.SetFrameProp(clp, "aaa", data=["cccc", "hello"])
blk = core.std.BlankClip()
clp = core.std.ClipToProp(clp, core.std.ClipToProp(blk, core.std.BlankClip()))

clp = core.text.Text(clp, core.test.Test(clp))

clp.set_output()

lansing · 4th June 2021, 18:14

It should be fixed now.

c3eni23 · 13th June 2021, 13:35

Hello,

I already fix some issues and create pull request.
Hope this program can be more useful.

lansing · 16th July 2021, 02:36

I fixed the problem with the matrix coefficient selection not working correctly in the Preview Advanced Settings. Now changing from rec709 to rec601 will show a change in color in the preview.

I think I'll also move the matrix setting to the preview filter dialogue and remove all the rest in the Preview Advanced Settings, since they served no purpose at all.

Myrsloik · 1st August 2021, 13:23

The compat formats will be removed in future builds of VS meaning that you'll have to use RGB24 as output and pack the image yourself. You can get the beta builds with this behavior here:
https://forum.doom9.org/showthread.php?t=183070

Zarxrax · 13th August 2021, 23:54

I'm not sure if I'm doing this wrong, but I am trying to write a .py script, and it seems that I have to close and reopen my vaporsynth script every time I want to reload a new version. Simply hitting f5 to update the preview doesn't reload the .py script. Not sure if there is a workaround for that, or if not, maybe scripts/plugins could be reloaded each time you preview the script?

It would also be great if when pressing f5 to preview, it would automatically change focus to the video area, so my arrow keys will let me navigate the video. Save a click of the mouse.

And is there any way to change the resize algorithm used for the preview video? Looks like its using point resize. Or alternatively, it would be fantastic if I could press Alt+Enter to pop up a full-screen preview.

10th May 2021, 10:59	#190 \| Link
vigan1 Registered User Join Date: Jul 2020 Posts: 28	Hello. I am trying to get vapoursynth up and running on Ubuntu 20.04. But I can't build and install vsedit (vapoursynth editor). Can you help me getting Vapoursynth editor 2 running on my linux ? Code: git clone https://bitbucket.org/gundamftw/vapoursynth-editor-2 cd vapoursynth-editor-2/pro qmake -norecursive pro.pro CONFIG+=release make Here is a justepastit of the errors I encounter : https://justpaste.it/23n0j It seems that ‘splitCommand’ is not a member of ‘QProcess’ Last edited by vigan1; 10th May 2021 at 12:06.

1st June 2021, 17:42	#191 \| Link
feisty2 I'm Siri Join Date: Oct 2012 Location: void Posts: 2,633	vsedit doesn't seem to display the indentation of a multi-line string properly, that's kinda weird,,, as you can see from the preview window, the string being displayed is indented and it doesn't appear so in the message box. this problem can be traced back to the original version of vsedit. core.test.Test() simply prints and returns the string representation of the first frame of a video node Code: PluginInstantiator::RegisterFunction("Test(clip: vnode)", [](auto Arguments, auto Core) { auto clip = static_cast<Node>(Arguments["clip"]); Core.Print(clip[0]); return static_cast<std::string>(clip[0]); });

1st August 2021, 13:23	#199 \| Link
Myrsloik Professional Code Monkey Join Date: Jun 2003 Location: Kinnarps Chair Posts: 2,555	The compat formats will be removed in future builds of VS meaning that you'll have to use RGB24 as output and pack the image yourself. You can get the beta builds with this behavior here: https://forum.doom9.org/showthread.php?t=183070 __________________ VapourSynth - proving that scripting languages and video processing isn't dead yet

30th March 2021, 06:01	#181 \| Link
poisondeathray Registered User Join Date: Sep 2007 Posts: 5,377	Actually, the color picker seems completely broken in R5.x. When testing 8bit solid color bars, the numbers change almost randomly as you mouse over a color (not dithering issue, solid single color). R4.x works ok

7th April 2021, 03:45	#183 \| Link
fAy01 Registered User Join Date: Jun 2010 Posts: 91	Thanks for working on this project. I tested it and found a few things maybe you could implement. 1 - Loading a script in vsedit without filepath and just the script name shows preview but currently vsedit2 doesn't have that feature. 2 - The preview doesn't load unless I press the F5 key or hit the preview button. What doesn't work is going to the 'Video' menu and selecting 'Play.' 3 - Is it possible for "Preview Advanced Settings" to fetch information from the d2v/m2ts/mkv/etc. file? 4 - Could you possibly add a search bar in the hotkeys menu? Kind Regards

9th April 2021, 23:20	#184 \| Link
Tima Registered User Join Date: Aug 2004 Location: Russia, Novosibirsk Posts: 176	A nasty bug: if I open some script and close VSEdit, and then delete this script, VSEdit crashes on all subsequent runs.

4th June 2021, 18:14	#196 \| Link
lansing Registered User Join Date: Sep 2006 Posts: 1,657	It should be fixed now.

13th June 2021, 13:35	#197 \| Link
c3eni23 Registered User Join Date: Mar 2017 Posts: 1	Hello, I already fix some issues and create pull request. Hope this program can be more useful.

16th July 2021, 02:36	#198 \| Link
lansing Registered User Join Date: Sep 2006 Posts: 1,657	I fixed the problem with the matrix coefficient selection not working correctly in the Preview Advanced Settings. Now changing from rec709 to rec601 will show a change in color in the preview. I think I'll also move the matrix setting to the preview filter dialogue and remove all the rest in the Preview Advanced Settings, since they served no purpose at all.

13th August 2021, 23:54	#200 \| Link
Zarxrax Registered User Join Date: Dec 2001 Posts: 1,219	I'm not sure if I'm doing this wrong, but I am trying to write a .py script, and it seems that I have to close and reopen my vaporsynth script every time I want to reload a new version. Simply hitting f5 to update the preview doesn't reload the .py script. Not sure if there is a workaround for that, or if not, maybe scripts/plugins could be reloaded each time you preview the script? It would also be great if when pressing f5 to preview, it would automatically change focus to the video area, so my arrow keys will let me navigate the video. Save a click of the mouse. And is there any way to change the resize algorithm used for the preview video? Looks like its using point resize. Or alternatively, it would be fantastic if I could press Alt+Enter to pop up a full-screen preview.