virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2025-01-24 13:56:33 +02:00
Code Issues Releases Activity

doc: reword the mp3 muxer documentation

Browse Source 
Make it more structured.
This commit is contained in:
Anton Khirnov 2014-04-12 15:20:01 +02:00
parent 99143140de
commit c63418e0a3
1 changed files with 24 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
doc/muxers.texi
View File

@ -347,29 +347,37 @@ avconv -re @var{<normal input/transcoding options>} -movflags isml+frag_keyframe
@section mp3 @section mp3
The MP3 muxer writes a raw MP3 stream with an ID3v2 header at the beginning and The MP3 muxer writes a raw MP3 stream with the following optional features:
optionally an ID3v1 tag at the end. ID3v2.3 and ID3v2.4 are supported, the @itemize @bullet
@code{id3v2_version} option controls which one is used. Setting @item
@code{id3v2_version} to 0 will disable the ID3v2 header completely. The legacy An ID3v2 metadata header at the beginning (enabled by default). Versions 2.3 and
ID3v1 tag is not written by default, but may be enabled with the 2.4 are supported, the @code{id3v2_version} private option controls which one is
@code{write_id3v1} option. used (3 or 4). Setting @code{id3v2_version} to 0 disables the ID3v2 header
completely.
The muxer may also write a Xing frame at the beginning, which contains the The muxer supports writing attached pictures (APIC frames) to the ID3v2 header.
number of frames in the file. It is useful for computing duration of VBR files. The pictures are supplied to the muxer in form of a video stream with a single
The Xing frame is written if the output stream is seekable and if the packet. There can be any number of those streams, each will correspond to a
@code{write_xing} option is set to 1 (the default). single APIC frame. The stream metadata tags @var{title} and @var{comment} map
to APIC @var{description} and @var{picture type} respectively. See
The muxer supports writing ID3v2 attached pictures (APIC frames). The pictures
are supplied to the muxer in form of a video stream with a single packet. There
can be any number of those streams, each will correspond to a single APIC frame.
The stream metadata tags @var{title} and @var{comment} map to APIC
@var{description} and @var{picture type} respectively. See
@url{http://id3.org/id3v2.4.0-frames} for allowed picture types. @url{http://id3.org/id3v2.4.0-frames} for allowed picture types.
Note that the APIC frames must be written at the beginning, so the muxer will Note that the APIC frames must be written at the beginning, so the muxer will
buffer the audio frames until it gets all the pictures. It is therefore advised buffer the audio frames until it gets all the pictures. It is therefore advised
to provide the pictures as soon as possible to avoid excessive buffering. to provide the pictures as soon as possible to avoid excessive buffering.
@item
A Xing/LAME frame right after the ID3v2 header (if present). It is enabled by
default, but will be written only if the output is seekable. The
@code{write_xing} private option can be used to disable it. The frame contains
various information that may be useful to the decoder, like the audio duration.
@item
A legacy ID3v1 tag at the end of the file (disabled by default). It may be
enabled with the @code{write_id3v1} private option, but as its capabilities are
very limited, its usage is not recommended.
@end itemize
Examples: Examples:
Write an mp3 with an ID3v2.3 header and an ID3v1 footer: Write an mp3 with an ID3v2.3 header and an ID3v1 footer: