Starter-kit for a noob...

[Sangan]

Hi guys... Well to explain, frankly I am a bit of a noob, from the GUI-fraction, but willing to learn. I managed to install VS (with the help of a friend). I have no experience with AS to build upon (Mac user). I tried to get behind what I am supposed to do to use the basic inspiring script from the How-To on the VS main page, but well, I didn't get anywhere.
If someone of you could explain how to use it, like a small inspire script, where I can see, what paths I should put in where and how to actually run the script... I am sorry, I am just no command line person, though, I think, once I have some basic example as a working scheme, I can get into it.

The reason I would like to try VS is I have a .dv (NTSC - Jap.) with nasty telecine, which the program I usually use for encoding simply can not cope with. I have high hopes, that with VS, the telecine poses less of a problem, also, I could sort out the rainbows.
I would really appreciate a helping hand in this.
VapourSynth is installed in the Cellar, mpv is installed too. The Editor didn't want to install though (last error after 'make' it gave was ../src/common/helpers.h:7:10: fatal error: 'vapoursynth/VapourSynth.h' file not found
#include <vapoursynth/VapourSynth.h> though, when checking the path, it's Cellar/vaporsynth/25/include/vapoursynth/VapourSynth.h
All on Mavericks.

[lansing]

Have you install python first before vapoursynth?

[Sangan]

Phyton is installed :) (the fitting version) also Xcode.

Edit: about the basic basics... (on the danger, this sounds VERY stupid): When calling a program on the command line, f.i. the 'whois' query, I type the whois and the IP I want to know about and go enter. With VS, I would type vapoursynth and do the pipe command afterwards where I name the path and file to be worked on and giving the place and name where the script to be used is (a .py file) and say what and where the output should be put and enter (and make some coffee and wait ^^)?

And don't get annoyed by the level of questions please...

[Are_]

I don't know anything about macs, but the path where you have your .h files does not look correct, but maybe it has to be like that. Try to symlink that directory to a place where the editor build script is looking for includes.

About the other question, you may want to take a look at vapoursynth documentation about vspipe (www.vapoursynth.com/doc/vspipe.html).

Using which on linux it would be something like:
$(which vspipe) -y script.py - | x264 -