Vapoursynth

[active1]

Originally Posted by Myrsloik

It is how my threading model works. Avisynth filters are for compatibility reasons limited so one instance may run on one core at one time. Avisynth-mt gets around this by creating multiple instances (one per thread), OR by making very unsafe assumptions.
Newly written and ported filters for the vs api can if done correctly handle multiple frames at once. See the included Lut/Lut2 function.

so there is a chance to make it even better than Avisynth MT in speed wise? (with only one filter)

[TurboPascal7]

Originally Posted by Myrsloik

I think I've fixed the crop argument checks. Can you give an example of the optional arguments maybe not working?

Traceback (most recent call last):
  File "D:/test.py", line 21, in <module>
    source = w.std.CropAbs(clip=source, x=16, y=16)
  File "vapoursynth.pyx", line 434, in vapoursynth.Function.__call__ (cython\vapoursynth.c:7371)
vapoursynth.Error: 'CropAbs: argument width is required'

source = w.std.CropAbs(clip=source, x=16, y=16, width=-16, height=-16)

Works but outputs garbage. Should throw error or work like avisynth's crop (subtracting provided negative width/height values from clip's parameters).

Originally Posted by Myrsloik

6. It's already included in list_functions(), why do you need one more?

I don't really need another list_functions() method. I do want to know Core class constructor parameters, VideoNode.output() method parameters (wanted to test callback, added in r4) etc. Without documentation and any public API I don't see any ways to do it since reflection doesn't work well with cython. I'm asking for this too early, I guess.

[Myrsloik]

Originally Posted by active1

so there is a chance to make it even better than Avisynth MT in speed wise? (with only one filter)

Not without porting filters, no. I'm not going to make another avisynth-mt mess. I intend to win people over in the end by being faster and more stable for most users.

[Myrsloik]

Originally Posted by TurboPascal7

Traceback (most recent call last):
  File "D:/test.py", line 21, in <module>
    source = w.std.CropAbs(clip=source, x=16, y=16)
  File "vapoursynth.pyx", line 434, in vapoursynth.Function.__call__ (cython\vapoursynth.c:7371)
vapoursynth.Error: 'CropAbs: argument width is required'

Of course width is required, this only moves the upper left point.

Originally Posted by TurboPascal7

source = w.std.CropAbs(clip=source, x=16, y=16, width=-16, height=-16)

Works but outputs garbage. Should throw error or work like avisynth's crop (subtracting provided negative width/height values from clip's parameters).

fixed

Originally Posted by TurboPascal7

I don't really need another list_functions() method. I do want to know Core class constructor parameters, VideoNode.output() method parameters (wanted to test callback, added in r4) etc. Without documentation and any public API I don't see any ways to do it since reflection doesn't work well with cython. I'm asking for this too early, I guess.

Core constructor: def __cinit__(self, flatten = True, addcache = True, int threads = 0)

Not much of interest, really. Flatten is whether or not single return value functions get the returned dict flattened to a single value automatically. addcache controls automatic cache insertion.

Output declaration:
def output(self, object fileobj not None, bint y4m = False, int lookahead = 10, object progress_update = None):

Where lookahead is the number of frame requests it has going at once to keep throughput up and progress_update is a functions that could looks like this:
def print_frame(n, total):
print('Frame: %d/%d' % (n, total))

[active1]

Originally Posted by Myrsloik

Not without porting filters, no. I'm not going to make another avisynth-mt mess. I intend to win people over in the end by being faster and more stable for most users.

that's good too, i hope that we will not need to load any filter from avisynth someday.

i have a problem with ColorMatrix:

every filter above work very well, except ColorMatrix
is it not supported yet?

[Myrsloik]

I released R5. Changes in the first post. If this one turns out well I'll start experimenting with other platforms.

[TheProfileth]

r5:
more python output fixes
added accept_lowercase as a setting for the core constructor
python module refinement, now all objects have a string representation with more information
other minor fixes

Does this mean you can do things with all lowercase now?

[Myrsloik]

Originally Posted by TheProfileth

Does this mean you can do things with all lowercase now?

Yes, I added it as an experiment and it's off by default. It may disappear again if I don't like it.

[wOxxOm]

this is great, let it be :-)
also, is there a way yet to create arbitrary clips like in avisynth's ScriptClip? The only way I see now is to loop through all frames and then core.std.splice individual frames after some processing which seems to defy the idea of lazy calculation in a ScriptClip.

[Reel.Deel]

I have managed to finally output y4m but I do not know how to successfully pipe Vapoursynth to X264. Can someone please post a sample of how to achieve this?

@ Myrsloik

So I noticed that the vsvfw.dll is no longer included in r5. Is it still needed?

[Myrsloik]

Originally Posted by Reel.Deel

I have managed to finally output y4m but I do not know how to successfully pipe Vapoursynth to X264. Can someone please post a sample of how to achieve this?

@ Myrsloik

So I noticed that the vsvfw.dll is no longer included in r5. Is it still needed?

It was never used. The vfw part still isn't anywhere near ready.

[TheFluff]

Originally Posted by active1

that's good too, i hope that we will not need to load any filter from avisynth someday.

i have a problem with ColorMatrix:
every filter above work very well, except ColorMatrix
is it not supported yet?

It's not supported yet. Vapoursynth doesn't have equivalents for all of the internal Avisynth functions yet, so filters like ColorMatrix that invoke internal Avisynth filters will break if the invoked function doesn't exist in Vapoursynth.

[Myrsloik]

Originally Posted by TheFluff

It's not supported yet. Vapoursynth doesn't have equivalents for all of the internal Avisynth functions yet, so filters like ColorMatrix that invoke internal Avisynth filters will break if the invoked function doesn't exist in Vapoursynth.

I'd like to add that I may never add any extensive invoke support on the avisynth side. I estimate that the time to port the few useful filters that use invoke and adding good enough support for it in vs is about the same. I know which one I'm going to pick.

[Yoshiyuki Blade]

Ok so I finally got past the "test" phase of the installation instructions LOL. It turns out that I needed the Microsoft Visual C++ 2010 Redistributable Package (instead of the 2008 one) to get it working. The list.functions() is messed up in r5 compared to r3 (I don't have r4 around for some reason). Can't wait to dabble with a new interface and learn new things.

[smok3]

vapour is win only?

[TurboPascal7]

Originally Posted by Yoshiyuki Blade

The list.functions() is messed up in r5 compared to r3 (I don't have r4 around for some reason).

It isn't messed up. It just returns a string instead of printing it. Should be used like print(core.list_functions()).

[Yoshiyuki Blade]

Originally Posted by TurboPascal7

It isn't messed up. It just returns a string instead of printing it. Should be used like print(core.list_functions()).

I see. Yeah, it looks fine when used that way.

[Myrsloik]

Originally Posted by smok3

vapour is win only?

Only until it's kinda stable.

[Reel.Deel]

When I try loading the "official" MVtools (v2.5.11.3) it works fine, but when I try it on Dithers MVTools (v2.6.0.5) it just silently crashes the python command line.

Also, I'm happy to see DGIndexNV work on Vapoursynth.

[Chikuzen]

Originally Posted by Reel.Deel

Also, I'm happy to see DGIndexNV work on Vapoursynth.

However, DGMPEGDec can't be used because it requires avs internal crop function.
I used TS2AVI/MPEG2Dec3k after a long time...