Vapoursynth

[kolak]

Will it be possible to do something like virtual file system?

http://forum.doom9.org/showthread.php?t=133313

[active1]

thanx! i'll try it now
stupid question: what is the advantage of VapourSynth over Avisynth MT?

[Myrsloik]

Originally Posted by kolak

Will it be possible to do something like virtual file system?

http://forum.doom9.org/showthread.php?t=133313

I suppose so. You could probably reuse quite a bit of the sourcecode so replacing avisynth as the backend should be quick. Or so my 15 second survey of the sourcecode tells me.

Originally Posted by active1

thanx! i'll try it now
stupid question: what is the advantage of VapourSynth over Avisynth MT?

VapourSynth may one day have all its threading issues fixed. I'm not so optimistic about avisynth mt...

And with that I return to my debugger.

[Rumbah]

The site seems to be down, is there another way to download it?

[sneaker_ger]

http://www.mediafire.com/?64s562ufwy8x7fp (Windows r2)

[Myrsloik]

Originally Posted by Rumbah

The site seems to be down, is there another way to download it?

Not for the moment, no. I will make a third release once it's back up. I guess you get what you pay for... and I pay $1.78/month.

Anyway, have some performance comparisons from r3 while you wait:

Avisynth 2.5.8
$ time avs2yuv.exe test.avs - > NUL
test.avs: 640x368, 24000/1001 fps, 5000 frames
 
real    1m23.680s
user    0m0.000s
sys     0m0.015s
 
VapourSynth r3:
$ time /c/Python32/python.exe test.py > NUL
 
real    0m23.753s
user    0m0.015s
sys     0m0.000s

Script:

import vapoursynth as vs
import sys
core = vs.Core(threads=4)
core.avs.LoadPlugin(path='ffms2.dll')
core.avs.LoadPlugin(path='mvtools2.dll')
ret = core.avs.FFVideoSource(source='possible rule 6 violation.avi', threads=0)
ret = core.std.Trim(clip=ret, first=10000, length=5000)

src = ret
c = core.avs.MSuper(c1=src)
b1v = core.avs.MAnalyse(c1=c, delta=1, isb=False)
f1v = core.avs.MAnalyse(c1=c, delta=1, isb=True)
b2v = core.avs.MAnalyse(c1=c, delta=2, isb=False)
f2v = core.avs.MAnalyse(c1=c, delta=2, isb=True)
ret = core.avs.MDegrain2(c1=src, c2=c, c3=b1v, c4=f1v, c5=b2v, c6=f2v)
ret.output(sys.stdout, y4m=True)

[active1]

wow, vapoursynth is really awesome!
thank you Myrsloik
Q: can i load avsi scripts with it?

Originally Posted by Myrsloik

I'm not so optimistic about avisynth mt...

can you explain 'why' a little?

[hajj_3]

Originally Posted by active1

can you explain 'why' a little?

because there has been virtually no development on avisynth for ages. Vapoursynth is already good and judging by the speed of changes i'm sure we'll have a great version ready within a few months with lots of added features.

[Myrsloik]

The website has stopped sleeping. R3 has been released. It has greatly improved avisynth plugin compatibility and many other fixes. Most notably mvtools works perfectly now so someone crazy could try porting the QTGMC script.

Next on the list is probably adding more things related to frame properties so they can become useful, including a port of ffms2.

[-Vit-]

I've been thinking about the QTGMC port, if I get some time this weekend I'll have a go.

[Keiyakusha]

Not working...

[Myrsloik]

Originally Posted by Keiyakusha

Not working...

\ is the escape character for python strings, just like in C.
Either write path=r'c:\blah.dll', path='c:/blah.dll' or path='c:\\blah.dll' to make it work as expected.

[Keiyakusha]

Oh yes, this way it works... Sorry.

[-Vit-]

I get problems encoding through y4m to x264 with core threads at anything other than 1. Affects any source. Can post scripts if you wish, but it's just a pass-through python script (FFVideoSource) & generic x264 settings. Get errors like this and encode terminates early (usually after a few frames, but a non-deterministic #):
y4m [error]: bad header magic (82848485 <=> àääéé)
y4m [error]: bad header magic (41524682 <=> éFRAM)

Thread count on FFVideoSource works fine. No problems so far experimenting with 1 core thread.

[JEEB]

Originally Posted by -Vit-

I get problems encoding through y4m to x264 with core threads at anything other than 1. Affects any source. Can post scripts if you wish, but it's just a pass-through python script (FFVideoSource) & generic x264 settings. Get errors like this and encode terminates early (usually after a few frames, but a non-deterministic #):
y4m [error]: bad header magic (82848485 <=> àääéé)
y4m [error]: bad header magic (41524682 <=> éFRAM)

Seems to be related to how x264 reads the stuff, if output it to a y4m file or switch x264 to avconv/ffmpeg, it will work :s
(Chikuzen had this problem last night)

[-Vit-]

Same problem with ffmpeg. Fine with core threads = 1. If core threads is anything else then it encodes only a few frames (final frames become offset to the right), no error message shown in ffmpeg. Seems like a threading issue to me.

[JEEB]

Originally Posted by -Vit-

Same problem with ffmpeg. Fine with core threads = 1. If core threads is anything else then it encodes only a few frames (final frames become offset to the right), no error message shown in ffmpeg. Seems like a threading issue to me.

Yeah, in that case it's a threading/output-related issue. At least Myrs is already debugging it.

[wOxxOm]

What is the easiest way of making vapoursynth case-insensitive for filter and parameter names (I mostly write everything in lowercase) ?

[TheFluff]

Originally Posted by wOxxOm

What is the easiest way of making vapoursynth case-insensitive for filter and parameter names (I mostly write everything in lowercase)?

Python function and variable names are always case sensitive; that's a language thing and not something VS gets to decide. Probably the simplest way of making it possible to write everything in lowercase would be write some metaprogramming magic that generates all-lowercase wrappers for all the methods on the VS core object.

[wOxxOm]

1. What are 'format' and 'yuvrange' and is it possible to mimick spline16/36/64resize with Spline(clip:clip;width:int:opt;height:int:opt;format:int:opt;yuvrange:int:opt;) ?
2. Is it possible to specify float numbers for the area to be resized like in avisynth's resize filters which have cropXXXX parameters?
3. What is the syntax of 'Lut' and 'Lut2' functions?
4. Is it possible to implement positional parameters so that instead of Spline(c1=myvideonode,width=1280,height=720) it'd be spline(myvideonode,1280,720) ?
5. It would be nice to have a callback in 'output' function with current frame number and coded frame size so that it could be used in a custom gui for progress reporting