VapourSynth Editor

[WolframRhodium]

"-Keep preview scrolling and frame number on refreshing the same script."
It does not work on my computer. I'm using Windows10 64bit, VapourSynth Editor r10.

On r9, only frame number is succesfully kept now.
On r10, none of them is kept.

[Mystery Keeper]

"-Keep preview scrolling and frame number on refreshing the same script."
It does not work on my computer. I'm using Windows10 64bit, VapourSynth Editor r10.

On r9, only frame number is succesfully kept now.
On r10, none of them is kept.Let me guess. You haven't saved your script. Nothing is ever saved for a script that has no name. No frame number, no scrolling, no bookmarks.
Frame number and scrolling are kept if either the script name or the whole script text is the same on refresh. Bookmarks are copied on "Save as".

[WolframRhodium]

Let me guess. You haven't saved your script. Nothing is ever saved for a script that has no name. No frame number, no scrolling, no bookmarks.
Frame number and scrolling are kept if either the script name or the whole script text is the same on refresh. Bookmarks are copied on "Save as".

I'm sure that my script is saved, and even when I open an old script, it still doesn't work.

The name of the script only consists of ascii characters.

[Mystery Keeper]

I'm sure that my script is saved, and even when I open an old script, it still doesn't work.

The name of the script only consists of ascii characters.

Refreshing the script is working alright for me. "Remember the last previewed frame on exit" seems broken though. Shall look into it.
Update: I looked into my settings and found a "General" section, which shouldn't be there at all. Deleted it - and last previewed frame remembering worked again. Don't know what has happened, but you might want to flush your config file. If you open it and see "General" section - delete that section.

[WolframRhodium]

Refreshing the script is working alright for me. "Remember the last previewed frame on exit" seems broken though. Shall look into it.
Update: I looked into my settings and found a "General" section, which shouldn't be there at all. Deleted it - and last previewed frame remembering worked again. Don't know what has happened, but you might want to flush your config file. If you open it and see "General" section - delete that section.

I checked the config file and there is no "General" section, just "common", "hotkeys", "theme" and "code_snippets" section.
And I also tried to delete the config file and use the new config file generated by the VS Editor, tick off "Remember the last previewed frame on exit", however, it still doesn't work.

This time I notice that, when I open the setting window, the log window displays
"Qt warning: QWindowsWindow::setGeometry: Unable to set geometry 421x467+750+307 on QWidgetWindow/'SettingsDialogWindow'. Resulting geometry: 421x483+750+307 (frame: 9, 38, 9, 9, custom margin: 0, 0, 0, 0, minimum size: 421x467, maximum size: 16777215x16777215)." Is there anything wrong?

Update:
This time, if I close a preview window (the editor program is still running) and reopen it, only scrolling is kept. Additionaly, if I close the editor window when previewing, then open the editor again and start previewing, only frame number is kept if I'm using r10, and nothing is kept if I'm using r9.

Update2:
Is "vsedit.config" located at %USERPROFILE%\AppData\Local ?

I notice that "last_preview_frame" in section "common" remembers last preview frame number as soon as I close the preview window, but when I try to preview again without any other operation, the value is set to 0, and I'm previewing frame 0 with remembered scrolling.

[Mystery Keeper]

This time I notice that, when I open the setting window, the log window displays
"Qt warning: QWindowsWindow::setGeometry: Unable to set geometry 421x467+750+307 on QWidgetWindow/'SettingsDialogWindow'. Resulting geometry: 421x483+750+307 (frame: 9, 38, 9, 9, custom margin: 0, 0, 0, 0, minimum size: 421x467, maximum size: 16777215x16777215)." Is there anything wrong?
No. There's nothing wrong. With your system metrics the minimum window size becomes larger than the initial size set by the application. Qt is notifying about it. Maybe I should only display Qt messages in debug build.

Is "vsedit.config" located at %USERPROFILE%\AppData\Local ?
Yes, if you're not working in portable mode.

This time, if I close a preview window (the editor program is still running) and reopen it, only scrolling is kept. Additionaly, if I close the editor window when previewing, then open the editor again and start previewing, only frame number is kept if I'm using r10, and nothing is kept if I'm using r9.
I notice that "last_preview_frame" in section "common" remembers last preview frame number as soon as I close the preview window, but when I try to preview again without any other operation, the value is set to 0, and I'm previewing frame 0 with remembered scrolling.
Scrolling is not really remembered. It is just not reset. Vsedit remembers last script you worked with. If on the start you're trying to preview the script with the same path - it restores the last remembered previewed frame. When refreshing preview it checks if either the script name (path) or the script text is the same as the one you previewed before. Then it keeps the current frame and scrolling. If both are different - current frame and scrolling are reset.

[WolframRhodium]

No. There's nothing wrong. With your system metrics the minimum window size becomes larger than the initial size set by the application. Qt is notifying about it. Maybe I should only display Qt messages in debug build.


Yes, if you're not working in portable mode.


Scrolling is not really remembered. It is just not reset. Vsedit remembers last script you worked with. If on the start you're trying to preview the script with the same path - it restores the last remembered previewed frame. When refreshing preview it checks if either the script name (path) or the script text is the same as the one you previewed before. Then it keeps the current frame and scrolling. If both are different - current frame and scrolling are reset.

So is there any suggestions that can make vsedit on my computer keeps the current frame when refreshing preview now?

[Mystery Keeper]

So is there any suggestions that can make vsedit on my computer keeps the current frame when refreshing preview now?Save new scripts before previewing them. If you save script with different name - refresh your preview before making any changes in it. Loading other script does reset current frame by design. I might add an option to keep the current frame unconditionally in future release.

[WolframRhodium]

Save new scripts before previewing them. If you save script with different name - refresh your preview before making any changes in it. Loading other script does reset current frame by design. I might add an option to keep the current frame unconditionally in future release.

It doesn't work, still
Thank you for your help. I'm looking for future release.

[TalasNetrag]

I'm trying to use 'Encode Video' functionality of VSEdit, but I get this error message.

Command line:
"H:/x264-10b-r2694-3b70645.exe" --frames 34567 --preset veryslow --tune animation --crf 18 --demuxer raw --output-csp i420 --input-csp i420 --input-depth 10 --input-res 1920x1080 --fps 24000/1001 --output "H:/test.h264"
Checking the encoder sanity.
x264 [error]: No input file. Run x264 --help for a list of options.
Encoder seems sane. Starting.
Encoder started. Beginning encoding.
x264 [error]: No input file. Run x264 --help for a list of options.
Encoder has suddenly stopped accepting data. Aborting.
Encoder has finished working while it shouldn't be running at all. Ignoring.

Executable:
H:/x264-10b-r2694-3b70645.exe
Arguments:

--frames {f}
--preset veryslow
--tune animation
--crf 18
--demuxer raw
--output-csp i{ss}
--input-csp i{ss}
--input-depth {bits}
--input-res {w}x{h}
--fps {fpsn}/{fpsd}
--output "H:/test.h264"

Using the generated command line with VSPipe works fine:

"H:\Videocoding\VapourSynth\VSPipe.exe" "H:\Videocoding\VapourSynth\scripts\Untitled.vpy" - | "H:/x264-10b-r2694-3b70645.exe" --frames 34567 --preset veryslow --tune animation --crf 18 --demuxer raw --output-csp i420 --input-csp i420 --input-depth 10 --input-res 1920x1080 --fps 24000/1001 --output "H:/test.h264" -

[Mystery Keeper]

I'm trying to use 'Encode Video' functionality of VSEdit, but I get this error message.

Command line:
"H:/x264-10b-r2694-3b70645.exe" --frames 34567 --preset veryslow --tune animation --crf 18 --demuxer raw --output-csp i420 --input-csp i420 --input-depth 10 --input-res 1920x1080 --fps 24000/1001 --output "H:/test.h264"
Checking the encoder sanity.
x264 [error]: No input file. Run x264 --help for a list of options.
Encoder seems sane. Starting.
Encoder started. Beginning encoding.
x264 [error]: No input file. Run x264 --help for a list of options.
Encoder has suddenly stopped accepting data. Aborting.
Encoder has finished working while it shouldn't be running at all. Ignoring.

Executable:
H:/x264-10b-r2694-3b70645.exe
Arguments:

--frames {f}
--preset veryslow
--tune animation
--crf 18
--demuxer raw
--output-csp i{ss}
--input-csp i{ss}
--input-depth {bits}
--input-res {w}x{h}
--fps {fpsn}/{fpsd}
--output "H:/test.h264"

Using the generated command line with VSPipe works fine:

"H:\Videocoding\VapourSynth\VSPipe.exe" "H:\Videocoding\VapourSynth\scripts\Untitled.vpy" - | "H:/x264-10b-r2694-3b70645.exe" --frames 34567 --preset veryslow --tune animation --crf 18 --demuxer raw --output-csp i420 --input-csp i420 --input-depth 10 --input-res 1920x1080 --fps 24000/1001 --output "H:/test.h264" -


You're missing the last "-" in arguments.

[TalasNetrag]

You're missing the last "-" in arguments.

OK. Now its working xD

[dipje]

For what it's worth, I also noticed a few releases back that when you press F5 for the preview it takes the current preview away. The window stays open, but the image disappears and reappears after the new one is done rendering.
In previous versions the old image would stay there until the new one was displayed. Made it very easy to compare the changes you did. Drag the editor window to the side but keep it focused, press F5 while staring at the preview window and you could spot your differences. Newer versions remove and then repop the image. A-Bing is more difficult now :).

[Mystery Keeper]

For what it's worth, I also noticed a few releases back that when you press F5 for the preview it takes the current preview away. The window stays open, but the image disappears and reappears after the new one is done rendering.
In previous versions the old image would stay there until the new one was displayed. Made it very easy to compare the changes you did. Drag the editor window to the side but keep it focused, press F5 while staring at the preview window and you could spot your differences. Newer versions remove and then repop the image. A-Bing is more difficult now :).That's a part of new errors handling logic. You can use snapshots if you need instant A-B'ing or use VapourSynth internal means like stacking and interleaving. Sliding shutter comparison is planned for future.

[TalasNetrag]

Is it possible to autocomplete only the functionname?
video = core.text.Text()
instead of
video = core.text.Text(clip, text, alignment)

[Mystery Keeper]

Is it possible to autocomplete only the functionname?
video = core.text.Text()
instead of
video = core.text.Text(clip, text, alignment)
Right now - no. But such improvements are planned too.

[l33tmeatwad]

Sorry for the lack of updates to the OSX dist, uploaded r10 to the downloads.

[ChaosKing]

The editor (r10) crashes sometimes then I refresh the preview window (aka press F5). It happens sometimes then I add or remove a new filter. No error msg is shown.
The same script works then I restart the editor and it also never crashes if I close the preview window before I press F5.

I'm using vp x64 R35 portable on Window 10 x64

I have visual studio installed and the debugger showed me this (don't know if it helps).
Exception error at 0x00007FFFEF1E8D80 (VapourSynth.dll) in vsedit.exe: 0xC0000005: Access violation at reading 0x00000000000000


p.s. I get also this msg in Log: Core freed but 729600 bytes still allocated in framebuffers

pp.s. Could You add a text search -> STRG+F? :)

[poisondeathray]

Anyone else having difficulty previewing RGB ? YUV formats work , but the preview pops up but is greyed out (empty, not black) with RGB formats

It doesn't matter what type of RGB source, image , etc.. even BlankClip

error message is

Error on frame 0 request:
Resize error 1026: RGB color family cannot be YUV


VapourSynth Editor r10 x64 , VapourSynth r35 installed x64, Windows 8.1 x64



import vapoursynth as vs
core = vs.get_core()
#video = core.std.BlankClip(format=vs.YUV444P8) #this one works
video = core.std.BlankClip(format=vs.RGB24)
video.set_output()

[poisondeathray]

No, I can't. Script processor only knows the output clip. Which clip is "original"? There can be several of them. I use few helper functions to arrange clips in a quartet: 1) original clip 2) processed clip 3) difference between the two 4) processed clip with enhanced local contrast (helps to see artifacts). So I always see them in comparison. Script in attachment. Rename to .py and import.

Thanks for this

Sort of related request, is the avspmod function of having separate "sheets" or tabs where you can use the number keys to flip between versions of scripts . I don't know anything about programming or internals or if it's possible in VapourSynth Editor, or if it's been requested before (I couldn't find it with search)

The reason I find this helpful is alignment - both temporal (same frame number between same base videos) and spatial (easier to compare details when flipping in the same preview space, instead of stacked horizontally or vertically) , and speed (pushing number keys) . Interleave(a,b,c...) works, but not as elegant and can be clunky if you have more than a few versions

[Mystery Keeper]

Thanks for this

Sort of related request, is the avspmod function of having separate "sheets" or tabs where you can use the number keys to flip between versions of scripts . I don't know anything about programming or internals or if it's possible in VapourSynth Editor, or if it's been requested before (I couldn't find it with search)

The reason I find this helpful is alignment - both temporal (same frame number between same base videos) and spatial (easier to compare details when flipping in the same preview space, instead of stacked horizontally or vertically) , and speed (pushing number keys) . Interleave(a,b,c...) works, but not as elegant and can be clunky if you have more than a few versions

If you're talking about comparing several nodes in the script - that was requested and will be implemented eventually. If you're talking about using tabs to work with several scripts - I shall not do that. It is convenient indeed. But it makes several scripts share the same memory. If one script makes the editor crash - you lose your work on all of open scripts.

Bug with previewing RGB confirmed. Fixing.

[Mystery Keeper]

Since preview bug was kind of critical - I'm making a fix release r11.
-BUGFIX: Default file drop template.
-BUGFIX: Preview non-YUV clips.
-An option to keep the currently previewed frame number on previewing different script.

[Mystery Keeper]

Test build (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/vapoursynth-editor-64bit-2016-11-23.7z) with improved log.
Lets you filter the displayed message types and save the log to HTML file.
Please test and tell me what you think of it.

[shader]

First: VapourSynthEditor is a great tool and I like it :)

But unfortunatelly I can't run VapourSynthEditor-r11-32bit, because I get an error (0x000007b)(see attachment) at startup.
In the past I already updated the editor several times (just extract), therefore I do not believe, that I did something wrong this time.

Does anybody know how to fix that problem?

Thanks!

[Mystery Keeper]

First: VapourSynthEditor is a great tool and I like it :)

But unfortunatelly I can't run VapourSynthEditor-r11-32bit, because I get an error (0x000007b)(see attachment) at startup.
In the past I already updated the editor several times (just extract), therefore I do not believe, that I did something wrong this time.

Does anybody know how to fix that problem?

Thanks!Try this. (http://www.gadgetsupersite.com/0xc00007b-error-fix/) Also, reinstall Visual Studio 2015 runtimes.
More info. (http://stackoverflow.com/questions/10492037/the-application-was-unable-to-start-correctly-0xc000007b)

[Mystery Keeper]

r12 is out with improved log.

It supports filtering and settings of styles and saving to HTML file.

[shader]

Try this. (http://www.gadgetsupersite.com/0xc00007b-error-fix/) Also, reinstall Visual Studio 2015 runtimes.
More info. (http://stackoverflow.com/questions/10492037/the-application-was-unable-to-start-correctly-0xc000007b)

Thanks for your help but unfortunatelly it did not work. I tried a lot and looked for other hints on the web later. Maybe Win10 is the reason,I do not know.

But it's not important any more. R12 works again !!!!!

[cylx]

r12 is out with improved log.

It supports filtering and settings of styles and saving to HTML file.
colorful log is wonderful. But I encountered a bug when transcoding directly from vsedit's encode window. Several minutes after starting encode, the speed became very slow and x265's cpu load was also at a low level. Everything would be ok if I encoded the same script with the same arguments by using vspipe. My environment was windows 10 1607 64bit.

Also, the encode log window became not scrollable under r12 version, could you fix it at next versions?

[Mystery Keeper]

colorful log is wonderful. But I encountered a bug when transcoding directly from vsedit's encode window. Several minutes after starting encode, the speed became very slow and x265's cpu load was also at a low level. Everything would be ok if I encoded the same script with the same arguments by using vspipe. My environment was windows 10 1607 64bit.

Also, the encode log window became not scrollable under r12 version, could you fix it at next versions?
Please tell me parameters of your video and your encoding preset.
As for not scrollable log - most likely your encoder is continuously outputting info, and log gets scrolled to the end. It should be scrolling alright when encoding has stopped.
And if you think the log is responsible for the performance drop (it is possible) - try to configure your encoder not constantly output unneeded feedback. Vsedit shows the encoding progress and framerate on its own.

[cylx]

Please tell me parameters of your video and your encoding preset.
As for not scrollable log - most likely your encoder is continuously outputting info, and log gets scrolled to the end. It should be scrolling alright when encoding has stopped.
And if you think the log is responsible for the performance drop (it is possible) - try to configure your encoder not constantly output unneeded feedback. Vsedit shows the encoding progress and framerate on its own.
Yes, log should be responsible for the performance drop. Adding "--no-progress" to x265's arguments fixed this problem.

[juhok]

Thank you for making this software available.

I can confirm gradual log/slowdown with r12 and x264 with Win10/64. "--no-progress" helped.

[Mystery Keeper]

Yes, new log can be slow. Use the encoder settings to suppress the progress output. Clear logs with context menu if necessary.

[Mystery Keeper]

r13 is out with y4m header for video encoding.

Sample presets:

ffmpeg - FFV1:
-y
-nostats
-i -
-c:v ffv1
"{sd}/{sn}.mkv"

x264:
--demuxer y4m
--pass 1
--bitrate 3000
--stats "{sd}/{sn}.stats"
--slow-firstpass
--min-keyint 1
--b-adapt 2
--ref 5
--vbv-init 1.0
--ratetol 20.0
--cplxblur 5
--rc-lookahead 250
--aq-mode 1
--merange 64
--me tesa
--subme 11
--partitions all
--trellis 2
--no-dct-decimate
--no-fast-pskip
--stitchable
--direct auto
--no-psy
--no-progress
-
-o "{sd}/{sn}.mkv"

x265:
--y4m
--stats "{sd}/{sn}.stats"
--pass 1
--bitrate 3000
--no-progress
--rd 6
--rd-refine
--cu-lossless
--max-merge 5
--ref 16
--me full
--subme 7
--merange 64
--no-open-gop
--allow-non-conformance
-
-o "{sd}/{sn}.h265"

[ChaosKing]

The editor (r10) crashes sometimes then I refresh the preview window (aka press F5). It happens sometimes then I add or remove a new filter. No error msg is shown.
The same script works then I restart the editor and it also never crashes if I close the preview window before I press F5.



It seems like that this is no longer the case in R13. No crashes so far! :D

Edit: or maybe not ... but it happens less often now.

[Sm3n]

I found the way to use Interleave. Now I would like to know the nature of each frame (P, B and so) to make comparison.
How do I do that? Is that possible?
Also, does VSE support multi tab? I'm pretty sure I didn't see this option. There must be a reason why ^^

Thx in advance.

[Mystery Keeper]

I found the way to use Interleave. Now I would like to know the nature of each frame (P, B and so) to make comparison.
How do I do that? Is that possible?
Also, does VSE support multi tab? I'm pretty sure I didn't see this option. There must be a reason why ^^

Thx in advance.It is not possible. Frame type only makes sense in context of encoding. In VapourSynth they all become equal uncompressed frames.

There are no tabs in VSE, and I am against adding them. Previewing multiple tabs would be confusing. And the main reason for not using tabs is that crash in one script processing would kill your work on other scripts as well.

[Myrsloik]

It is not possible. Frame type only makes sense in context of encoding. In VapourSynth they all become equal uncompressed frames.

There are no tabs in VSE, and I am against adding them. Previewing multiple tabs would be confusing. And the main reason for not using tabs is that crash in one script processing would kill your work on other scripts as well.

Print the frame properties. FFMS2 attaches the decoded frame type if you use that. I don't think any other decoder does it though.

[Sm3n]

It is not possible. Frame type only makes sense in context of encoding. In VapourSynth they all become equal uncompressed frames.
Even if I load the source and the encode?
My goal is precisely to compare my encode to the source. Let say I load in "a=" the source then in "b=" the encode. If the frame are "lossless" can't I still comparing it?

There are no tabs in VSE, and I am against adding them. Previewing multiple tabs would be confusing. And the main reason for not using tabs is that crash in one script processing would kill your work on other scripts as well.

I understand.

Print the frame properties. FFMS2 attaches the decoded frame type if you use that. I don't think any other decoder does it though.

It was my first idea in fact.^^ Loading the videos and using the avisynth ffinfo to display these informations.

@Mystery Keeper @Myrsloik Can't I use ffinfo the same way in VS than in avs? What would be the option to add to the script?

[Myrsloik]

...
@Mystery Keeper @Myrsloik Can't I use ffinfo the same way in VS than in avs?

It's attached as a frame property. Simpy use FrameProps() to print it all.

[Sm3n]

It's attached as a frame property. Simpy use FrameProps() to print it all.

Very nice. There is even FrameNum() that could help.

Cheers

[Mystery Keeper]

r14 is out with few new features and fixes.
-BUGFIX: Encoding logic.
-Core buffer usage display.
-Relative paths are resolved from the application directory, not CWD.
-Benchmark and encoding progress in window title.
-MS Windows: taskbar button progress for benchmark and encoding.
-Script dialogs status bar reorganized.
-WebP snapshots support.

[Izuchi]

Is it possible to change the handling on commenting/uncommenting lines? I think it would be a lot more convenient if there was just one hotkey that toggles commenting on/off for a particular line which is how AvsPmod implements it.

[Mystery Keeper]

Is it possible to change the handling on commenting/uncommenting lines? I think it would be a lot more convenient if there was just one hotkey that toggles commenting on/off for a particular line which is how AvsPmod implements it.Subjective. I like it the way it is now. Would you like one more hotkey for it? Which?

[l33tmeatwad]

Uploaded r14 to the OSX distribution page, sorry for the lack of updates as I have been working on my own project here recently.

[Izuchi]

Subjective. I like it the way it is now. Would you like one more hotkey for it? Which?

Would be nice to have in my opinion. Maybe Ctrl+E?

[sl1pkn07]

Why not configurable?

[ChaosKing]

I just wanted to report that after updating to vp R36 I hadn't any editor crashes since then!

[Mystery Keeper]

I just wanted to report that after updating to vp R36 I hadn't any editor crashes since then!Thank you for good news.

[ChaosKing]

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. Now this msg is shown in the Log:


File "mylogo.py", line 16, in Logo
cut + \
File "src\cython\vapoursynth.pyx", line 1126, in vapoursynth.VideoNode.__add__ (src\cython\vapoursynth.c:24935)
File "src\cython\vapoursynth.pyx", line 1604, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:33131)
vapoursynth.Error: Splice: nodes foreign to this core passed as input, improper api usage detected


So this happens only in the second preview window call.
I also have no errors with encoding via vspipe etc.

//EDIT
No issues when I copy the import code to my main script.

----------------
I have an import that looks like this:



import vapoursynth as vs
#import havsfunc as haf
core = vs.get_core()



def Logo(clip, start):

logo = core.ffms2.Source(source= "mylogo.mkv")
end = start + logo.num_frames - 1

#cut = clip.std.Trim(start,end)
cut = logo
clip = clip.std.Trim(0,start-1)+ \
cut + \
clip.std.Trim(end+1)

#clip = clip.std.Trim(0,start-1) + cut + clip.std.Trim(end+1) # makes no difference
return clip

And my script:


import mylogo as db


def insertLogos(clip):
clip = db.Logo(clip, 118)
# etc
return clip

clip = core.ffms2.Source(source=myvideo)
clip = insertLogos(clip)
clip.set_output()

[Mystery Keeper]

r15 is out:
-BUGFIX: crash on colour picking while refreshing preview.
-BUGFIX: random junk instead of black frame on preview refresh.
-BUGFIX: wrong hours displayed in estimated finish time for benchmark and encoding.
-Buildable with Qt version lower than 5.4.
-Float formats support in yuv4mpeg video header for encoding.