Vapoursynth

[LoRd_MuldeR]

Thanks for the update.

However I noticed that with the new VSPIPE version querying the VapourSynth version doesn't work, which breaks the VapourSynth detection code in my GUI program:

C:\Program Files (x86)\VapourSynth\core32>vspipe.exe -v
No script file specified

C:\Program Files (x86)\VapourSynth\core32>vspipe.exe -version
No output file specified

C:\Program Files (x86)\VapourSynth\core32>vspipe.exe --version
No script file specified

VapourSynth detection is running, please stand by...
VSPIPE.EXE failed with code 0x00000001 -> disable Vapousynth support!
VapourSynth thread finished.
VapourSynth thread failed to detect installation!

Also, maybe more a cosmetic problem, but anyway: Is it supposed to show those $s's there?

VSPipe usage:
  $s [options] <script> <outfile>

Examples:
  Show script info:
    $s --info script.vpy -

BTW: Changing the CLI syntax in a non-backward-compatible way is generally bad for GUI front-end's, since we either need to support old and new variants (which is pain) or we support only a specific VapourSynth version (then user is doomed if program A wants VapourSynth r23 and program B wants VapourSynth r24).

[Myrsloik]

VapourSynth R24 test 3

Fixes the vspipe issues.

Originally Posted by LoRd_MuldeR

...

BTW: Changing the CLI syntax in a non-backward-compatible way is generally bad for GUI front-end's, since we either need to support old and new variants (which is pain) or we support only a specific VapourSynth version (then user is doomed if program A wants VapourSynth r23 and program B wants VapourSynth r24).

I know changing things is bad, that's why I keep a list of major things I'm going to break all at once at an unspecified later time for the core API. The rest of the project is kinda in an evolutionary state though.

However having saner argument parsing is just too attractive to not do it and adding additional options would've been difficult without re-writing it all anyway. Now it follows standard command line conventions and makes more sense. The user base is also still small and fast enough to adapt to the changes. You're the only one making a GUI front end that I know of. Feel free to drop support for older versions of VS if it's too much work. I really try to make each release better than the last, or at least release a fix quickly if a major issue is found.

Anyway, no more major vspipe changes. Now it's done.

[LoRd_MuldeR]

Originally Posted by Myrsloik

VapourSynth R24 test 3

Fixes the vspipe issues.

Confirmed

c:\Program Files (x86)\VapourSynth\core32>vspipe.exe --version
VapourSynth Video Processing Library
Copyright (c) 2012-2014 Fredrik Mellbin
Core r24
API r3

Originally Posted by Myrsloik

Anyway, no more major vspipe changes. Now it's done.

From your lips to God's ears

[zerowalker]

How is Vapoursynth looking?

It's been awhile since it came, so i wonder, is the improvements as expected and all that?

I know it's still far from done, so not expecting it to be comparable, but i just mean in the sense that it's using a more modern approach and how that compares.

[Mystery Keeper]

VapourSynth is rather great. Especially compared to the current state of AviSynth. But it lacks some essential plugins. NNEDI3 is only supporting 8bit colordepth so far. No motion compensation. No DFTTest.

[zerowalker]

How's the speed compared to Avisynth, in stuff that's working as expected?

[Myrsloik]

I'm back AGAIN!

Here's R24 RC1 with a pile of important additional fixes.

Test everything a bit so it doesn't crashe too often. I had to change a lot of python code to fix some of the bugs.

All changes in R24 so far:

r24:
fixed reference leak in FrameEval
more functions in the vsscript api now return success or failure
improved handling of the vsfunc type in python, it should now have all the functionality originally intended
removed r21 argument compatibility since all scripts should have been changed by now
include file paths in the windows sdk have been changed to better match linux and osx
the core will no longer be completely freed until all filter instances belonging to it have been released, this prevents crashes in some circumstances
vsvfw now properly returns an error message when no output has been set instead of silently failing
fixed a reference leak in vsscript
vspipe has a new argument for passing on values to the script environment from the command line 
vspipe now has improved command line parsing and short forms, however old command lines will have to be modified to work
re-added clip.output()
fixed a filter error propagation issue
mixed improvements to vivtc (nodame)
fixed mac compilation of genericfilters
added FreezeFrames, DuplicateFrames and DeleteFrames, they can all delete/duplicate/freeze multiple frames with one command (nodame)
mixed documentation improvements (nodame)
fixed tracking of memory usage that was broken in r22 (nodame)
vivtc now uses framedifference internally and runs completely in parallel, also minor metric reporting fixes (nodame)

[Myrsloik]

Originally Posted by zerowalker

How's the speed compared to Avisynth, in stuff that's working as expected?

About the same speed for single threaded. Good scaling with the number of cores on medium-complex scripts when multithreaded. Not much more to say about it.

[anonymlol]

Originally Posted by Myrsloik

I'm back AGAIN!
Here's R24 RC1 with a pile of important additional fixes.

Chrome is blocking it:

[Myrsloik]

Originally Posted by anonymlol

Chrome is blocking it:

It's chrome acting like shit antivirus software. Use IE or something else to download where you can ignore the warnings.

Installers are regularly blacklisted/blocked by incompetence.

[alexxdls]

Can I maintain aspect ratio while resizing?

v = core.resize.Lanczos(clip=v, width=1920, height=new_height)

new_height = original_height / original_width x 1920

How can I get original_height and original_width with VapourSynth? Please give a detailed example.

[jackoneill]

Originally Posted by alexxdls

Can I maintain aspect ratio while resizing?

v = core.resize.Lanczos(clip=v, width=1920, height=new_height)

new_height = original_height / original_width x 1920

How can I get original_height and original_width with VapourSynth? Please give a detailed example.

http://www.vapoursynth.com/doc/pythonreference.html

new_height = int(v.height / v.width * 1920 + 0.5)

This rounds up to the next integer, which may not be what you need (if you have subsampling).

[alexxdls]

Is it correct calculation (rounding to the neares even value)?

new_height = v.height / v.width * new_width - 0.5
new_height = lambda new_height : round( new_height / 2.) * 2	
v = core.resize.Lanczos(clip=v, width=new_width , height=new_height)

[alexxdls]

import vapoursynth as vs
core = vs.get_core()
import os
core.std.LoadPlugin(path=r"d:\TOOLS\MyDCPConverter\Tools\imwri-64.dll")
core.std.LoadPlugin(path=r"d:\TOOLS\MyDCPConverter\Tools\fmtconv.dll")
ext = 'L.png'
dir = r"F:\TEMP\TRAIN-DRAGON-2_TLR-G-3D_RU-XX_RU-00_51_2K_TCF_20140417_DWA_IOP-3D\REEL1/"
srcs = [dir + src for src in os.listdir(dir) if src.endswith(ext)]
vl1 = core.imwri.Read(srcs)
vl1 = core.fmtc.matrix(vl1, mat="709", col_fam=vs.YUV, csp=vs.YUV444P16, bits=16, fulls=1, fulld=1)
vl = vl1
dir = r"F:\TEMP\TRAIN-DRAGON-2_TLR-G-3D_RU-XX_RU-00_51_2K_TCF_20140417_DWA_IOP-3D\REEL2/"
srcs = [dir + src for src in os.listdir(dir) if src.endswith(ext)]
vl2 = core.imwri.Read(srcs)
vl2 = core.fmtc.matrix(vl2, mat="709", col_fam=vs.YUV, csp=vs.YUV444P16, bits=16, fulls=1, fulld=1)
vl = vl + vl2
vl = core.std.CropRel(vl, left=15, right=15, top=0, bottom=0)
new_height = round(vl.height / vl.width * 1920 / 2) * 2
vl = core.resize.Lanczos(vl, width=1920, height=new_height)
border_height = round((1080 - vl.height) / 2)
vl = core.std.AddBorders(vl, top=border_height, bottom=border_height)
ext = 'R.png'
dir = r"F:\TEMP\TRAIN-DRAGON-2_TLR-G-3D_RU-XX_RU-00_51_2K_TCF_20140417_DWA_IOP-3D\REEL1/"
srcs = [dir + src for src in os.listdir(dir) if src.endswith(ext)]
vr1 = core.imwri.Read(srcs)
vr1 = core.fmtc.matrix(vr1, mat="709", col_fam=vs.YUV, csp=vs.YUV444P16, bits=16, fulls=1, fulld=1)
vr = vr1
dir = r"F:\TEMP\TRAIN-DRAGON-2_TLR-G-3D_RU-XX_RU-00_51_2K_TCF_20140417_DWA_IOP-3D\REEL2/"
srcs = [dir + src for src in os.listdir(dir) if src.endswith(ext)]
vr2 = core.imwri.Read(srcs)
vr2 = core.fmtc.matrix(vr2, mat="709", col_fam=vs.YUV, csp=vs.YUV444P16, bits=16, fulls=1, fulld=1)
vr = vr + vr2
vr = core.std.CropRel(vr, left=15, right=15, top=0, bottom=0)
vr = core.resize.Lanczos(vr, width=1920, height=new_height)
border_height = round((1080 - vr.height) / 2)
vr = core.std.AddBorders(vr, top=border_height, bottom=border_height)
v = core.std.StackHorizontal([vl,vr])
v = core.std.AssumeFPS(v, fpsnum=24)
v = core.fmtc.resample(v, css="420")
v = core.fmtc.bitdepth(v, bits=8, dmode=3)
v.set_output()

I get an error

unable to destroy mutex: Resource device

trying to encode this script. The same thing in FRIMEncode and x264 (with vspipe). Checking the script with VapourSynthEditor-64bit goees well

Script was successfully evaluated. Output video info:
Frames: 72 | Time: 0:00:03.000 | Size: 3840x1080 | FPS: 24/1 = 24 | Format: YUV420P8

But previewing fails and VapourSynthEditor-64bit crushes.

[Mystery Keeper]

Evaluates, but crashes on processing? The error is in GetFrame().

[alexxdls]

Replacing

v = core.std.StackHorizontal([vl,vr])

with

v = vl + vr

or

v = core.std.StackHorizontal([vr,vr])

or

v = core.std.StackHorizontal([vl,vl])

gives positive result and VapourSynthEditor-64bit doesn't crash anymore.
Even the simplest script with one frame in vl and vr crushes the same way

import vapoursynth as vs
core = vs.get_core()
import os
core.std.LoadPlugin(path=r"d:\TOOLS\MyDCPConverter\Tools\imwri-64.dll")
core.std.LoadPlugin(path=r"d:\TOOLS\MyDCPConverter\Tools\fmtconv.dll")
vl = core.imwri.Read(r"F:\TEMP\TRAIN-DRAGON-2_TLR-G-3D_RU-XX_RU-00_51_2K_TCF_20140417_DWA_IOP-3D\REEL2\000034L.png")
vr = core.imwri.Read(r"F:\TEMP\TRAIN-DRAGON-2_TLR-G-3D_RU-XX_RU-00_51_2K_TCF_20140417_DWA_IOP-3D\REEL2\000034R.png")
v = core.std.StackHorizontal([vl,vr])
v.set_output()

Script was successfully evaluated. Output video info:
Frames: 1 | Time: 0:00:00.033 | Size: 4096x858 | FPS: 30/1 = 30 | Format: RGB48

What is wrong with std.StackHorizontal???

[Myrsloik]

Originally Posted by alexxdls

What is wrong with std.StackHorizontal???

I will take a look at it. I just happen to have plenty of other things as well to test. And a job. Posting in more threads about it won't make me happier or make me work faster.

[nu774]

Build of vapoursynth.pyd fails here (on windows) due to failure of "cimport windows". I needed to create the following file named "windows.pxd" placed under Cython directory.

cdef extern from "windows.h" nogil:
    bint WriteFile(void *hFile, void *lpBuffer, int nNumberOfBytesToWrite, int *lpNumberOfBytesWritten, void *lpOverlapped) nogil

[Myrsloik]

Originally Posted by nu774

Build of vapoursynth.pyd fails here (on windows) due to failure of "cimport windows". I needed to create the following file named "windows.pxd" placed under Cython directory.

cdef extern from "windows.h" nogil:
    bint WriteFile(void *hFile, void *lpBuffer, int nNumberOfBytesToWrite, int *lpNumberOfBytesWritten, void *lpOverlapped) nogil

I forgot to add it. It's committed now.

[alexxdls]

Originally Posted by Myrsloik

Posting in more threads about it won't make me happier or make me work faster.

I sumply thought it is VS and Python issue and posted here. But then did some optimizations with my script to have just basic funtions to use Stack. And tests pointed me out that it could be the plugin issue.