[FFmpeg-devel] [PATCH] doc/muxers: document mov faststart option.
Clément Bœsch
ubitux at gmail.com
Sun Oct 21 20:17:23 CEST 2012
On Sun, Oct 21, 2012 at 07:16:50PM +0200, Stefano Sabatini wrote:
> On date Sunday 2012-10-21 15:23:01 +0200, Clément Bœsch encoded:
> > ---
> > doc/muxers.texi | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/doc/muxers.texi b/doc/muxers.texi
> > index 83c21db..34eed0f 100644
> > --- a/doc/muxers.texi
> > +++ b/doc/muxers.texi
> > @@ -252,7 +252,8 @@ See also the @ref{framemd5} muxer.
> > 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
> > +better playback by adding @var{faststart} to the @var{movflags}, or
> > +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
> > @@ -310,6 +311,10 @@ more efficient), but with this option set, the muxer writes one moof/mdat
> > pair for each track, making it easier to separate tracks.
> >
> > This option is implicitly set when writing ismv (Smooth Streaming) files.
> > + at item -movflags faststart
> > +Run a second pass moving the moov atom on top of the file. This
> > +operation can take a while, and will not work in various situations such
> > +as fragmented output, thus it is not enabled by default.
> > @end table
>
> LGTM, thanks.
Applied.
--
Clément B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20121021/664ee832/attachment.asc>
More information about the ffmpeg-devel
mailing list