On Sun, Mar 02, 2014 at 12:06:58AM +0100, Luca Barbato wrote:
> --- a/doc/muxers.texi
> +++ b/doc/muxers.texi
> @@ -419,6 +419,22 @@ avconv -i file.mpg -c copy \
> -y out.ts
> @end example
>
> +@section nut
> +
> +@table @option
> +@item -nut_flags @var{flags}
> +Modify the nut muxing behaviour in specific ways:
"behavior", the documentation is written in American English.
> +@example
> +avconv -i INPUT -f_strict experimental -nut_flags pipe - | processor
> +@end example
> +
> @section null
Reorder alphabetically.
> --- a/doc/nut.texi
> +++ b/doc/nut.texi
> @@ -17,6 +17,27 @@ subtitle and user-defined streams in a simple, yet
> efficient, way.
> +@multitable @columnfractions .4 .4
> +@item BROADCAST @tab Extend the syncpoint to report the sender wallclock
> +@item PIPE @tab Omit completely the syncpoint
completely omit
> +@section PIPE
> +
> +The PIPE variant assumes NUT is used as non-seekable intermediate container,
Isn't it called plain "Nut"?
> +The PIPE variant assumes NUT is used as non-seekable intermediate container,
> +by not using syncpoint removes unneeded overhead and reduces the overall
> +memory usage.
Make this two sentences.
> --- a/libavformat/nutenc.c
> +++ b/libavformat/nutenc.c
> @@ -945,6 +964,22 @@ static int nut_write_trailer(AVFormatContext *s)
>
> +#define OFFSET(x) offsetof(NUTContext, x)
> +#define E AV_OPT_FLAG_ENCODING_PARAM
> +static const AVOption options[] = {
> + { "nut_flags", "NUT muxer flags",
> OFFSET(flags), AV_OPT_TYPE_FLAGS, {.i64 = 0},
> INT_MIN, INT_MAX, E, "nutflags" },
> + { "pipe", "NUT pipe mode, syncpoints and max_distance ignored",
> 0, AV_OPT_TYPE_CONST, {.i64 = NUT_PIPE}, INT_MIN,
> INT_MAX, E, "nutflags" },
> + { "broadcast", "NUT broadcast mode, add a wallclock time reference to
> syncpoints", 0, AV_OPT_TYPE_CONST, {.i64 = NUT_BROADCAST},
> INT_MIN, INT_MAX, E, "nutflags" },
> + { NULL },
spaces inside {}
You could align this table either more or less, but it looks ugly half aligned.
Diego
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
