VapourSynth Editor - Page 11

Selur · 16th September 2016, 15:55

Quote:

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)

Quote:

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 · 17th September 2016, 08:15

5k, iMac then

Selur · 17th September 2016, 08:19

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 · 20th September 2016, 17:24

Another treat for you, Windows users.
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 · 20th September 2016, 20:05

Cool, thanks.

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

brucethemoose · 22nd September 2016, 03:04

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 · 22nd September 2016, 03:16

Quote:

Originally Posted by 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?

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 · 22nd September 2016, 03:29

Quote:

Originally Posted by Mystery Keeper

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 · 22nd September 2016, 12:04

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

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 · 22nd September 2016, 16:36

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 · 23rd September 2016, 11:48

New Windows build with supposedly completely handled encoding. Please test extensively while I'm implementing profiles. It also has a bug in playback fixed.

groucho86 · 23rd September 2016, 20:02

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:

Mystery Keeper · 23rd September 2016, 20:44

Quote:

Originally Posted by 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:

Sounds like a Qt bug. Try updating Qt?

groucho86 · 23rd September 2016, 22:00

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

Mystery Keeper · 23rd September 2016, 22:02

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

groucho86 · 23rd September 2016, 22:32

Quote:

Originally Posted by Mystery Keeper

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 · 24th September 2016, 03:03

Quote:

Originally Posted by groucho86

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 · 24th September 2016, 03:11

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

jackoneill · 24th September 2016, 17:58

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

Mystery Keeper · 25th September 2016, 03:56

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?

17th September 2016, 08:19	#203 \| Link
Selur Registered User Join Date: Oct 2001 Location: Germany Posts: 7,277	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). __________________ Hybrid here in the forum, homepage

20th September 2016, 17:24	#204 \| Link
Mystery Keeper Beyond Kawaii Join Date: Feb 2008 Location: Russia Posts: 724	Another treat for you, Windows users. 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. __________________ ...desu!

22nd September 2016, 03:04	#206 \| Link
brucethemoose Registered User Join Date: Sep 2016 Posts: 67	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. Last edited by brucethemoose; 22nd September 2016 at 03:08.

22nd September 2016, 12:04	#209 \| Link
shekh Registered User Join Date: Mar 2015 Posts: 775	It is quite funny to compare things in my latest VD build (hope this adds to subject) 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" __________________ VirtualDub2

22nd September 2016, 16:36	#210 \| Link
Mystery Keeper Beyond Kawaii Join Date: Feb 2008 Location: Russia Posts: 724	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. __________________ ...desu! Last edited by Mystery Keeper; 22nd September 2016 at 17:45.

17th September 2016, 08:15	#202 \| Link
feisty2 I'm Siri Join Date: Oct 2012 Location: void Posts: 2,633	5k, iMac then

20th September 2016, 20:05	#205 \| Link
trip_let Registered User Join Date: Sep 2012 Posts: 47	Cool, thanks. btw that is quite a number of digits reported on the benchmark FPS.

23rd September 2016, 11:48	#211 \| Link
Mystery Keeper Beyond Kawaii Join Date: Feb 2008 Location: Russia Posts: 724	New Windows build with supposedly completely handled encoding. Please test extensively while I'm implementing profiles. It also has a bug in playback fixed. __________________ ...desu!

23rd September 2016, 20:02	#212 \| Link
groucho86 Registered User Join Date: Apr 2016 Posts: 85	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: Attached Images

23rd September 2016, 22:00	#214 \| Link
groucho86 Registered User Join Date: Apr 2016 Posts: 85	I had compiled it with 5.6.0. Just tried with 5.6.1 and I have the same issue.

23rd September 2016, 22:02	#215 \| Link
Mystery Keeper Beyond Kawaii Join Date: Feb 2008 Location: Russia Posts: 724	And what if you set zooming to "No zoom"? __________________ ...desu!

24th September 2016, 03:11	#218 \| Link
Mystery Keeper Beyond Kawaii Join Date: Feb 2008 Location: Russia Posts: 724	It shouldn't have anything to do with graphic driver. __________________ ...desu!

24th September 2016, 17:58	#219 \| Link
jackoneill unsigned int Join Date: Oct 2012 Location: 🇪🇺 Posts: 760	It may be helpful to show that same frame when it's not corrupted. __________________ Buy me a "coffee" and/or hire me to write code!

25th September 2016, 03:56	#220 \| Link
Mystery Keeper Beyond Kawaii Join Date: Feb 2008 Location: Russia Posts: 724	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? __________________ ...desu!