VapourSynth Editor

[Selur]

Would you like an option to synchronize preview fixed zoom with crop zoom?
Yes, that would be nice. (since my main machine is on a 5k monitor, cropping SD and HD content always requires to zoom in)

Any thoughts about the play functionality and changed GUI responsiveness?
Didn't have any problems with the responsiveness before, so I didn't really see a change there. ;)
Playback worked nice so far. Took me a while to find that I had to press on 'Show timeline panel'-button to find the 'play'-button. :)

[feisty2]

5k, iMac then

[Selur]

Nope, using a HP Z27q 5k as monitor on my main machine which is a Win10/Linux dual-boot system (I also got an mac mini, but that one is hooked up to a normal HD Eizo display).

[Mystery Keeper]

Another treat for you, Windows users. (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/vapoursynth-editor-64bit-play-benchmark-encode.7z)
A much more stable build with implemented benchmarking and somewhat working CLI encoding. Encoding is just a draft. Expect bugs on a slightest mistake in arguments or frame format. Release version will have encoding profiles management.
The build comes with predefined settings for ProRes 422 encoding via ffmpeg. Video must be in YUV422P10 for it to work.

[trip_let]

Cool, thanks.

btw that is quite a number of digits reported on the benchmark FPS.

http://i.imgur.com/9ZE8uyT.png

[brucethemoose]

I like the new benchmark.


Small feature request: could you add a button that lets us compare the original frame to the processed one in the preview window?

Press button: original frame is show.

Press button again: processed frame is shown.

Example of that in action:

http://www.screenshotcomparison.com/comparison/185123

This would be immensely helpful for tuning VS filters. I do it manually now, but it's rather clunky.

Some AS editors have a more complicated version of that, but honestly I like the simplicity of a comparison button.

[Mystery Keeper]

I like the new benchmark.


Small feature request: could you add a button that lets us compare the original frame to the processed one?

Press button: original frame is show.

Press button again: processed frame is shown.

This would be immensely helpful for tuning VS filters. I do it manually now, but it's rather clunky.

Some AS editors have a more complicated version of that, but honestly I like the simplicity of a comparison button.

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.

[brucethemoose]

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.

Oh, right, I forgot that VS Editor isn't the thing importing the video.

I guess you could compare the same frames in 2 seperate scripts, but that's complicated to implement (as VS Editor would have to handle another script).


Thanks for the helper script.

[shekh]

It is quite funny to compare things in my latest VD build (hope this adds to subject)

http://s14.postimg.org/6ini754s1/compare.png

How it works:
1) open script
2) add filter (fflayer) with source video
3) close filter config and open filter blending

withing filter blending you have preview, color picker and blending options:
Apply opacity curve by coincidence acts as on/off toggle (because default state for curve is all off)
Another option is to move left/top etc. margin, this behaves as "onion skinning"

[Mystery Keeper]

GUI filter sounds nice. Though requires a lot of preprocessor magic to code in cross-platform way.

Upd: It happens that VapourSynth supports multiple outputs. I could use it to implement different comparison techniques.

[Mystery Keeper]

New Windows build (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/vapoursynth-editor-64bit-encoding.7z) with supposedly completely handled encoding. Please test extensively while I'm implementing profiles. It also has a bug in playback fixed.

[groucho86]

On both l33tmeatwad OSX's installer and manually compiling the latest version, I'm getting the following issue:

I cannot get an image preview unless the preview size is set to x0.75 or 0.25 Bilinear (edit: actually it's currently working at 0.5).
Fit to Frame works well as long as (I think) the image is under x1.0

Anything else returns either a black image or a corrupt rendered image:
http://forum.doom9.org/attachment.php?attachmentid=15593&stc=1&d=1474657307

[Mystery Keeper]

On both l33tmeatwad OSX's installer and manually compiling the latest version, I'm getting the following issue:

I cannot get an image preview unless the preview size is set to x0.75 or 0.25 Bilinear (edit: actually it's currently working at 0.5).
Fit to Frame works well as long as (I think) the image is under x1.0

Anything else returns either a black image or a corrupt rendered image:
http://forum.doom9.org/attachment.php?attachmentid=15593&stc=1&d=1474657307Sounds like a Qt bug. Try updating Qt?

[groucho86]

I had compiled it with 5.6.0. Just tried with 5.6.1 and I have the same issue.

[Mystery Keeper]

And what if you set zooming to "No zoom"?

[groucho86]

And what if you set zooming to "No zoom"?

The preview looks corrupt.

It appears that only 0.25, 0.50 and 0.75 work (bilinear, not nearest).

My graphics card is by no means impressive (ATI Radeon HD 5770) but I am able to successfully render using vspipe and ffmpeg.
I wonder if it is a graphics card limitation... (Hoping to get a new one relatively soon)

[brucethemoose]

The preview looks corrupt.

It appears that only 0.25, 0.50 and 0.75 work (bilinear, not nearest).

My graphics card is by no means impressive (ATI Radeon HD 5770) but I am able to successfully render using vspipe and ffmpeg.
I wonder if it is a graphics card limitation... (Hoping to get a new one relatively soon)

It works on my 6620G IGP, which is the same generation as your 5770.

Maybe try a fresh graphics driver install, just to rule it out? Uninstall normally, run DDU, install your driver.

[Mystery Keeper]

It shouldn't have anything to do with graphic driver.

[jackoneill]

It may be helpful to show that same frame when it's not corrupted.

[Mystery Keeper]

VapourSynth Editor r⑨ is here with new awesome features:
-Asynchronous frames processing. More responsive GUI.
-Preview video playback.
-Script processing benchmarking.
-Encoding video with CLI tools.

Links are in the first post.

It is called r⑨ for a reason. Barely tested. Colour picking is broken in play mode. It will be fixed in next release along with more internal changes.

To moderators: may this thread be made sticky please?

[trip_let]

Nice update. Asynchronous frames processing now too.

So nice I have a feature request now. Do you think you could have an encoding video preset/option that reads the parameters from the script itself? That is, you leave a special commented line in the .vpy and it grabs this.

Something like this in the script:
# ;Executable; x265-10b
# ;Arguments; --input - --input-res %wx%h --fps %fpsn/%fpsd --input-depth %bits --preset slower --deblock 1:0 --crf 18 --qcomp 0.65 -o %sd/%sn.hevc
import vapoursynth as vs
core = vs.get_core()
blah

and then it would search the script for the ;Executable; and ;Arguments; lines and use those. This way the encoding parameters you use are documented in the script. If nobody else thinks this might be useful, then don't bother. It would take some kind of documentation, and regardless you can always just paste into the box.

[Mystery Keeper]

trip_let, I gave it a thought and decided against it. It doesn't sit well with the jobs schedule feature I want to implement. It is meant for multi-pass encoding. And you might want to encode your script with different encoders and compare. So why let the script decide how it should be encoded? You've got presets now, so you don't need to copy-paste all that much.

Upd: Though what I do want to implement is conditional functions in arguments that change the string depending on user provided condition. That would also let us put special tags into script to set special parameters that do belong to the script, but can not be evaluated otherwise. For example - DAR.

[groucho86]

It may be helpful to show that same frame when it's not corrupted.

Sorry this won't be very useful... On Friday things looked really funky, right now it just looks black.

At x0.75:
http://forum.doom9.org/attachment.php?attachmentid=15601&stc=1&d=1474906676

At x1.00:
http://forum.doom9.org/attachment.php?attachmentid=15602&stc=1&d=1474906676

Despite it looking black, the YUV picker is detecting colors...

[Mystery Keeper]

Colour picker reads values from the frame itself, not from its converted pixmap representation. Your problem is with QPixmap, not the editor code.

[Selur]

What files is vsedit looking for when it's complaining about:
VapourSynth script processor: Failed to load vapoursynth script library!
Please set up the library search paths in settings.

[Mystery Keeper]

What files is vsedit looking for when it's complaining about:"vsscript.dll" on Windows or "vapoursynth-script.so" on Linux.

[Boulder]

Hitting F6 to refresh the preview also moves the preview display back to the default position (upper left corner). The previous versions remembered where I had zoomed in to inspect the preview.

[Mystery Keeper]

Hitting F6 to refresh the preview also moves the preview display back to the default position (upper left corner). The previous versions remembered where I had zoomed in to inspect the preview.I believe you meant F5. Interesting. I shall look into that.

[Boulder]

No, F6 is the preview while F5 just parses the script. I just noticed this odd behaviour today although I've used the latest version for some time now :)

[Mystery Keeper]

No, F6 is the preview while F5 just parses the script. I just noticed this odd behaviour today although I've used the latest version for some time now :)Your hotkeys look swapped. Check your hotkey settings, unless you deliberately swapped them. However, reposition bug is indeed occurring.

[Boulder]

Your hotkeys look swapped. Check your hotkey settings, unless you deliberately swapped them. However, reposition bug is indeed occurring.Oh yes, I probably did that a long time ago. Checking the script and then previewing the output goes more logically from a smaller function key to larger :)

Good that you can also see the odd behaviour.

[Mystery Keeper]

Oh yes, I probably did that a long time ago. Checking the script and then previewing the output goes more logically from a smaller function key to larger :)

Good that you can also see the odd behaviour.It is not really an odd behaviour. It is safe behaviour. I'm trying to make the preview dialog to remember position again while properly handling errors. If it makes the code too complicated - I might ditch the idea and keep new behaviour.

Upadate: And fixed! Now preview scrolling and frame number are kept for the same script file and reset for the new one. Have a nice test build with bug fixes and editor improvements, everyone. But I'm not done yet. Want to implement snippets before releasing r10.
VapourSynth Editor 64bit 2016-10-16 (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/vapoursynth-editor-64bit-2016-10-16.7z)

[sl1pkn07]

wen save screenshot from preview window


Qt warning: Invalid URL: QUrl("1080p.vpy - 44757.png")


the image is saved without problem. but the warning is show in the vsedit log

[Boulder]

Upadate: And fixed! Now preview scrolling and frame number are kept for the same script file and reset for the new one. Have a nice test build with bug fixes and editor improvements, everyone. But I'm not done yet. Want to implement snippets before releasing r10.
VapourSynth Editor 64bit 2016-10-16 (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/vapoursynth-editor-64bit-2016-10-16.7z)Thanks, I'll give the new version a shot right after I get all the numerous index files ready :)

[Mystery Keeper]

wen save screenshot from preview window


Qt warning: Invalid URL: QUrl("1080p.vpy - 44757.png")


the image is saved without problem. but the warning is show in the vsedit logSuper weird, considering there's no URLs involved in saving a snapshot. Can only be a Qt bug.

[Are_]

This is happening to me too, it happens not when you save but when the text for the filename in the save menu is created. If you start typing every time yo push a key a new message is created.

http://i.imgur.com/2pTGE9G.png

I'm using latest git with Qt-5.6.2 (Linux).

[Mystery Keeper]

This is happening to me too, it happens not when you save but when the text for the filename in the save menu is created. If you start typing every time yo push a key a new message is created.

http://i.imgur.com/2pTGE9G.png

I'm using latest git with Qt-5.6.2 (Linux).
There's nothing I can do about it. But out of curiosity. Does the same happen when you're saving new script?

[sl1pkn07]

yes. the same problem when the script is saved

my Qt5 is 5.7.0

[Mystery Keeper]

Reported the bug to Qt team. That's all I can do about this issue.

Update: Could not reproduce this on Linux Mint 18, Qt 5.5.1.

[Mystery Keeper]

Have a new test build. (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/vapoursynth-editor-64bit-2016-10-20.7z)
New templates dialog with:
- Code snippets to quickly paste into your script.
- New script template.
- File drop templates. Now you can define categories of files with a list of wildcards like "*.mpg;*.mkv;*.mp4" and set a template for each category. When you drop files into your script editor - corresponding templates will be pasted into your script. Dropping multiple files is supported. If you drop a single .vpy file - the editor will prompt you to save your script and open that file.

This is very close to r10, so please give it a thorough testing and report any and all quirks in its work.

[WolframRhodium]

In the latest bulid, "Theme elements - Common script text, Text background color" seems do not work in "Scrip templates - Code snippets".

[Mystery Keeper]

In the latest bulid, "Theme elements - Common script text, Text background color" seems do not work in "Scrip templates - Code snippets".Ugh. Indeed. It is not working in the main window either. Shall fix.
Update: Recompiled, and now it does work in the main window, but not in snippets. Super weird, considering all script editors are treated evenly. Still on it.
Update 2: Fixed in Git.

[Mystery Keeper]

New test build. (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/vapoursynth-editor-64bit-2016-10-23.7z)
-Optional highlighting of selection matches in script editor.
-Timeline bookmarks with auto-saving/loading bookmarks files along with the script file. Timeline has new operation mode. With CTRL key pressed mouse navigation on timeline snaps to the closest bookmarks.
-Various bugs and usability fixes.
-Some default hotkeys have been changed. You may need to revise your hotkey settings.

And that's it with new features for r10. I shall only be refining the code and fixing bugs. Please give this build a super-thorough testing and expect a release soon.

[dipje]

If QUrl reports 'invalid url' isn't that simply because you aren't given it an URL or url-scheme, but just a file name?
Use the file:/ url scheme (so instead of 'test.png' use 'file:test.png') or use the staticd QUrl::fromLocalFile() to generate the QUrl object if you're working with local files.

Not knowing your source but is there a reason you seem to using QUrl everywhere where file opening / saving is involved and not regular QFile's or something similar? You want everything to be internet-remote-ready or something?

[Mystery Keeper]

If QUrl reports 'invalid url' isn't that simply because you aren't given it an URL or url-scheme, but just a file name?
Use the file:/ url scheme (so instead of 'test.png' use 'file:test.png') or use the staticd QUrl::fromLocalFile() to generate the QUrl object if you're working with local files.

Not knowing your source but is there a reason you seem to using QUrl everywhere where file opening / saving is involved and not regular QFile's or something similar? You want everything to be internet-remote-ready or something?What you're saying is right. Thing is: I have nothing to do with it. I just use QFileDialog::getSaveFileName() function, and it does the QUrl manipulations inside.
I made my program display all messages from Qt, and it is good. It does help finding bugs. So it will stay this way.

[trugulum78]

Hi, first of all. thanks for your work and sorry for my bad english.
I usually work with vspipe from cli, but I'm trying to do it from the editor. How do I tell input? Does the executable and arguments are x264?
I'm in ArchLinux,and all is working fine.
Thanks in advance.

[Are_]

Hi, first of all. thanks for your work and sorry for my bad english.
I usually work with vspipe from cli, but I'm trying to do it from the editor. How do I tell input? Does the executable and arguments are x264?
I'm in ArchLinux,and all is working fine.
Thanks in advance.

vseditor outputs raw frames, so an example for x264 would be:
Executable:
x264

Arguments:
--crf 15
--demuxer raw
--colormatrix bt709
--input-depth %bits
--input-range tv
--output-csp i444
--input-csp i444
--input-res %wx%h
--fps %fpsn/%fpsd
--output %sn.mkv
-

That's for YUV444P10 video, use x264 --fullhelp for more info on what to put in "--input-csp" and "--output-csp".

It would be nice if there was a variable for "total frames" so the encoder could provide ETA estimations.

[Mystery Keeper]

It would be nice if there was a variable for "total frames" so the encoder could provide ETA estimations.Shall do!

[trugulum78]

"vseditor outputs raw frames"
That was the point!
Thanks Are_ ,all working now.
Regards.

[Mystery Keeper]

And finally r10 is out.

VapourSynth Editor r10 32bit (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/VapourSynthEditor-r10-32bit.7z)
VapourSynth Editor r10 64bit (https://bitbucket.org/mystery_keeper/vapoursynth-editor/downloads/VapourSynthEditor-r10-64bit.7z)

Tons of improvements:
-BUGFIX: Colour picking.
-BUGFIX: VapourSynth messages handling.
-BUGFIX: Frame processing errors handling in different modes.
-BUGFIX: Pasting crop snippet into the last script line.
-BUGFIX: Benchmark and encode dialogs forward initialization error to main window log and hide on error if open.
-Crashlog on VapourSynth fatal errors.
-Keep preview scrolling and frame number on refreshing the same script.
Reset on previewing new script. Unsaved script preview is always reset.
-Editor: selected text/current line duplication action.
-Editor: comment/uncomment selected lines actions.
-Editor: multiline tab and backtab.
-Options to use spaces as Tab and set Tab size.
-Editor: Replace Tab characters with spaces action.
-Editor: smart Home key behaviour.
-An option to remember and restore the last previewed frame between sessions.
-New script template setting.
-Code snippets.
-File drop templates.
-Option to highlight selection matches in script editor.
-Timeline bookmarks with auto-saving/loading bookmarks file along the script file.
-Remember timeline panel visibility.
-Most timeline colours are bound to OS theme.
-Changes in default standard hotkeys. Many default hotkeys are now OS-dependent. CTRL + arrows in preview window now move between bookmarks and CTRL + SHIFT + arrows jump time intervals.
-Frames number and subsampling string tokens in encoder.
-Estimated finish time output in benchmark and encoder.
-Encoder argument tokens format changed into more readable one.
-Colour picker moved into status bar.
-Paste shown frame number into script action.

Might be a long time till next major release. Rather complex features planned. Enjoy!