On Mon, Dec 12, 2011 at 07:17:22PM +0100, Anton Khirnov wrote: > > --- a/libavformat/avformat.h > +++ b/libavformat/avformat.h > @@ -31,6 +31,41 @@ > * > + * Libavformat (lavf) is a library for dealing with various media container > + * formats. Its main two purposes are demuxing - i.e. splitting a media file > + * into component streams, and the reverse process of muxing - writing > supplied > + * data in a specified container format. It also has an @ref lavf_io
data into a > + * "I/O module" which supports a number of protocols for accessing the data > (e.g. > + * file, tcp, http and others). Before using lavf, you need to call TCP, HTTP > + * Unless you are absolutely sure you won't use libavformat's network s/won't/will not/ > + * A supported input format is described by an AVInputFormat struct, > conversely > + * an output format is described by AVOutputFormat. You can iterate over all is described by an AVOutputFormat struct > + * registered input/output formats using the av_iformat_next() / > + * av_oformat_next() functions. The protocols layer is not part of the public protocol layer > + * Main lavf structure used for both muxing and demuxing is AVFormatContext, The main lavf structure > + * which exports all information about the file being read or written. As > with > + * most Libav structures, its size is not part of public ABI, so it cannot be > + * allocated on stack or directly with av_malloc(). To create an on the strack > + * Most importantly an AVFormatContext contains: > + * @li the @ref AVFormatContext.iformat "input" or @ref > AVFormatContext.oformat > + * "output" format. It is either autodetected or set by user for input; > + * always set by user for output. by the user, by the user > + * @li an @ref AVFormatContext.streams "array" of AVStreams, which describe > all which describes > + * @li an @ref AVFormatContext.pb "I/O context". It is either opened by lavf > or > + * set by user for input, always set by user for output (unless you are > dealing > + * with an AVFMT_NOFILE format). by the user, by the user Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
