On Mon, Jan 30, 2012 at 02:16:27PM +0200, Martin Storsjö wrote:
> ---
> doc/muxers.texi | 61
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 61 insertions(+), 0 deletions(-)
Push with my below suggestions please.
> --- a/doc/muxers.texi
> +++ b/doc/muxers.texi
> @@ -142,6 +142,67 @@ Note also that the pattern must not necessarily contain
> "%d" or
>
> +@section MOV/MP4/ISMV
> +
> +The mov/mp4/ismv muxer supports fragmentation. Normally, a MOV/MP4
> +file has all the metadata about all packets stored in one location
> +(written at the end of the file, it can be moved to the start for
> +better playback using the @command{qt-faststart} tool). A fragmented
> +file consists of a number of fragments, where packets and metadata
> +about these packets are stored together. Writing a fragmented
> +file has the advantage that the file is decodable even if the
> +writing is interrupted (while a normal MOV/MP4 is undecodable if
> +it isn't properly finished), and it requires less memory when writing
is not
> +very long files (since writing normal MOV/MP4 files stores info about
> +every single packet in memory until the file is closed). The downside
> +is that it normally is less compatible with other applications.
s/normally//
> +@item -movflags empty_moov
> +Write an initial moov atom directly at the start of the file, without
> +describing any samples in it. Generally, a mdat/moov pair is written
an mdat/moov pair
Diego
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
