Vapoursynth

[vdcrim]

Originally Posted by Groucho2004

No. The script's parent directory is not the script's directory.

Both are often used interchangeably. It could be just a common mistake though...

Originally Posted by Myrsloik

I still want to keep the original function as well in case someone wants to have a different behavior.

I agree.

[vdcrim]

It would be worth adding a comment somewhere in the header files saying that strings are always encoded/decoded with UTF-8.

[qyot27]

How do we set the correct python install so waf doesn't get confused? The addition of vsscript to the build system altered the detection method, and now it can only find 2.7.4 on my system. Setting it back to the old python detection allows it to pick up on 3.3.1, but it doesn't really solve it because the build process fails when it gets to vsscript.

I tried setting an alias so that 'python' is detected as python3, but waf still picks 2.7.4.

[Myrsloik]

PYTHON=python3 ./waf...

I think that will work. Note that i haven't managed to build it myself on Mac yet. I've also mentioned the python detection issues to zor so he should get around to fixing it soon.

[Adub]

I was able to build rev-513 on my Macbook Pro a little while back, but I haven't tested the latest updates quite yet (should be able to soon). Internet's been a little spoty recently so I haven't had a chance to sync yet.

That, and I also use a virtualenv for my dev purposes with just python3 loaded.

[Myrsloik]

Originally Posted by Adub

I was able to build rev-513 on my Macbook Pro a little while back, but I haven't tested the latest updates quite yet (should be able to soon). Internet's been a little spoty recently so I haven't had a chance to sync yet.

That, and I also use a virtualenv for my dev purposes with just python3 loaded.

I did get it to build on mac now. Simply install qt, python3 and yasm using brew. Then install cython one way or another. Do PYTHON=python3. /waf... For all build commands.

Also, the project has moved to github now. Enjoy the absolutely zero difference in development efficiency...

[Adub]

I did see some issues when running ./waf test, even with PYTHON=python3. This is on Ubuntu 12.04, rev 530.

Here is my output:

blah@u1c6f650423c14ff77388:~/code/vapoursynth$ PYTHON=python3 ./waf test
Waf: Entering directory `/home/blah/code/vapoursynth/build'
Traceback (most recent call last):
File "/home/blah/code/vapoursynth/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Scripting.py", line 97, in waf_entry_point
run_commands()
File "/home/blah/code/vapoursynth/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Scripting.py", line 153, in run_commands
ctx=run_command(cmd_name)
File "/home/blah/code/vapoursynth/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Scripting.py", line 146, in run_command
ctx.execute()
File "/home/blah/code/vapoursynth/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Scripting.py", line 351, in execute
return execute_method(self)
File "/home/blah/code/vapoursynth/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Build.py", line 106, in execute
self.execute_build()
File "/home/blah/code/vapoursynth/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Build.py", line 109, in execute_build
self.recurse([self.run_dir])
File "/home/blah/code/vapoursynth/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Context.py", line 128, in recurse
user_function(self)
File "/home/blah/code/vapoursynth/wscript", line 393, in test
if subprocess.Popen([ctx.env.PYTHON, name]).wait() != 0:
File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child
raise child_exception
AttributeError: 'list' object has no attribute 'rfind'

[Adub]

Ahhh oops!! Never mind, didn't see the new Github repo. The latest checkout from there builds and tests completely successfully.

For those of you wondering, the new source URL is here : https://github.com/vapoursynth/vapoursynth

[buchanan]

Hello Myrsloik

I'm using the 4th r19 test version, and i'm trying to run an x264 encode using the stdout method. My command line is:

"C:\Program Files (x86)\VapourSynth\core\vspipe.exe" "C:\test\test.vpy" - -y4m | "C:\test\x264.exe" --crf 20 --output "C:\test\test.mkv" --demuxer y4m -

The encoding runs fine, but at the end I get this message:



(vspipe.exe stopped working, close the program or debug etc)

The output file seems to be correct though

That didn't happen with the 1st r19 test version, I didn't try with the 2nd and 3rd

[Myrsloik]

Originally Posted by buchanan

Hello Myrsloik

I'm using the 4th r19 test version, and i'm trying to run an x264 encode using the stdout method. My command line is:

"C:\Program Files (x86)\VapourSynth\core\vspipe.exe" "C:\test\test.vpy" - -y4m | "C:\test\x264.exe" --crf 20 --output "C:\test\test.mkv" --demuxer y4m -

The encoding runs fine, but at the end I get this message:

(vspipe.exe stopped working, close the program or debug etc)

The output file seems to be correct though

That didn't happen with the 1st r19 test version, I didn't try with the 2nd and 3rd

It's a known issue. I just haven't gotten around to fixing it yet. Pressing ctrl-c will also make it crash. It shouldn't do anything bad to the output since it crashes after everything is done.

[buchanan]

Originally Posted by Myrsloik

It's a known issue. I just haven't gotten around to fixing it yet. Pressing ctrl-c will also make it crash. It shouldn't do anything bad to the output since it crashes after everything is done.

Ok ! Thank you for your quick answer

[zerowalker]

Is vapoursynth supposed to succeed Avisynth?

From my understanding, it´s not, and just a "by product", but i wanted to make sure.

[Myrsloik]

Originally Posted by zerowalker

Is vapoursynth supposed to succeed Avisynth?

From my understanding, it´s not, and just a "by product", but i wanted to make sure.

It's a by-product in the same way that humans are by-products of sex.

[ryrynz]

Myrsloik, I think you've just gone and made yourself a new signature.

VapourSynth - a by-product of Avisynth in the same way that humans are by-products of sex.

[Adub]

Small bug I noticed, comment here: https://github.com/vapoursynth/vapoursynth/commit/244f23d244d55770a3c32258f25d1f523b1e2bdd#commitcomment-3620372

Essentially, commit 244f23d244d55770a3c32258f25d1f523b1e2bdd used the "FEATURE_AVISYNTH" syntax instead of "VS_FEATURE_AVISYNTH" syntax.

EDIT: Nevermind, it appears this was fixed.

[sl1pkn07]

waf test fail

http://sl1pkn07.no-ip.com/paste/view/0caf88ed

[Adub]

I'd wager you are out of date from the git repo. The tests were fixed 7 days ago: https://github.com/vapoursynth/vapou...0474ad76717848

[sl1pkn07]

ok, then my problem is other


howto make waf test before install the library?

[Adub]

You could use a virtualenv and a local prefix to install the libs to your home directory to act as a staging area.

So, setup a virtualenv for Python3, and then use the --prefix=/home/blah option during the ./waf configure phase to install all objects into your home directory.

[Myrsloik]

Grab what will hopefully be released as R19 here:
VapourSynth R19 rc1

I think I've managed to fix all reported bugs so far as well. If there's anything still happening in this version then report it again because I've missed it. The vsscript api may have some extremely minor changes for R20 if I get more feedback.

Most big changes listed here:

r19:
lut/lut2 now processes all planes by default
ported to work on arm and powerpc (Zor)
fixed 9-16 bit format support in Expr
properly initialize color in addborders to 0
calls to the getFrame() function inside vapoursynth can never deadlock now, the thread handling is also slightly improved
fixed a bug in the cache that would stop it from freeing all its frames when memory is needed, fixes an out of memory error reported by Chikuzen
output is no longer determined by setting the last variable in __main__, instead clip.set_output(int index = 0) is used to set which clip(s) are exported
fixed some memory leaks in the internal filters when they're freed (jackoneill)
now properly initializes blankclips to all 0 when no values are given
added proper const declarations now that cython supports it, cython 0.18 or later required to build the extension now
fixed get_write_ptr() in python to actually return a write pointer
fixed the lut and lut2 filters for > 8 bit formats (ADub)
various minor fixes to vivtc
removed clip.output() since it's a bad design decision, now a command-line program called vspipe can be used to pipe or write raw video output
renamed newMap() to createMap() to match the naming of all other functions
added core.get_plugins() for the core and core.namepace.get_functions() for namespaces, it works similarly to list_functions() but instead returns the information in a dict
removed the unmentioned and unused link option for filter arguments as it is completely pointless and similar functionality may be implemented anyway
there's now a sane external api available for embedding in other applications, see vsscript.h and vsvfw for an example
now a singleton pattern is used for the core in python scripts, use vs.get_core() to get a reference to it
clip.get_frame() now throws an exception when out of bounds frames are requested
fixes a reference leak in the VideoProps python class
now ignores functions with . in their argument string for avisynth compatibility, this makes warpsharp mostly compatible