On Tue, 30 Apr 2013 16:30:48 +0200, Diego Biurrun <[email protected]> wrote: > On Tue, Apr 31, 2013 at 08:37:32AM +0200, Anton Khirnov wrote: > > --- a/Changelog > > +++ b/Changelog > > @@ -16,6 +16,7 @@ version 9_beta3: > > - multi-channel ALAC encoding up to 7.1 > > - TAK demuxer, parser, and decoder > > - adaptive frame-level multithreading for H.264 > > +- an option in matroska muxer to put the index at the beginning of the file > > Matroska muxer can now put the index at the beginning > > Both sound kinda awkward to my ears :-/ > > > --- a/doc/muxers.texi > > +++ b/doc/muxers.texi > > @@ -367,6 +367,27 @@ For example a 3D WebM clip can be created using the > > following command line: > > + > > +@item reserve_index_space > > +By default, this muxer writes the index for seeking (called cues in > > matroska > > Matroska > > > +terms) at the end of the file, because it cannot know in advance how much > > space > > +to leave for it at the beginning of the file. However for some use cases > > -- e.g. > > s/it/the index/ > > > +If this option is set to a non-zero value, the muxer will reserve a given > > amount > > +of space in the file header and then try to write the cues there when the > > muxing > > What do you mean by "a given amount", that sounds quite arbitrary. It is > interpret this as the muxer making up a value, when I think it should > really be user-supplied.
"a given amount" is the value that the user set for this option, that sounds quite obvious to me. Or got any better suggestions? -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
