On Tuesday, January 14, 2014, Stephen Hutchinson wrote:
> ---
> doc/general.texi | 38 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/doc/general.texi b/doc/general.texi
> index 9fa79f5..a056704 100644
> --- a/doc/general.texi
> +++ b/doc/general.texi
> @@ -112,6 +112,44 @@ Go to @url{https://github.com/dekkers/libilbc} and
> follow the instructions for
> installing the library. Then pass @code{--enable-libilbc} to configure to
> enable it.
>
> +@section AviSynth
> +
> +Libav can read AviSynth scripts as input.
> +
> +For Windows, the avisynth_c.h header needed for this support is the
> variant
> +provided by x264's source code in its extras/ directory, or provided with
> a
> +Makefile at @url{https://github.com/qyot27/avisynth_headers} (which is a
> +temporary repository). The reason for this is because the copy provided
> +in classic AviSynth's CVS repository has not been updated to support
> +AviSynth 2.6. AviSynth 2.5 is not supported by Libav.
> +
> +For Linux and OSX, AvxSynth is used to provide this support.
> avxsynth_c.h is
"To provide this feature" or "to support this feature" IMO sound better.
+installed as part of the normal build routine, as illustrated on AvxSynth's
> +wiki: @url{https://github.com/avxsynth/avxsynth/wiki/System-Setup} (the
> +instructions for compiling its prerequisites are outdated, as FFMS 2.18 or
> +higher is now needed; the list of dependencies to be downloaded from the
> +repositories is still the same, though).
> +
> +Pass @code{--enable-avisynth} to configure to enable the support.
> +
> +Supported versions (Windows):
> +AviSynth 2.6 (@url{http://avisynth.nl}, current version = alpha 5)
> +AviSynth+ 0.1 (@url{http://avs-plus.net})
What is avisynth+? A brief description in the windows paragraph before
listing it here would be nice.
> +
> +Supported versions (Linux and OSX):
> +AvxSynth (@url{https://github.com/avxsynth/avxsynth})
> +
> +@float NOTE
> +AviSynth and AvxSynth are loaded dynamically. Distributors can build
> Libav
> +with @code{--enable-avisynth}, and the binaries will work regardless of
> the
> +end user having AviSynth or AvxSynth installed - they'll only need to be
> +installed to use AviSynth scripts (obviously).
> +
> +For 64-bit builds of Libav on Windows, the only version that can be used
> +is AviSynth+, since classic AviSynth doesn't support 64-bit.
I remember seeing 64bit avisynth builds, official for 2.5 and
unofficial for 2.6. Are you sure the 2.6 64bit builds do not work at all?
Vittorio
> +@end float
> +
> +
>
>
> @chapter Supported File Formats and Codecs
> --
> 1.8.3.2
>
> _______________________________________________
> libav-devel mailing list
> [email protected] <javascript:;>
> https://lists.libav.org/mailman/listinfo/libav-devel
>
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
