mirror of
https://github.com/id-Software/DOOM-3-BFG.git
synced 2025-01-06 01:41:17 +00:00
2011 lines
84 KiB
HTML
2011 lines
84 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<!-- Created on April 4, 2014 by texi2html 1.82 -->
|
|
<!--
|
|
texi2html was written by:
|
|
Lionel Cons <Lionel.Cons@cern.ch> (original author)
|
|
Karl Berry <karl@freefriends.org>
|
|
Olaf Bachmann <obachman@mathematik.uni-kl.de>
|
|
and many others.
|
|
Maintained by: Many creative people.
|
|
Send bugs and suggestions to <texi2html-bug@nongnu.org>
|
|
|
|
-->
|
|
<head>
|
|
<title>FFmpeg documentation : FFmpeg Formats </title>
|
|
|
|
<meta name="description" content="FFmpeg Formats Documentation: ">
|
|
<meta name="keywords" content="FFmpeg documentation : FFmpeg Formats ">
|
|
<meta name="Generator" content="texi2html 1.82">
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<link rel="stylesheet" type="text/css" href="default.css" />
|
|
|
|
<link rel="icon" href="favicon.png" type="image/png" />
|
|
</head>
|
|
<body>
|
|
<div id="container">
|
|
<div id="body">
|
|
|
|
<a name="SEC_Top"></a>
|
|
<h1 class="settitle">FFmpeg Formats Documentation</h1>
|
|
|
|
<a name="SEC_Contents"></a>
|
|
<h1>Table of Contents</h1>
|
|
<div class="contents">
|
|
|
|
<ul class="toc">
|
|
<li><a name="toc-Description" href="#Description">1. Description</a></li>
|
|
<li><a name="toc-Format-Options" href="#Format-Options">2. Format Options</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Format-stream-specifiers-1" href="#Format-stream-specifiers-1">2.1 Format stream specifiers</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-Demuxers" href="#Demuxers">3. Demuxers</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-applehttp" href="#applehttp">3.1 applehttp</a></li>
|
|
<li><a name="toc-asf" href="#asf">3.2 asf</a></li>
|
|
<li><a name="toc-concat-1" href="#concat-1">3.3 concat</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Syntax" href="#Syntax">3.3.1 Syntax</a></li>
|
|
<li><a name="toc-Options-2" href="#Options-2">3.3.2 Options</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-flv" href="#flv">3.4 flv</a></li>
|
|
<li><a name="toc-libgme" href="#libgme">3.5 libgme</a></li>
|
|
<li><a name="toc-libquvi" href="#libquvi">3.6 libquvi</a></li>
|
|
<li><a name="toc-image2-1" href="#image2-1">3.7 image2</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Examples-4" href="#Examples-4">3.7.1 Examples</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-mpegts-1" href="#mpegts-1">3.8 mpegts</a></li>
|
|
<li><a name="toc-rawvideo" href="#rawvideo">3.9 rawvideo</a></li>
|
|
<li><a name="toc-sbg" href="#sbg">3.10 sbg</a></li>
|
|
<li><a name="toc-tedcaptions" href="#tedcaptions">3.11 tedcaptions</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-Muxers" href="#Muxers">4. Muxers</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-aiff-1" href="#aiff-1">4.1 aiff</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Options-6" href="#Options-6">4.1.1 Options</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-crc-1" href="#crc-1">4.2 crc</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Examples-1" href="#Examples-1">4.2.1 Examples</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-framecrc-1" href="#framecrc-1">4.3 framecrc</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Examples-3" href="#Examples-3">4.3.1 Examples</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-framemd5-1" href="#framemd5-1">4.4 framemd5</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Examples-5" href="#Examples-5">4.4.1 Examples</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-gif-1" href="#gif-1">4.5 gif</a></li>
|
|
<li><a name="toc-hls-1" href="#hls-1">4.6 hls</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Options-1" href="#Options-1">4.6.1 Options</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-ico-1" href="#ico-1">4.7 ico</a></li>
|
|
<li><a name="toc-image2-2" href="#image2-2">4.8 image2</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Examples" href="#Examples">4.8.1 Examples</a></li>
|
|
<li><a name="toc-Options-4" href="#Options-4">4.8.2 Options</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-matroska" href="#matroska">4.9 matroska</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Metadata" href="#Metadata">4.9.1 Metadata</a></li>
|
|
<li><a name="toc-Options-7" href="#Options-7">4.9.2 Options</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-md5-1" href="#md5-1">4.10 md5</a></li>
|
|
<li><a name="toc-mov_002c-mp4_002c-ismv" href="#mov_002c-mp4_002c-ismv">4.11 mov, mp4, ismv</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Options-3" href="#Options-3">4.11.1 Options</a></li>
|
|
<li><a name="toc-Example" href="#Example">4.11.2 Example</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-mp3" href="#mp3">4.12 mp3</a></li>
|
|
<li><a name="toc-mpegts" href="#mpegts">4.13 mpegts</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Options" href="#Options">4.13.1 Options</a></li>
|
|
<li><a name="toc-Example-1" href="#Example-1">4.13.2 Example</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-null" href="#null">4.14 null</a></li>
|
|
<li><a name="toc-ogg" href="#ogg">4.15 ogg</a></li>
|
|
<li><a name="toc-segment_002c-stream_005fsegment_002c-ssegment" href="#segment_002c-stream_005fsegment_002c-ssegment">4.16 segment, stream_segment, ssegment</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Options-5" href="#Options-5">4.16.1 Options</a></li>
|
|
<li><a name="toc-Examples-6" href="#Examples-6">4.16.2 Examples</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-tee" href="#tee">4.17 tee</a>
|
|
<ul class="toc">
|
|
<li><a name="toc-Examples-2" href="#Examples-2">4.17.1 Examples</a></li>
|
|
</ul>
|
|
</li>
|
|
</ul></li>
|
|
<li><a name="toc-Metadata-1" href="#Metadata-1">5. Metadata</a></li>
|
|
<li><a name="toc-See-Also" href="#See-Also">6. See Also</a></li>
|
|
<li><a name="toc-Authors" href="#Authors">7. Authors</a></li>
|
|
</ul>
|
|
</div>
|
|
|
|
<a name="Description"></a>
|
|
<h1 class="chapter"><a href="ffmpeg-formats.html#toc-Description">1. Description</a></h1>
|
|
|
|
<p>This document describes the supported formats (muxers and demuxers)
|
|
provided by the libavformat library.
|
|
</p>
|
|
|
|
<a name="Format-Options"></a>
|
|
<h1 class="chapter"><a href="ffmpeg-formats.html#toc-Format-Options">2. Format Options</a></h1>
|
|
|
|
<p>The libavformat library provides some generic global options, which
|
|
can be set on all the muxers and demuxers. In addition each muxer or
|
|
demuxer may support so-called private options, which are specific for
|
|
that component.
|
|
</p>
|
|
<p>Options may be set by specifying -<var>option</var> <var>value</var> in the
|
|
FFmpeg tools, or by setting the value explicitly in the
|
|
<code>AVFormatContext</code> options or using the ‘<tt>libavutil/opt.h</tt>’ API
|
|
for programmatic use.
|
|
</p>
|
|
<p>The list of supported options follows:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>avioflags <var>flags</var> (<em>input/output</em>)</samp>’</dt>
|
|
<dd><p>Possible values:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>direct</samp>’</dt>
|
|
<dd><p>Reduce buffering.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
</dd>
|
|
<dt> ‘<samp>probesize <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Set probing size in bytes, i.e. the size of the data to analyze to get
|
|
stream information. A higher value will allow to detect more
|
|
information in case it is dispersed into the stream, but will increase
|
|
latency. Must be an integer not lesser than 32. It is 5000000 by default.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>packetsize <var>integer</var> (<em>output</em>)</samp>’</dt>
|
|
<dd><p>Set packet size.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>fflags <var>flags</var> (<em>input/output</em>)</samp>’</dt>
|
|
<dd><p>Set format flags.
|
|
</p>
|
|
<p>Possible values:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>ignidx</samp>’</dt>
|
|
<dd><p>Ignore index.
|
|
</p></dd>
|
|
<dt> ‘<samp>genpts</samp>’</dt>
|
|
<dd><p>Generate PTS.
|
|
</p></dd>
|
|
<dt> ‘<samp>nofillin</samp>’</dt>
|
|
<dd><p>Do not fill in missing values that can be exactly calculated.
|
|
</p></dd>
|
|
<dt> ‘<samp>noparse</samp>’</dt>
|
|
<dd><p>Disable AVParsers, this needs <code>+nofillin</code> too.
|
|
</p></dd>
|
|
<dt> ‘<samp>igndts</samp>’</dt>
|
|
<dd><p>Ignore DTS.
|
|
</p></dd>
|
|
<dt> ‘<samp>discardcorrupt</samp>’</dt>
|
|
<dd><p>Discard corrupted frames.
|
|
</p></dd>
|
|
<dt> ‘<samp>sortdts</samp>’</dt>
|
|
<dd><p>Try to interleave output packets by DTS.
|
|
</p></dd>
|
|
<dt> ‘<samp>keepside</samp>’</dt>
|
|
<dd><p>Do not merge side data.
|
|
</p></dd>
|
|
<dt> ‘<samp>latm</samp>’</dt>
|
|
<dd><p>Enable RTP MP4A-LATM payload.
|
|
</p></dd>
|
|
<dt> ‘<samp>nobuffer</samp>’</dt>
|
|
<dd><p>Reduce the latency introduced by optional buffering
|
|
</p></dd>
|
|
</dl>
|
|
|
|
</dd>
|
|
<dt> ‘<samp>seek2any <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Allow seeking to non-keyframes on demuxer level when supported if set to 1.
|
|
Default is 0.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>analyzeduration <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Specify how many microseconds are analyzed to probe the input. A
|
|
higher value will allow to detect more accurate information, but will
|
|
increase latency. It defaults to 5,000,000 microseconds = 5 seconds.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>cryptokey <var>hexadecimal string</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Set decryption key.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>indexmem <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Set max memory used for timestamp index (per stream).
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>rtbufsize <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Set max memory used for buffering real-time frames.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>fdebug <var>flags</var> (<em>input/output</em>)</samp>’</dt>
|
|
<dd><p>Print specific debug info.
|
|
</p>
|
|
<p>Possible values:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>ts</samp>’</dt>
|
|
</dl>
|
|
|
|
</dd>
|
|
<dt> ‘<samp>max_delay <var>integer</var> (<em>input/output</em>)</samp>’</dt>
|
|
<dd><p>Set maximum muxing or demuxing delay in microseconds.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>fpsprobesize <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Set number of frames used to probe fps.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>audio_preload <var>integer</var> (<em>output</em>)</samp>’</dt>
|
|
<dd><p>Set microseconds by which audio packets should be interleaved earlier.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>chunk_duration <var>integer</var> (<em>output</em>)</samp>’</dt>
|
|
<dd><p>Set microseconds for each chunk.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>chunk_size <var>integer</var> (<em>output</em>)</samp>’</dt>
|
|
<dd><p>Set size in bytes for each chunk.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>err_detect, f_err_detect <var>flags</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Set error detection flags. <code>f_err_detect</code> is deprecated and
|
|
should be used only via the <code>ffmpeg</code> tool.
|
|
</p>
|
|
<p>Possible values:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>crccheck</samp>’</dt>
|
|
<dd><p>Verify embedded CRCs.
|
|
</p></dd>
|
|
<dt> ‘<samp>bitstream</samp>’</dt>
|
|
<dd><p>Detect bitstream specification deviations.
|
|
</p></dd>
|
|
<dt> ‘<samp>buffer</samp>’</dt>
|
|
<dd><p>Detect improper bitstream length.
|
|
</p></dd>
|
|
<dt> ‘<samp>explode</samp>’</dt>
|
|
<dd><p>Abort decoding on minor error detection.
|
|
</p></dd>
|
|
<dt> ‘<samp>careful</samp>’</dt>
|
|
<dd><p>Consider things that violate the spec and have not been seen in the
|
|
wild as errors.
|
|
</p></dd>
|
|
<dt> ‘<samp>compliant</samp>’</dt>
|
|
<dd><p>Consider all spec non compliancies as errors.
|
|
</p></dd>
|
|
<dt> ‘<samp>aggressive</samp>’</dt>
|
|
<dd><p>Consider things that a sane encoder should not do as an error.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
</dd>
|
|
<dt> ‘<samp>use_wallclock_as_timestamps <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Use wallclock as timestamps.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>avoid_negative_ts <var>integer</var> (<em>output</em>)</samp>’</dt>
|
|
<dd>
|
|
<p>Possible values:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>make_non_negative</samp>’</dt>
|
|
<dd><p>Shift timestamps to make them non-negative.
|
|
Also note that this affects only leading negative timestamps, and not
|
|
non-monotonic negative timestamps.
|
|
</p></dd>
|
|
<dt> ‘<samp>make_zero</samp>’</dt>
|
|
<dd><p>Shift timestamps so that the first timestamp is 0.
|
|
</p></dd>
|
|
<dt> ‘<samp>auto (default)</samp>’</dt>
|
|
<dd><p>Enables shifting when required by the target format.
|
|
</p></dd>
|
|
<dt> ‘<samp>disabled</samp>’</dt>
|
|
<dd><p>Disables shifting of timestamp.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>When shifting is enabled, all output timestamps are shifted by the
|
|
same amount. Audio, video, and subtitles desynching and relative
|
|
timestamp differences are preserved compared to how they would have
|
|
been without shifting.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>skip_initial_bytes <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Set number of bytes to skip before reading header and frames if set to 1.
|
|
Default is 0.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>correct_ts_overflow <var>integer</var> (<em>input</em>)</samp>’</dt>
|
|
<dd><p>Correct single timestamp overflows if set to 1. Default is 1.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>flush_packets <var>integer</var> (<em>output</em>)</samp>’</dt>
|
|
<dd><p>Flush the underlying I/O stream after each packet. Default 1 enables it, and
|
|
has the effect of reducing the latency; 0 disables it and may slightly
|
|
increase performance in some cases.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>output_ts_offset <var>offset</var> (<em>output</em>)</samp>’</dt>
|
|
<dd><p>Set the output time offset.
|
|
</p>
|
|
<p><var>offset</var> must be a time duration specification,
|
|
see <a href="ffmpeg-utils.html#time-duration-syntax">(ffmpeg-utils)time duration syntax</a>.
|
|
</p>
|
|
<p>The offset is added by the muxer to the output timestamps.
|
|
</p>
|
|
<p>Specifying a positive offset means that the corresponding streams are
|
|
delayed bt the time duration specified in <var>offset</var>. Default value
|
|
is <code>0</code> (meaning that no offset is applied).
|
|
</p></dd>
|
|
</dl>
|
|
|
|
|
|
<p><a name="Format-stream-specifiers"></a>
|
|
</p><a name="Format-stream-specifiers-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-Format-stream-specifiers-1">2.1 Format stream specifiers</a></h2>
|
|
|
|
<p>Format stream specifiers allow selection of one or more streams that
|
|
match specific properties.
|
|
</p>
|
|
<p>Possible forms of stream specifiers are:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp><var>stream_index</var></samp>’</dt>
|
|
<dd><p>Matches the stream with this index.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp><var>stream_type</var>[:<var>stream_index</var>]</samp>’</dt>
|
|
<dd><p><var>stream_type</var> is one of following: ’v’ for video, ’a’ for audio,
|
|
’s’ for subtitle, ’d’ for data, and ’t’ for attachments. If
|
|
<var>stream_index</var> is given, then it matches the stream number
|
|
<var>stream_index</var> of this type. Otherwise, it matches all streams of
|
|
this type.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>p:<var>program_id</var>[:<var>stream_index</var>]</samp>’</dt>
|
|
<dd><p>If <var>stream_index</var> is given, then it matches the stream with number
|
|
<var>stream_index</var> in the program with the id
|
|
<var>program_id</var>. Otherwise, it matches all streams in the program.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>#<var>stream_id</var></samp>’</dt>
|
|
<dd><p>Matches the stream by a format-specific ID.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>The exact semantics of stream specifiers is defined by the
|
|
<code>avformat_match_stream_specifier()</code> function declared in the
|
|
‘<tt>libavformat/avformat.h</tt>’ header.
|
|
</p>
|
|
<a name="Demuxers"></a>
|
|
<h1 class="chapter"><a href="ffmpeg-formats.html#toc-Demuxers">3. Demuxers</a></h1>
|
|
|
|
<p>Demuxers are configured elements in FFmpeg that can read the
|
|
multimedia streams from a particular type of file.
|
|
</p>
|
|
<p>When you configure your FFmpeg build, all the supported demuxers
|
|
are enabled by default. You can list all available ones using the
|
|
configure option <code>--list-demuxers</code>.
|
|
</p>
|
|
<p>You can disable all the demuxers using the configure option
|
|
<code>--disable-demuxers</code>, and selectively enable a single demuxer with
|
|
the option <code>--enable-demuxer=<var>DEMUXER</var></code>, or disable it
|
|
with the option <code>--disable-demuxer=<var>DEMUXER</var></code>.
|
|
</p>
|
|
<p>The option <code>-formats</code> of the ff* tools will display the list of
|
|
enabled demuxers.
|
|
</p>
|
|
<p>The description of some of the currently available demuxers follows.
|
|
</p>
|
|
<a name="applehttp"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-applehttp">3.1 applehttp</a></h2>
|
|
|
|
<p>Apple HTTP Live Streaming demuxer.
|
|
</p>
|
|
<p>This demuxer presents all AVStreams from all variant streams.
|
|
The id field is set to the bitrate variant index number. By setting
|
|
the discard flags on AVStreams (by pressing ’a’ or ’v’ in ffplay),
|
|
the caller can decide which variant streams to actually receive.
|
|
The total bitrate of the variant that the stream belongs to is
|
|
available in a metadata key named "variant_bitrate".
|
|
</p>
|
|
<a name="asf"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-asf">3.2 asf</a></h2>
|
|
|
|
<p>Advanced Systems Format demuxer.
|
|
</p>
|
|
<p>This demuxer is used to demux ASF files and MMS network streams.
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>-no_resync_search <var>bool</var></samp>’</dt>
|
|
<dd><p>Do not try to resynchronize by looking for a certain optional start code.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p><a name="concat"></a>
|
|
</p><a name="concat-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-concat-1">3.3 concat</a></h2>
|
|
|
|
<p>Virtual concatenation script demuxer.
|
|
</p>
|
|
<p>This demuxer reads a list of files and other directives from a text file and
|
|
demuxes them one after the other, as if all their packet had been muxed
|
|
together.
|
|
</p>
|
|
<p>The timestamps in the files are adjusted so that the first file starts at 0
|
|
and each next file starts where the previous one finishes. Note that it is
|
|
done globally and may cause gaps if all streams do not have exactly the same
|
|
length.
|
|
</p>
|
|
<p>All files must have the same streams (same codecs, same time base, etc.).
|
|
</p>
|
|
<p>The duration of each file is used to adjust the timestamps of the next file:
|
|
if the duration is incorrect (because it was computed using the bit-rate or
|
|
because the file is truncated, for example), it can cause artifacts. The
|
|
<code>duration</code> directive can be used to override the duration stored in
|
|
each file.
|
|
</p>
|
|
<a name="Syntax"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Syntax">3.3.1 Syntax</a></h3>
|
|
|
|
<p>The script is a text file in extended-ASCII, with one directive per line.
|
|
Empty lines, leading spaces and lines starting with ’#’ are ignored. The
|
|
following directive is recognized:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp><code>file <var>path</var></code></samp>’</dt>
|
|
<dd><p>Path to a file to read; special characters and spaces must be escaped with
|
|
backslash or single quotes.
|
|
</p>
|
|
<p>All subsequent file-related directives apply to that file.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp><code>ffconcat version 1.0</code></samp>’</dt>
|
|
<dd><p>Identify the script type and version. It also sets the ‘<samp>safe</samp>’ option
|
|
to 1 if it was to its default -1.
|
|
</p>
|
|
<p>To make FFmpeg recognize the format automatically, this directive must
|
|
appears exactly as is (no extra space or byte-order-mark) on the very first
|
|
line of the script.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp><code>duration <var>dur</var></code></samp>’</dt>
|
|
<dd><p>Duration of the file. This information can be specified from the file;
|
|
specifying it here may be more efficient or help if the information from the
|
|
file is not available or accurate.
|
|
</p>
|
|
<p>If the duration is set for all files, then it is possible to seek in the
|
|
whole concatenated video.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp><code>stream</code></samp>’</dt>
|
|
<dd><p>Introduce a stream in the virtual file.
|
|
All subsequent stream-related directives apply to the last introduced
|
|
stream.
|
|
Some streams properties must be set in order to allow identifying the
|
|
matching streams in the subfiles.
|
|
If no streams are defined in the script, the streams from the first file are
|
|
copied.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp><code>exact_stream_id <var>id</var></code></samp>’</dt>
|
|
<dd><p>Set the id of the stream.
|
|
If this directive is given, the string with the corresponding id in the
|
|
subfiles will be used.
|
|
This is especially useful for MPEG-PS (VOB) files, where the order of the
|
|
streams is not reliable.
|
|
</p>
|
|
</dd>
|
|
</dl>
|
|
|
|
<a name="Options-2"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Options-2">3.3.2 Options</a></h3>
|
|
|
|
<p>This demuxer accepts the following option:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>safe</samp>’</dt>
|
|
<dd><p>If set to 1, reject unsafe file paths. A file path is considered safe if it
|
|
does not contain a protocol specification and is relative and all components
|
|
only contain characters from the portable character set (letters, digits,
|
|
period, underscore and hyphen) and have no period at the beginning of a
|
|
component.
|
|
</p>
|
|
<p>If set to 0, any file name is accepted.
|
|
</p>
|
|
<p>The default is -1, it is equivalent to 1 if the format was automatically
|
|
probed and 0 otherwise.
|
|
</p>
|
|
</dd>
|
|
</dl>
|
|
|
|
<a name="flv"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-flv">3.4 flv</a></h2>
|
|
|
|
<p>Adobe Flash Video Format demuxer.
|
|
</p>
|
|
<p>This demuxer is used to demux FLV files and RTMP network streams.
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>-flv_metadata <var>bool</var></samp>’</dt>
|
|
<dd><p>Allocate the streams according to the onMetaData array content.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<a name="libgme"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-libgme">3.5 libgme</a></h2>
|
|
|
|
<p>The Game Music Emu library is a collection of video game music file emulators.
|
|
</p>
|
|
<p>See <a href="http://code.google.com/p/game-music-emu/">http://code.google.com/p/game-music-emu/</a> for more information.
|
|
</p>
|
|
<p>Some files have multiple tracks. The demuxer will pick the first track by
|
|
default. The ‘<samp>track_index</samp>’ option can be used to select a different
|
|
track. Track indexes start at 0. The demuxer exports the number of tracks as
|
|
<var>tracks</var> meta data entry.
|
|
</p>
|
|
<p>For very large files, the ‘<samp>max_size</samp>’ option may have to be adjusted.
|
|
</p>
|
|
<a name="libquvi"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-libquvi">3.6 libquvi</a></h2>
|
|
|
|
<p>Play media from Internet services using the quvi project.
|
|
</p>
|
|
<p>The demuxer accepts a ‘<samp>format</samp>’ option to request a specific quality. It
|
|
is by default set to <var>best</var>.
|
|
</p>
|
|
<p>See <a href="http://quvi.sourceforge.net/">http://quvi.sourceforge.net/</a> for more information.
|
|
</p>
|
|
<p>FFmpeg needs to be built with <code>--enable-libquvi</code> for this demuxer to be
|
|
enabled.
|
|
</p>
|
|
<a name="image2-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-image2-1">3.7 image2</a></h2>
|
|
|
|
<p>Image file demuxer.
|
|
</p>
|
|
<p>This demuxer reads from a list of image files specified by a pattern.
|
|
The syntax and meaning of the pattern is specified by the
|
|
option <var>pattern_type</var>.
|
|
</p>
|
|
<p>The pattern may contain a suffix which is used to automatically
|
|
determine the format of the images contained in the files.
|
|
</p>
|
|
<p>The size, the pixel format, and the format of each image must be the
|
|
same for all the files in the sequence.
|
|
</p>
|
|
<p>This demuxer accepts the following options:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>framerate</samp>’</dt>
|
|
<dd><p>Set the frame rate for the video stream. It defaults to 25.
|
|
</p></dd>
|
|
<dt> ‘<samp>loop</samp>’</dt>
|
|
<dd><p>If set to 1, loop over the input. Default value is 0.
|
|
</p></dd>
|
|
<dt> ‘<samp>pattern_type</samp>’</dt>
|
|
<dd><p>Select the pattern type used to interpret the provided filename.
|
|
</p>
|
|
<p><var>pattern_type</var> accepts one of the following values.
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>sequence</samp>’</dt>
|
|
<dd><p>Select a sequence pattern type, used to specify a sequence of files
|
|
indexed by sequential numbers.
|
|
</p>
|
|
<p>A sequence pattern may contain the string "%d" or "%0<var>N</var>d", which
|
|
specifies the position of the characters representing a sequential
|
|
number in each filename matched by the pattern. If the form
|
|
"%d0<var>N</var>d" is used, the string representing the number in each
|
|
filename is 0-padded and <var>N</var> is the total number of 0-padded
|
|
digits representing the number. The literal character ’%’ can be
|
|
specified in the pattern with the string "%%".
|
|
</p>
|
|
<p>If the sequence pattern contains "%d" or "%0<var>N</var>d", the first filename of
|
|
the file list specified by the pattern must contain a number
|
|
inclusively contained between <var>start_number</var> and
|
|
<var>start_number</var>+<var>start_number_range</var>-1, and all the following
|
|
numbers must be sequential.
|
|
</p>
|
|
<p>For example the pattern "img-%03d.bmp" will match a sequence of
|
|
filenames of the form ‘<tt>img-001.bmp</tt>’, ‘<tt>img-002.bmp</tt>’, ...,
|
|
‘<tt>img-010.bmp</tt>’, etc.; the pattern "i%%m%%g-%d.jpg" will match a
|
|
sequence of filenames of the form ‘<tt>i%m%g-1.jpg</tt>’,
|
|
‘<tt>i%m%g-2.jpg</tt>’, ..., ‘<tt>i%m%g-10.jpg</tt>’, etc.
|
|
</p>
|
|
<p>Note that the pattern must not necessarily contain "%d" or
|
|
"%0<var>N</var>d", for example to convert a single image file
|
|
‘<tt>img.jpeg</tt>’ you can employ the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i img.jpeg img.png
|
|
</pre></td></tr></table>
|
|
|
|
</dd>
|
|
<dt> ‘<samp>glob</samp>’</dt>
|
|
<dd><p>Select a glob wildcard pattern type.
|
|
</p>
|
|
<p>The pattern is interpreted like a <code>glob()</code> pattern. This is only
|
|
selectable if libavformat was compiled with globbing support.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>glob_sequence <em>(deprecated, will be removed)</em></samp>’</dt>
|
|
<dd><p>Select a mixed glob wildcard/sequence pattern.
|
|
</p>
|
|
<p>If your version of libavformat was compiled with globbing support, and
|
|
the provided pattern contains at least one glob meta character among
|
|
<code>%*?[]{}</code> that is preceded by an unescaped "%", the pattern is
|
|
interpreted like a <code>glob()</code> pattern, otherwise it is interpreted
|
|
like a sequence pattern.
|
|
</p>
|
|
<p>All glob special characters <code>%*?[]{}</code> must be prefixed
|
|
with "%". To escape a literal "%" you shall use "%%".
|
|
</p>
|
|
<p>For example the pattern <code>foo-%*.jpeg</code> will match all the
|
|
filenames prefixed by "foo-" and terminating with ".jpeg", and
|
|
<code>foo-%?%?%?.jpeg</code> will match all the filenames prefixed with
|
|
"foo-", followed by a sequence of three characters, and terminating
|
|
with ".jpeg".
|
|
</p>
|
|
<p>This pattern type is deprecated in favor of <var>glob</var> and
|
|
<var>sequence</var>.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>Default value is <var>glob_sequence</var>.
|
|
</p></dd>
|
|
<dt> ‘<samp>pixel_format</samp>’</dt>
|
|
<dd><p>Set the pixel format of the images to read. If not specified the pixel
|
|
format is guessed from the first image file in the sequence.
|
|
</p></dd>
|
|
<dt> ‘<samp>start_number</samp>’</dt>
|
|
<dd><p>Set the index of the file matched by the image file pattern to start
|
|
to read from. Default value is 0.
|
|
</p></dd>
|
|
<dt> ‘<samp>start_number_range</samp>’</dt>
|
|
<dd><p>Set the index interval range to check when looking for the first image
|
|
file in the sequence, starting from <var>start_number</var>. Default value
|
|
is 5.
|
|
</p></dd>
|
|
<dt> ‘<samp>ts_from_file</samp>’</dt>
|
|
<dd><p>If set to 1, will set frame timestamp to modification time of image file. Note
|
|
that monotonity of timestamps is not provided: images go in the same order as
|
|
without this option. Default value is 0.
|
|
</p></dd>
|
|
<dt> ‘<samp>video_size</samp>’</dt>
|
|
<dd><p>Set the video size of the images to read. If not specified the video
|
|
size is guessed from the first image file in the sequence.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<a name="Examples-4"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Examples-4">3.7.1 Examples</a></h3>
|
|
|
|
<ul>
|
|
<li>
|
|
Use <code>ffmpeg</code> for creating a video from the images in the file
|
|
sequence ‘<tt>img-001.jpeg</tt>’, ‘<tt>img-002.jpeg</tt>’, ..., assuming an
|
|
input frame rate of 10 frames per second:
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -framerate 10 -i 'img-%03d.jpeg' out.mkv
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
As above, but start by reading from a file with index 100 in the sequence:
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -framerate 10 -start_number 100 -i 'img-%03d.jpeg' out.mkv
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
Read images matching the "*.png" glob pattern , that is all the files
|
|
terminating with the ".png" suffix:
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -framerate 10 -pattern_type glob -i "*.png" out.mkv
|
|
</pre></td></tr></table>
|
|
</li></ul>
|
|
|
|
<a name="mpegts-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-mpegts-1">3.8 mpegts</a></h2>
|
|
|
|
<p>MPEG-2 transport stream demuxer.
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>fix_teletext_pts</samp>’</dt>
|
|
<dd><p>Overrides teletext packet PTS and DTS values with the timestamps calculated
|
|
from the PCR of the first program which the teletext stream is part of and is
|
|
not discarded. Default value is 1, set this option to 0 if you want your
|
|
teletext packet PTS and DTS values untouched.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<a name="rawvideo"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-rawvideo">3.9 rawvideo</a></h2>
|
|
|
|
<p>Raw video demuxer.
|
|
</p>
|
|
<p>This demuxer allows one to read raw video data. Since there is no header
|
|
specifying the assumed video parameters, the user must specify them
|
|
in order to be able to decode the data correctly.
|
|
</p>
|
|
<p>This demuxer accepts the following options:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>framerate</samp>’</dt>
|
|
<dd><p>Set input video frame rate. Default value is 25.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>pixel_format</samp>’</dt>
|
|
<dd><p>Set the input video pixel format. Default value is <code>yuv420p</code>.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>video_size</samp>’</dt>
|
|
<dd><p>Set the input video size. This value must be specified explicitly.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>For example to read a rawvideo file ‘<tt>input.raw</tt>’ with
|
|
<code>ffplay</code>, assuming a pixel format of <code>rgb24</code>, a video
|
|
size of <code>320x240</code>, and a frame rate of 10 images per second, use
|
|
the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffplay -f rawvideo -pixel_format rgb24 -video_size 320x240 -framerate 10 input.raw
|
|
</pre></td></tr></table>
|
|
|
|
<a name="sbg"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-sbg">3.10 sbg</a></h2>
|
|
|
|
<p>SBaGen script demuxer.
|
|
</p>
|
|
<p>This demuxer reads the script language used by SBaGen
|
|
<a href="http://uazu.net/sbagen/">http://uazu.net/sbagen/</a> to generate binaural beats sessions. A SBG
|
|
script looks like that:
|
|
</p><table><tr><td> </td><td><pre class="example">-SE
|
|
a: 300-2.5/3 440+4.5/0
|
|
b: 300-2.5/0 440+4.5/3
|
|
off: -
|
|
NOW == a
|
|
+0:07:00 == b
|
|
+0:14:00 == a
|
|
+0:21:00 == b
|
|
+0:30:00 off
|
|
</pre></td></tr></table>
|
|
|
|
<p>A SBG script can mix absolute and relative timestamps. If the script uses
|
|
either only absolute timestamps (including the script start time) or only
|
|
relative ones, then its layout is fixed, and the conversion is
|
|
straightforward. On the other hand, if the script mixes both kind of
|
|
timestamps, then the <var>NOW</var> reference for relative timestamps will be
|
|
taken from the current time of day at the time the script is read, and the
|
|
script layout will be frozen according to that reference. That means that if
|
|
the script is directly played, the actual times will match the absolute
|
|
timestamps up to the sound controller’s clock accuracy, but if the user
|
|
somehow pauses the playback or seeks, all times will be shifted accordingly.
|
|
</p>
|
|
<a name="tedcaptions"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-tedcaptions">3.11 tedcaptions</a></h2>
|
|
|
|
<p>JSON captions used for <a href="http://www.ted.com/">TED Talks</a>.
|
|
</p>
|
|
<p>TED does not provide links to the captions, but they can be guessed from the
|
|
page. The file ‘<tt>tools/bookmarklets.html</tt>’ from the FFmpeg source tree
|
|
contains a bookmarklet to expose them.
|
|
</p>
|
|
<p>This demuxer accepts the following option:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>start_time</samp>’</dt>
|
|
<dd><p>Set the start time of the TED talk, in milliseconds. The default is 15000
|
|
(15s). It is used to sync the captions with the downloadable videos, because
|
|
they include a 15s intro.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>Example: convert the captions to a format most players understand:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i http://www.ted.com/talks/subtitles/id/1/lang/en talk1-en.srt
|
|
</pre></td></tr></table>
|
|
|
|
<a name="Muxers"></a>
|
|
<h1 class="chapter"><a href="ffmpeg-formats.html#toc-Muxers">4. Muxers</a></h1>
|
|
|
|
<p>Muxers are configured elements in FFmpeg which allow writing
|
|
multimedia streams to a particular type of file.
|
|
</p>
|
|
<p>When you configure your FFmpeg build, all the supported muxers
|
|
are enabled by default. You can list all available muxers using the
|
|
configure option <code>--list-muxers</code>.
|
|
</p>
|
|
<p>You can disable all the muxers with the configure option
|
|
<code>--disable-muxers</code> and selectively enable / disable single muxers
|
|
with the options <code>--enable-muxer=<var>MUXER</var></code> /
|
|
<code>--disable-muxer=<var>MUXER</var></code>.
|
|
</p>
|
|
<p>The option <code>-formats</code> of the ff* tools will display the list of
|
|
enabled muxers.
|
|
</p>
|
|
<p>A description of some of the currently available muxers follows.
|
|
</p>
|
|
<p><a name="aiff"></a>
|
|
</p><a name="aiff-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-aiff-1">4.1 aiff</a></h2>
|
|
|
|
<p>Audio Interchange File Format muxer.
|
|
</p>
|
|
<a name="Options-6"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Options-6">4.1.1 Options</a></h3>
|
|
|
|
<p>It accepts the following options:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>write_id3v2</samp>’</dt>
|
|
<dd><p>Enable ID3v2 tags writing when set to 1. Default is 0 (disabled).
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>id3v2_version</samp>’</dt>
|
|
<dd><p>Select ID3v2 version to write. Currently only version 3 and 4 (aka.
|
|
ID3v2.3 and ID3v2.4) are supported. The default is version 4.
|
|
</p>
|
|
</dd>
|
|
</dl>
|
|
|
|
<p><a name="crc"></a>
|
|
</p><a name="crc-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-crc-1">4.2 crc</a></h2>
|
|
|
|
<p>CRC (Cyclic Redundancy Check) testing format.
|
|
</p>
|
|
<p>This muxer computes and prints the Adler-32 CRC of all the input audio
|
|
and video frames. By default audio frames are converted to signed
|
|
16-bit raw audio and video frames to raw video before computing the
|
|
CRC.
|
|
</p>
|
|
<p>The output of the muxer consists of a single line of the form:
|
|
CRC=0x<var>CRC</var>, where <var>CRC</var> is a hexadecimal number 0-padded to
|
|
8 digits containing the CRC for all the decoded input frames.
|
|
</p>
|
|
<p>See also the <a href="#framecrc">framecrc</a> muxer.
|
|
</p>
|
|
<a name="Examples-1"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Examples-1">4.2.1 Examples</a></h3>
|
|
|
|
<p>For example to compute the CRC of the input, and store it in the file
|
|
‘<tt>out.crc</tt>’:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f crc out.crc
|
|
</pre></td></tr></table>
|
|
|
|
<p>You can print the CRC to stdout with the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f crc -
|
|
</pre></td></tr></table>
|
|
|
|
<p>You can select the output format of each frame with <code>ffmpeg</code> by
|
|
specifying the audio and video codec and format. For example to
|
|
compute the CRC of the input audio converted to PCM unsigned 8-bit
|
|
and the input video converted to MPEG-2 video, use the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f crc -
|
|
</pre></td></tr></table>
|
|
|
|
<p><a name="framecrc"></a>
|
|
</p><a name="framecrc-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-framecrc-1">4.3 framecrc</a></h2>
|
|
|
|
<p>Per-packet CRC (Cyclic Redundancy Check) testing format.
|
|
</p>
|
|
<p>This muxer computes and prints the Adler-32 CRC for each audio
|
|
and video packet. By default audio frames are converted to signed
|
|
16-bit raw audio and video frames to raw video before computing the
|
|
CRC.
|
|
</p>
|
|
<p>The output of the muxer consists of a line for each audio and video
|
|
packet of the form:
|
|
</p><table><tr><td> </td><td><pre class="example"><var>stream_index</var>, <var>packet_dts</var>, <var>packet_pts</var>, <var>packet_duration</var>, <var>packet_size</var>, 0x<var>CRC</var>
|
|
</pre></td></tr></table>
|
|
|
|
<p><var>CRC</var> is a hexadecimal number 0-padded to 8 digits containing the
|
|
CRC of the packet.
|
|
</p>
|
|
<a name="Examples-3"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Examples-3">4.3.1 Examples</a></h3>
|
|
|
|
<p>For example to compute the CRC of the audio and video frames in
|
|
‘<tt>INPUT</tt>’, converted to raw audio and video packets, and store it
|
|
in the file ‘<tt>out.crc</tt>’:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f framecrc out.crc
|
|
</pre></td></tr></table>
|
|
|
|
<p>To print the information to stdout, use the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f framecrc -
|
|
</pre></td></tr></table>
|
|
|
|
<p>With <code>ffmpeg</code>, you can select the output format to which the
|
|
audio and video frames are encoded before computing the CRC for each
|
|
packet by specifying the audio and video codec. For example, to
|
|
compute the CRC of each decoded input audio frame converted to PCM
|
|
unsigned 8-bit and of each decoded input video frame converted to
|
|
MPEG-2 video, use the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f framecrc -
|
|
</pre></td></tr></table>
|
|
|
|
<p>See also the <a href="#crc">crc</a> muxer.
|
|
</p>
|
|
<p><a name="framemd5"></a>
|
|
</p><a name="framemd5-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-framemd5-1">4.4 framemd5</a></h2>
|
|
|
|
<p>Per-packet MD5 testing format.
|
|
</p>
|
|
<p>This muxer computes and prints the MD5 hash for each audio
|
|
and video packet. By default audio frames are converted to signed
|
|
16-bit raw audio and video frames to raw video before computing the
|
|
hash.
|
|
</p>
|
|
<p>The output of the muxer consists of a line for each audio and video
|
|
packet of the form:
|
|
</p><table><tr><td> </td><td><pre class="example"><var>stream_index</var>, <var>packet_dts</var>, <var>packet_pts</var>, <var>packet_duration</var>, <var>packet_size</var>, <var>MD5</var>
|
|
</pre></td></tr></table>
|
|
|
|
<p><var>MD5</var> is a hexadecimal number representing the computed MD5 hash
|
|
for the packet.
|
|
</p>
|
|
<a name="Examples-5"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Examples-5">4.4.1 Examples</a></h3>
|
|
|
|
<p>For example to compute the MD5 of the audio and video frames in
|
|
‘<tt>INPUT</tt>’, converted to raw audio and video packets, and store it
|
|
in the file ‘<tt>out.md5</tt>’:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f framemd5 out.md5
|
|
</pre></td></tr></table>
|
|
|
|
<p>To print the information to stdout, use the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f framemd5 -
|
|
</pre></td></tr></table>
|
|
|
|
<p>See also the <a href="#md5">md5</a> muxer.
|
|
</p>
|
|
<p><a name="gif"></a>
|
|
</p><a name="gif-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-gif-1">4.5 gif</a></h2>
|
|
|
|
<p>Animated GIF muxer.
|
|
</p>
|
|
<p>It accepts the following options:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>loop</samp>’</dt>
|
|
<dd><p>Set the number of times to loop the output. Use <code>-1</code> for no loop, <code>0</code>
|
|
for looping indefinitely (default).
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>final_delay</samp>’</dt>
|
|
<dd><p>Force the delay (expressed in centiseconds) after the last frame. Each frame
|
|
ends with a delay until the next frame. The default is <code>-1</code>, which is a
|
|
special value to tell the muxer to re-use the previous delay. In case of a
|
|
loop, you might want to customize this value to mark a pause for instance.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>For example, to encode a gif looping 10 times, with a 5 seconds delay between
|
|
the loops:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -loop 10 -final_delay 500 out.gif
|
|
</pre></td></tr></table>
|
|
|
|
<p>Note 1: if you wish to extract the frames in separate GIF files, you need to
|
|
force the <a href="#image2">image2</a> muxer:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -c:v gif -f image2 "out%d.gif"
|
|
</pre></td></tr></table>
|
|
|
|
<p>Note 2: the GIF format has a very small time base: the delay between two frames
|
|
can not be smaller than one centi second.
|
|
</p>
|
|
<p><a name="hls"></a>
|
|
</p><a name="hls-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-hls-1">4.6 hls</a></h2>
|
|
|
|
<p>Apple HTTP Live Streaming muxer that segments MPEG-TS according to
|
|
the HTTP Live Streaming (HLS) specification.
|
|
</p>
|
|
<p>It creates a playlist file and numbered segment files. The output
|
|
filename specifies the playlist filename; the segment filenames
|
|
receive the same basename as the playlist, a sequential number and
|
|
a .ts extension.
|
|
</p>
|
|
<p>For example, to convert an input file with <code>ffmpeg</code>:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i in.nut out.m3u8
|
|
</pre></td></tr></table>
|
|
|
|
<p>See also the <a href="#segment">segment</a> muxer, which provides a more generic and
|
|
flexible implementation of a segmenter, and can be used to perform HLS
|
|
segmentation.
|
|
</p>
|
|
<a name="Options-1"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Options-1">4.6.1 Options</a></h3>
|
|
|
|
<p>This muxer supports the following options:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>hls_time <var>seconds</var></samp>’</dt>
|
|
<dd><p>Set the segment length in seconds. Default value is 2.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>hls_list_size <var>size</var></samp>’</dt>
|
|
<dd><p>Set the maximum number of playlist entries. If set to 0 the list file
|
|
will contain all the segments. Default value is 5.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>hls_wrap <var>wrap</var></samp>’</dt>
|
|
<dd><p>Set the number after which the segment filename number (the number
|
|
specified in each segment file) wraps. If set to 0 the number will be
|
|
never wrapped. Default value is 0.
|
|
</p>
|
|
<p>This option is useful to avoid to fill the disk with many segment
|
|
files, and limits the maximum number of segment files written to disk
|
|
to <var>wrap</var>.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>start_number <var>number</var></samp>’</dt>
|
|
<dd><p>Start the playlist sequence number from <var>number</var>. Default value is
|
|
0.
|
|
</p>
|
|
<p>Note that the playlist sequence number must be unique for each segment
|
|
and it is not to be confused with the segment filename sequence number
|
|
which can be cyclic, for example if the ‘<samp>wrap</samp>’ option is
|
|
specified.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p><a name="ico"></a>
|
|
</p><a name="ico-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-ico-1">4.7 ico</a></h2>
|
|
|
|
<p>ICO file muxer.
|
|
</p>
|
|
<p>Microsoft’s icon file format (ICO) has some strict limitations that should be noted:
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
Size cannot exceed 256 pixels in any dimension
|
|
|
|
</li><li>
|
|
Only BMP and PNG images can be stored
|
|
|
|
</li><li>
|
|
If a BMP image is used, it must be one of the following pixel formats:
|
|
<table><tr><td> </td><td><pre class="example">BMP Bit Depth FFmpeg Pixel Format
|
|
1bit pal8
|
|
4bit pal8
|
|
8bit pal8
|
|
16bit rgb555le
|
|
24bit bgr24
|
|
32bit bgra
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
If a BMP image is used, it must use the BITMAPINFOHEADER DIB header
|
|
|
|
</li><li>
|
|
If a PNG image is used, it must use the rgba pixel format
|
|
</li></ul>
|
|
|
|
<p><a name="image2"></a>
|
|
</p><a name="image2-2"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-image2-2">4.8 image2</a></h2>
|
|
|
|
<p>Image file muxer.
|
|
</p>
|
|
<p>The image file muxer writes video frames to image files.
|
|
</p>
|
|
<p>The output filenames are specified by a pattern, which can be used to
|
|
produce sequentially numbered series of files.
|
|
The pattern may contain the string "%d" or "%0<var>N</var>d", this string
|
|
specifies the position of the characters representing a numbering in
|
|
the filenames. If the form "%0<var>N</var>d" is used, the string
|
|
representing the number in each filename is 0-padded to <var>N</var>
|
|
digits. The literal character ’%’ can be specified in the pattern with
|
|
the string "%%".
|
|
</p>
|
|
<p>If the pattern contains "%d" or "%0<var>N</var>d", the first filename of
|
|
the file list specified will contain the number 1, all the following
|
|
numbers will be sequential.
|
|
</p>
|
|
<p>The pattern may contain a suffix which is used to automatically
|
|
determine the format of the image files to write.
|
|
</p>
|
|
<p>For example the pattern "img-%03d.bmp" will specify a sequence of
|
|
filenames of the form ‘<tt>img-001.bmp</tt>’, ‘<tt>img-002.bmp</tt>’, ...,
|
|
‘<tt>img-010.bmp</tt>’, etc.
|
|
The pattern "img%%-%d.jpg" will specify a sequence of filenames of the
|
|
form ‘<tt>img%-1.jpg</tt>’, ‘<tt>img%-2.jpg</tt>’, ..., ‘<tt>img%-10.jpg</tt>’,
|
|
etc.
|
|
</p>
|
|
<a name="Examples"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Examples">4.8.1 Examples</a></h3>
|
|
|
|
<p>The following example shows how to use <code>ffmpeg</code> for creating a
|
|
sequence of files ‘<tt>img-001.jpeg</tt>’, ‘<tt>img-002.jpeg</tt>’, ...,
|
|
taking one image every second from the input video:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i in.avi -vsync 1 -r 1 -f image2 'img-%03d.jpeg'
|
|
</pre></td></tr></table>
|
|
|
|
<p>Note that with <code>ffmpeg</code>, if the format is not specified with the
|
|
<code>-f</code> option and the output filename specifies an image file
|
|
format, the image2 muxer is automatically selected, so the previous
|
|
command can be written as:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i in.avi -vsync 1 -r 1 'img-%03d.jpeg'
|
|
</pre></td></tr></table>
|
|
|
|
<p>Note also that the pattern must not necessarily contain "%d" or
|
|
"%0<var>N</var>d", for example to create a single image file
|
|
‘<tt>img.jpeg</tt>’ from the input video you can employ the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i in.avi -f image2 -frames:v 1 img.jpeg
|
|
</pre></td></tr></table>
|
|
|
|
<p>The ‘<samp>strftime</samp>’ option allows you to expand the filename with
|
|
date and time information. Check the documentation of
|
|
the <code>strftime()</code> function for the syntax.
|
|
</p>
|
|
<p>For example to generate image files from the <code>strftime()</code>
|
|
"%Y-%m-%d_%H-%M-%S" pattern, the following <code>ffmpeg</code> command
|
|
can be used:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -f v4l2 -r 1 -i /dev/video0 -f image2 -strftime 1 "%Y-%m-%d_%H-%M-%S.jpg"
|
|
</pre></td></tr></table>
|
|
|
|
<a name="Options-4"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Options-4">4.8.2 Options</a></h3>
|
|
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>start_number</samp>’</dt>
|
|
<dd><p>Start the sequence from the specified number. Default value is 1. Must
|
|
be a non-negative number.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>update</samp>’</dt>
|
|
<dd><p>If set to 1, the filename will always be interpreted as just a
|
|
filename, not a pattern, and the corresponding file will be continuously
|
|
overwritten with new images. Default value is 0.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>strftime</samp>’</dt>
|
|
<dd><p>If set to 1, expand the filename with date and time information from
|
|
<code>strftime()</code>. Default value is 0.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>The image muxer supports the .Y.U.V image file format. This format is
|
|
special in that that each image frame consists of three files, for
|
|
each of the YUV420P components. To read or write this image file format,
|
|
specify the name of the ’.Y’ file. The muxer will automatically open the
|
|
’.U’ and ’.V’ files as required.
|
|
</p>
|
|
<a name="matroska"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-matroska">4.9 matroska</a></h2>
|
|
|
|
<p>Matroska container muxer.
|
|
</p>
|
|
<p>This muxer implements the matroska and webm container specs.
|
|
</p>
|
|
<a name="Metadata"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Metadata">4.9.1 Metadata</a></h3>
|
|
|
|
<p>The recognized metadata settings in this muxer are:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>title</samp>’</dt>
|
|
<dd><p>Set title name provided to a single track.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>language</samp>’</dt>
|
|
<dd><p>Specify the language of the track in the Matroska languages form.
|
|
</p>
|
|
<p>The language can be either the 3 letters bibliographic ISO-639-2 (ISO
|
|
639-2/B) form (like "fre" for French), or a language code mixed with a
|
|
country code for specialities in languages (like "fre-ca" for Canadian
|
|
French).
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>stereo_mode</samp>’</dt>
|
|
<dd><p>Set stereo 3D video layout of two views in a single video track.
|
|
</p>
|
|
<p>The following values are recognized:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>mono</samp>’</dt>
|
|
<dd><p>video is not stereo
|
|
</p></dd>
|
|
<dt> ‘<samp>left_right</samp>’</dt>
|
|
<dd><p>Both views are arranged side by side, Left-eye view is on the left
|
|
</p></dd>
|
|
<dt> ‘<samp>bottom_top</samp>’</dt>
|
|
<dd><p>Both views are arranged in top-bottom orientation, Left-eye view is at bottom
|
|
</p></dd>
|
|
<dt> ‘<samp>top_bottom</samp>’</dt>
|
|
<dd><p>Both views are arranged in top-bottom orientation, Left-eye view is on top
|
|
</p></dd>
|
|
<dt> ‘<samp>checkerboard_rl</samp>’</dt>
|
|
<dd><p>Each view is arranged in a checkerboard interleaved pattern, Left-eye view being first
|
|
</p></dd>
|
|
<dt> ‘<samp>checkerboard_lr</samp>’</dt>
|
|
<dd><p>Each view is arranged in a checkerboard interleaved pattern, Right-eye view being first
|
|
</p></dd>
|
|
<dt> ‘<samp>row_interleaved_rl</samp>’</dt>
|
|
<dd><p>Each view is constituted by a row based interleaving, Right-eye view is first row
|
|
</p></dd>
|
|
<dt> ‘<samp>row_interleaved_lr</samp>’</dt>
|
|
<dd><p>Each view is constituted by a row based interleaving, Left-eye view is first row
|
|
</p></dd>
|
|
<dt> ‘<samp>col_interleaved_rl</samp>’</dt>
|
|
<dd><p>Both views are arranged in a column based interleaving manner, Right-eye view is first column
|
|
</p></dd>
|
|
<dt> ‘<samp>col_interleaved_lr</samp>’</dt>
|
|
<dd><p>Both views are arranged in a column based interleaving manner, Left-eye view is first column
|
|
</p></dd>
|
|
<dt> ‘<samp>anaglyph_cyan_red</samp>’</dt>
|
|
<dd><p>All frames are in anaglyph format viewable through red-cyan filters
|
|
</p></dd>
|
|
<dt> ‘<samp>right_left</samp>’</dt>
|
|
<dd><p>Both views are arranged side by side, Right-eye view is on the left
|
|
</p></dd>
|
|
<dt> ‘<samp>anaglyph_green_magenta</samp>’</dt>
|
|
<dd><p>All frames are in anaglyph format viewable through green-magenta filters
|
|
</p></dd>
|
|
<dt> ‘<samp>block_lr</samp>’</dt>
|
|
<dd><p>Both eyes laced in one Block, Left-eye view is first
|
|
</p></dd>
|
|
<dt> ‘<samp>block_rl</samp>’</dt>
|
|
<dd><p>Both eyes laced in one Block, Right-eye view is first
|
|
</p></dd>
|
|
</dl>
|
|
</dd>
|
|
</dl>
|
|
|
|
<p>For example a 3D WebM clip can be created using the following command line:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i sample_left_right_clip.mpg -an -c:v libvpx -metadata stereo_mode=left_right -y stereo_clip.webm
|
|
</pre></td></tr></table>
|
|
|
|
<a name="Options-7"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Options-7">4.9.2 Options</a></h3>
|
|
|
|
<p>This muxer supports the following options:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>reserve_index_space</samp>’</dt>
|
|
<dd><p>By default, this muxer writes the index for seeking (called cues in Matroska
|
|
terms) at the end of the file, because it cannot know in advance how much space
|
|
to leave for the index at the beginning of the file. However for some use cases
|
|
– e.g. streaming where seeking is possible but slow – it is useful to put the
|
|
index at the beginning of the file.
|
|
</p>
|
|
<p>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
|
|
finishes. If the available space does not suffice, muxing will fail. A safe size
|
|
for most use cases should be about 50kB per hour of video.
|
|
</p>
|
|
<p>Note that cues are only written if the output is seekable and this option will
|
|
have no effect if it is not.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p><a name="md5"></a>
|
|
</p><a name="md5-1"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-md5-1">4.10 md5</a></h2>
|
|
|
|
<p>MD5 testing format.
|
|
</p>
|
|
<p>This muxer computes and prints the MD5 hash of all the input audio
|
|
and video frames. By default audio frames are converted to signed
|
|
16-bit raw audio and video frames to raw video before computing the
|
|
hash.
|
|
</p>
|
|
<p>The output of the muxer consists of a single line of the form:
|
|
MD5=<var>MD5</var>, where <var>MD5</var> is a hexadecimal number representing
|
|
the computed MD5 hash.
|
|
</p>
|
|
<p>For example to compute the MD5 hash of the input converted to raw
|
|
audio and video, and store it in the file ‘<tt>out.md5</tt>’:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f md5 out.md5
|
|
</pre></td></tr></table>
|
|
|
|
<p>You can print the MD5 to stdout with the command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f md5 -
|
|
</pre></td></tr></table>
|
|
|
|
<p>See also the <a href="#framemd5">framemd5</a> muxer.
|
|
</p>
|
|
<a name="mov_002c-mp4_002c-ismv"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-mov_002c-mp4_002c-ismv">4.11 mov, mp4, ismv</a></h2>
|
|
|
|
<p>MOV/MP4/ISMV (Smooth Streaming) muxer.
|
|
</p>
|
|
<p>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 by adding <var>faststart</var> to the <var>movflags</var>, or
|
|
using the <code>qt-faststart</code> 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 is not properly finished), and it requires less memory when writing
|
|
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 is less compatible with other applications.
|
|
</p>
|
|
<a name="Options-3"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Options-3">4.11.1 Options</a></h3>
|
|
|
|
<p>Fragmentation is enabled by setting one of the AVOptions that define
|
|
how to cut the file into fragments:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>-moov_size <var>bytes</var></samp>’</dt>
|
|
<dd><p>Reserves space for the moov atom at the beginning of the file instead of placing the
|
|
moov atom at the end. If the space reserved is insufficient, muxing will fail.
|
|
</p></dd>
|
|
<dt> ‘<samp>-movflags frag_keyframe</samp>’</dt>
|
|
<dd><p>Start a new fragment at each video keyframe.
|
|
</p></dd>
|
|
<dt> ‘<samp>-frag_duration <var>duration</var></samp>’</dt>
|
|
<dd><p>Create fragments that are <var>duration</var> microseconds long.
|
|
</p></dd>
|
|
<dt> ‘<samp>-frag_size <var>size</var></samp>’</dt>
|
|
<dd><p>Create fragments that contain up to <var>size</var> bytes of payload data.
|
|
</p></dd>
|
|
<dt> ‘<samp>-movflags frag_custom</samp>’</dt>
|
|
<dd><p>Allow the caller to manually choose when to cut fragments, by
|
|
calling <code>av_write_frame(ctx, NULL)</code> to write a fragment with
|
|
the packets written so far. (This is only useful with other
|
|
applications integrating libavformat, not from <code>ffmpeg</code>.)
|
|
</p></dd>
|
|
<dt> ‘<samp>-min_frag_duration <var>duration</var></samp>’</dt>
|
|
<dd><p>Don’t create fragments that are shorter than <var>duration</var> microseconds long.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>If more than one condition is specified, fragments are cut when
|
|
one of the specified conditions is fulfilled. The exception to this is
|
|
<code>-min_frag_duration</code>, which has to be fulfilled for any of the other
|
|
conditions to apply.
|
|
</p>
|
|
<p>Additionally, the way the output file is written can be adjusted
|
|
through a few other options:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>-movflags empty_moov</samp>’</dt>
|
|
<dd><p>Write an initial moov atom directly at the start of the file, without
|
|
describing any samples in it. Generally, an mdat/moov pair is written
|
|
at the start of the file, as a normal MOV/MP4 file, containing only
|
|
a short portion of the file. With this option set, there is no initial
|
|
mdat atom, and the moov atom only describes the tracks but has
|
|
a zero duration.
|
|
</p>
|
|
<p>Files written with this option set do not work in QuickTime.
|
|
This option is implicitly set when writing ismv (Smooth Streaming) files.
|
|
</p></dd>
|
|
<dt> ‘<samp>-movflags separate_moof</samp>’</dt>
|
|
<dd><p>Write a separate moof (movie fragment) atom for each track. Normally,
|
|
packets for all tracks are written in a moof atom (which is slightly
|
|
more efficient), but with this option set, the muxer writes one moof/mdat
|
|
pair for each track, making it easier to separate tracks.
|
|
</p>
|
|
<p>This option is implicitly set when writing ismv (Smooth Streaming) files.
|
|
</p></dd>
|
|
<dt> ‘<samp>-movflags faststart</samp>’</dt>
|
|
<dd><p>Run a second pass moving the index (moov atom) to the beginning 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.
|
|
</p></dd>
|
|
<dt> ‘<samp>-movflags rtphint</samp>’</dt>
|
|
<dd><p>Add RTP hinting tracks to the output file.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<a name="Example"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Example">4.11.2 Example</a></h3>
|
|
|
|
<p>Smooth Streaming content can be pushed in real time to a publishing
|
|
point on IIS with this muxer. Example:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -re <var><normal input/transcoding options></var> -movflags isml+frag_keyframe -f ismv http://server/publishingpoint.isml/Streams(Encoder1)
|
|
</pre></td></tr></table>
|
|
|
|
<a name="mp3"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-mp3">4.12 mp3</a></h2>
|
|
|
|
<p>The MP3 muxer writes a raw MP3 stream with an ID3v2 header at the beginning and
|
|
optionally an ID3v1 tag at the end. ID3v2.3 and ID3v2.4 are supported, the
|
|
<code>id3v2_version</code> option controls which one is used. Setting
|
|
<code>id3v2_version</code> to 0 will disable the ID3v2 header completely. The legacy
|
|
ID3v1 tag is not written by default, but may be enabled with the
|
|
<code>write_id3v1</code> option.
|
|
</p>
|
|
<p>The muxer may also write a Xing frame at the beginning, which contains the
|
|
number of frames in the file. It is useful for computing duration of VBR files.
|
|
The Xing frame is written if the output stream is seekable and if the
|
|
<code>write_xing</code> option is set to 1 (the default).
|
|
</p>
|
|
<p>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</var> and <var>comment</var> map to APIC
|
|
<var>description</var> and <var>picture type</var> respectively. See
|
|
<a href="http://id3.org/id3v2.4.0-frames">http://id3.org/id3v2.4.0-frames</a> for allowed picture types.
|
|
</p>
|
|
<p>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
|
|
to provide the pictures as soon as possible to avoid excessive buffering.
|
|
</p>
|
|
<p>Examples:
|
|
</p>
|
|
<p>Write an mp3 with an ID3v2.3 header and an ID3v1 footer:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -id3v2_version 3 -write_id3v1 1 out.mp3
|
|
</pre></td></tr></table>
|
|
|
|
<p>To attach a picture to an mp3 file select both the audio and the picture stream
|
|
with <code>map</code>:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i input.mp3 -i cover.png -c copy -map 0 -map 1
|
|
-metadata:s:v title="Album cover" -metadata:s:v comment="Cover (Front)" out.mp3
|
|
</pre></td></tr></table>
|
|
|
|
<p>Write a "clean" MP3 without any extra features:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i input.wav -write_xing 0 -id3v2_version 0 out.mp3
|
|
</pre></td></tr></table>
|
|
|
|
<a name="mpegts"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-mpegts">4.13 mpegts</a></h2>
|
|
|
|
<p>MPEG transport stream muxer.
|
|
</p>
|
|
<p>This muxer implements ISO 13818-1 and part of ETSI EN 300 468.
|
|
</p>
|
|
<p>The recognized metadata settings in mpegts muxer are <code>service_provider</code>
|
|
and <code>service_name</code>. If they are not set the default for
|
|
<code>service_provider</code> is "FFmpeg" and the default for
|
|
<code>service_name</code> is "Service01".
|
|
</p>
|
|
<a name="Options"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Options">4.13.1 Options</a></h3>
|
|
|
|
<p>The muxer options are:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>-mpegts_original_network_id <var>number</var></samp>’</dt>
|
|
<dd><p>Set the original_network_id (default 0x0001). This is unique identifier
|
|
of a network in DVB. Its main use is in the unique identification of a
|
|
service through the path Original_Network_ID, Transport_Stream_ID.
|
|
</p></dd>
|
|
<dt> ‘<samp>-mpegts_transport_stream_id <var>number</var></samp>’</dt>
|
|
<dd><p>Set the transport_stream_id (default 0x0001). This identifies a
|
|
transponder in DVB.
|
|
</p></dd>
|
|
<dt> ‘<samp>-mpegts_service_id <var>number</var></samp>’</dt>
|
|
<dd><p>Set the service_id (default 0x0001) also known as program in DVB.
|
|
</p></dd>
|
|
<dt> ‘<samp>-mpegts_pmt_start_pid <var>number</var></samp>’</dt>
|
|
<dd><p>Set the first PID for PMT (default 0x1000, max 0x1f00).
|
|
</p></dd>
|
|
<dt> ‘<samp>-mpegts_start_pid <var>number</var></samp>’</dt>
|
|
<dd><p>Set the first PID for data packets (default 0x0100, max 0x0f00).
|
|
</p></dd>
|
|
<dt> ‘<samp>-mpegts_m2ts_mode <var>number</var></samp>’</dt>
|
|
<dd><p>Enable m2ts mode if set to 1. Default value is -1 which disables m2ts mode.
|
|
</p></dd>
|
|
<dt> ‘<samp>-muxrate <var>number</var></samp>’</dt>
|
|
<dd><p>Set muxrate.
|
|
</p></dd>
|
|
<dt> ‘<samp>-pes_payload_size <var>number</var></samp>’</dt>
|
|
<dd><p>Set minimum PES packet payload in bytes.
|
|
</p></dd>
|
|
<dt> ‘<samp>-mpegts_flags <var>flags</var></samp>’</dt>
|
|
<dd><p>Set flags (see below).
|
|
</p></dd>
|
|
<dt> ‘<samp>-mpegts_copyts <var>number</var></samp>’</dt>
|
|
<dd><p>Preserve original timestamps, if value is set to 1. Default value is -1, which
|
|
results in shifting timestamps so that they start from 0.
|
|
</p></dd>
|
|
<dt> ‘<samp>-tables_version <var>number</var></samp>’</dt>
|
|
<dd><p>Set PAT, PMT and SDT version (default 0, valid values are from 0 to 31, inclusively).
|
|
This option allows updating stream structure so that standard consumer may
|
|
detect the change. To do so, reopen output AVFormatContext (in case of API
|
|
usage) or restart ffmpeg instance, cyclically changing tables_version value:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
|
|
ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
|
|
...
|
|
ffmpeg -i source3.ts -codec copy -f mpegts -tables_version 31 udp://1.1.1.1:1111
|
|
ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
|
|
ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
|
|
...
|
|
</pre></td></tr></table>
|
|
</dd>
|
|
</dl>
|
|
|
|
<p>Option mpegts_flags may take a set of such flags:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>resend_headers</samp>’</dt>
|
|
<dd><p>Reemit PAT/PMT before writing the next packet.
|
|
</p></dd>
|
|
<dt> ‘<samp>latm</samp>’</dt>
|
|
<dd><p>Use LATM packetization for AAC.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<a name="Example-1"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Example-1">4.13.2 Example</a></h3>
|
|
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i file.mpg -c copy \
|
|
-mpegts_original_network_id 0x1122 \
|
|
-mpegts_transport_stream_id 0x3344 \
|
|
-mpegts_service_id 0x5566 \
|
|
-mpegts_pmt_start_pid 0x1500 \
|
|
-mpegts_start_pid 0x150 \
|
|
-metadata service_provider="Some provider" \
|
|
-metadata service_name="Some Channel" \
|
|
-y out.ts
|
|
</pre></td></tr></table>
|
|
|
|
<a name="null"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-null">4.14 null</a></h2>
|
|
|
|
<p>Null muxer.
|
|
</p>
|
|
<p>This muxer does not generate any output file, it is mainly useful for
|
|
testing or benchmarking purposes.
|
|
</p>
|
|
<p>For example to benchmark decoding with <code>ffmpeg</code> you can use the
|
|
command:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -benchmark -i INPUT -f null out.null
|
|
</pre></td></tr></table>
|
|
|
|
<p>Note that the above command does not read or write the ‘<tt>out.null</tt>’
|
|
file, but specifying the output file is required by the <code>ffmpeg</code>
|
|
syntax.
|
|
</p>
|
|
<p>Alternatively you can write the command as:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -benchmark -i INPUT -f null -
|
|
</pre></td></tr></table>
|
|
|
|
<a name="ogg"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-ogg">4.15 ogg</a></h2>
|
|
|
|
<p>Ogg container muxer.
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>-page_duration <var>duration</var></samp>’</dt>
|
|
<dd><p>Preferred page duration, in microseconds. The muxer will attempt to create
|
|
pages that are approximately <var>duration</var> microseconds long. This allows the
|
|
user to compromise between seek granularity and container overhead. The default
|
|
is 1 second. A value of 0 will fill all segments, making pages as large as
|
|
possible. A value of 1 will effectively use 1 packet-per-page in most
|
|
situations, giving a small seek granularity at the cost of additional container
|
|
overhead.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p><a name="segment"></a>
|
|
</p><a name="segment_002c-stream_005fsegment_002c-ssegment"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-segment_002c-stream_005fsegment_002c-ssegment">4.16 segment, stream_segment, ssegment</a></h2>
|
|
|
|
<p>Basic stream segmenter.
|
|
</p>
|
|
<p>This muxer outputs streams to a number of separate files of nearly
|
|
fixed duration. Output filename pattern can be set in a fashion similar to
|
|
<a href="#image2">image2</a>.
|
|
</p>
|
|
<p><code>stream_segment</code> is a variant of the muxer used to write to
|
|
streaming output formats, i.e. which do not require global headers,
|
|
and is recommended for outputting e.g. to MPEG transport stream segments.
|
|
<code>ssegment</code> is a shorter alias for <code>stream_segment</code>.
|
|
</p>
|
|
<p>Every segment starts with a keyframe of the selected reference stream,
|
|
which is set through the ‘<samp>reference_stream</samp>’ option.
|
|
</p>
|
|
<p>Note that if you want accurate splitting for a video file, you need to
|
|
make the input key frames correspond to the exact splitting times
|
|
expected by the segmenter, or the segment muxer will start the new
|
|
segment with the key frame found next after the specified start
|
|
time.
|
|
</p>
|
|
<p>The segment muxer works best with a single constant frame rate video.
|
|
</p>
|
|
<p>Optionally it can generate a list of the created segments, by setting
|
|
the option <var>segment_list</var>. The list type is specified by the
|
|
<var>segment_list_type</var> option. The entry filenames in the segment
|
|
list are set by default to the basename of the corresponding segment
|
|
files.
|
|
</p>
|
|
<p>See also the <a href="#hls">hls</a> muxer, which provides a more specific
|
|
implementation for HLS segmentation.
|
|
</p>
|
|
<a name="Options-5"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Options-5">4.16.1 Options</a></h3>
|
|
|
|
<p>The segment muxer supports the following options:
|
|
</p>
|
|
<dl compact="compact">
|
|
<dt> ‘<samp>reference_stream <var>specifier</var></samp>’</dt>
|
|
<dd><p>Set the reference stream, as specified by the string <var>specifier</var>.
|
|
If <var>specifier</var> is set to <code>auto</code>, the reference is chosen
|
|
automatically. Otherwise it must be a stream specifier (see the “Stream
|
|
specifiers” chapter in the ffmpeg manual) which specifies the
|
|
reference stream. The default value is <code>auto</code>.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_format <var>format</var></samp>’</dt>
|
|
<dd><p>Override the inner container format, by default it is guessed by the filename
|
|
extension.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_list <var>name</var></samp>’</dt>
|
|
<dd><p>Generate also a listfile named <var>name</var>. If not specified no
|
|
listfile is generated.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_list_flags <var>flags</var></samp>’</dt>
|
|
<dd><p>Set flags affecting the segment list generation.
|
|
</p>
|
|
<p>It currently supports the following flags:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>cache</samp>’</dt>
|
|
<dd><p>Allow caching (only affects M3U8 list files).
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>live</samp>’</dt>
|
|
<dd><p>Allow live-friendly file generation.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
</dd>
|
|
<dt> ‘<samp>segment_list_size <var>size</var></samp>’</dt>
|
|
<dd><p>Update the list file so that it contains at most the last <var>size</var>
|
|
segments. If 0 the list file will contain all the segments. Default
|
|
value is 0.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_list_entry_prefix <var>prefix</var></samp>’</dt>
|
|
<dd><p>Set <var>prefix</var> to prepend to the name of each entry filename. By
|
|
default no prefix is applied.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_list_type <var>type</var></samp>’</dt>
|
|
<dd><p>Specify the format for the segment list file.
|
|
</p>
|
|
<p>The following values are recognized:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>flat</samp>’</dt>
|
|
<dd><p>Generate a flat list for the created segments, one segment per line.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>csv, ext</samp>’</dt>
|
|
<dd><p>Generate a list for the created segments, one segment per line,
|
|
each line matching the format (comma-separated values):
|
|
</p><table><tr><td> </td><td><pre class="example"><var>segment_filename</var>,<var>segment_start_time</var>,<var>segment_end_time</var>
|
|
</pre></td></tr></table>
|
|
|
|
<p><var>segment_filename</var> is the name of the output file generated by the
|
|
muxer according to the provided pattern. CSV escaping (according to
|
|
RFC4180) is applied if required.
|
|
</p>
|
|
<p><var>segment_start_time</var> and <var>segment_end_time</var> specify
|
|
the segment start and end time expressed in seconds.
|
|
</p>
|
|
<p>A list file with the suffix <code>".csv"</code> or <code>".ext"</code> will
|
|
auto-select this format.
|
|
</p>
|
|
<p>‘<samp>ext</samp>’ is deprecated in favor or ‘<samp>csv</samp>’.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>ffconcat</samp>’</dt>
|
|
<dd><p>Generate an ffconcat file for the created segments. The resulting file
|
|
can be read using the FFmpeg <a href="#concat">concat</a> demuxer.
|
|
</p>
|
|
<p>A list file with the suffix <code>".ffcat"</code> or <code>".ffconcat"</code> will
|
|
auto-select this format.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>m3u8</samp>’</dt>
|
|
<dd><p>Generate an extended M3U8 file, version 3, compliant with
|
|
<a href="http://tools.ietf.org/id/draft-pantos-http-live-streaming">http://tools.ietf.org/id/draft-pantos-http-live-streaming</a>.
|
|
</p>
|
|
<p>A list file with the suffix <code>".m3u8"</code> will auto-select this format.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<p>If not specified the type is guessed from the list file name suffix.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_time <var>time</var></samp>’</dt>
|
|
<dd><p>Set segment duration to <var>time</var>, the value must be a duration
|
|
specification. Default value is "2". See also the
|
|
‘<samp>segment_times</samp>’ option.
|
|
</p>
|
|
<p>Note that splitting may not be accurate, unless you force the
|
|
reference stream key-frames at the given time. See the introductory
|
|
notice and the examples below.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_time_delta <var>delta</var></samp>’</dt>
|
|
<dd><p>Specify the accuracy time when selecting the start time for a
|
|
segment, expressed as a duration specification. Default value is "0".
|
|
</p>
|
|
<p>When delta is specified a key-frame will start a new segment if its
|
|
PTS satisfies the relation:
|
|
</p><table><tr><td> </td><td><pre class="example">PTS >= start_time - time_delta
|
|
</pre></td></tr></table>
|
|
|
|
<p>This option is useful when splitting video content, which is always
|
|
split at GOP boundaries, in case a key frame is found just before the
|
|
specified split time.
|
|
</p>
|
|
<p>In particular may be used in combination with the ‘<tt>ffmpeg</tt>’ option
|
|
<var>force_key_frames</var>. The key frame times specified by
|
|
<var>force_key_frames</var> may not be set accurately because of rounding
|
|
issues, with the consequence that a key frame time may result set just
|
|
before the specified time. For constant frame rate videos a value of
|
|
1/(2*<var>frame_rate</var>) should address the worst case mismatch between
|
|
the specified time and the time set by <var>force_key_frames</var>.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_times <var>times</var></samp>’</dt>
|
|
<dd><p>Specify a list of split points. <var>times</var> contains a list of comma
|
|
separated duration specifications, in increasing order. See also
|
|
the ‘<samp>segment_time</samp>’ option.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_frames <var>frames</var></samp>’</dt>
|
|
<dd><p>Specify a list of split video frame numbers. <var>frames</var> contains a
|
|
list of comma separated integer numbers, in increasing order.
|
|
</p>
|
|
<p>This option specifies to start a new segment whenever a reference
|
|
stream key frame is found and the sequential number (starting from 0)
|
|
of the frame is greater or equal to the next value in the list.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_wrap <var>limit</var></samp>’</dt>
|
|
<dd><p>Wrap around segment index once it reaches <var>limit</var>.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>segment_start_number <var>number</var></samp>’</dt>
|
|
<dd><p>Set the sequence number of the first segment. Defaults to <code>0</code>.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>reset_timestamps <var>1|0</var></samp>’</dt>
|
|
<dd><p>Reset timestamps at the begin of each segment, so that each segment
|
|
will start with near-zero timestamps. It is meant to ease the playback
|
|
of the generated segments. May not work with some combinations of
|
|
muxers/codecs. It is set to <code>0</code> by default.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>initial_offset <var>offset</var></samp>’</dt>
|
|
<dd><p>Specify timestamp offset to apply to the output packet timestamps. The
|
|
argument must be a time duration specification, and defaults to 0.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<a name="Examples-6"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Examples-6">4.16.2 Examples</a></h3>
|
|
|
|
<ul>
|
|
<li>
|
|
To remux the content of file ‘<tt>in.mkv</tt>’ to a list of segments
|
|
‘<tt>out-000.nut</tt>’, ‘<tt>out-001.nut</tt>’, etc., and write the list of
|
|
generated segments to ‘<tt>out.list</tt>’:
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.list out%03d.nut
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
As the example above, but segment the input file according to the split
|
|
points specified by the <var>segment_times</var> option:
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.csv -segment_times 1,2,3,5,8,13,21 out%03d.nut
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
As the example above, but use the <code>ffmpeg</code> ‘<samp>force_key_frames</samp>’
|
|
option to force key frames in the input at the specified location, together
|
|
with the segment option ‘<samp>segment_time_delta</samp>’ to account for
|
|
possible roundings operated when setting key frame times.
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i in.mkv -force_key_frames 1,2,3,5,8,13,21 -codec:v mpeg4 -codec:a pcm_s16le -map 0 \
|
|
-f segment -segment_list out.csv -segment_times 1,2,3,5,8,13,21 -segment_time_delta 0.05 out%03d.nut
|
|
</pre></td></tr></table>
|
|
<p>In order to force key frames on the input file, transcoding is
|
|
required.
|
|
</p>
|
|
</li><li>
|
|
Segment the input file by splitting the input file according to the
|
|
frame numbers sequence specified with the ‘<samp>segment_frames</samp>’ option:
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.csv -segment_frames 100,200,300,500,800 out%03d.nut
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
To convert the ‘<tt>in.mkv</tt>’ to TS segments using the <code>libx264</code>
|
|
and <code>libfaac</code> encoders:
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i in.mkv -map 0 -codec:v libx264 -codec:a libfaac -f ssegment -segment_list out.list out%03d.ts
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
Segment the input file, and create an M3U8 live playlist (can be used
|
|
as live HLS source):
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -re -i in.mkv -codec copy -map 0 -f segment -segment_list playlist.m3u8 \
|
|
-segment_list_flags +live -segment_time 10 out%03d.mkv
|
|
</pre></td></tr></table>
|
|
</li></ul>
|
|
|
|
<a name="tee"></a>
|
|
<h2 class="section"><a href="ffmpeg-formats.html#toc-tee">4.17 tee</a></h2>
|
|
|
|
<p>The tee muxer can be used to write the same data to several files or any
|
|
other kind of muxer. It can be used, for example, to both stream a video to
|
|
the network and save it to disk at the same time.
|
|
</p>
|
|
<p>It is different from specifying several outputs to the <code>ffmpeg</code>
|
|
command-line tool because the audio and video data will be encoded only once
|
|
with the tee muxer; encoding can be a very expensive process. It is not
|
|
useful when using the libavformat API directly because it is then possible
|
|
to feed the same packets to several muxers directly.
|
|
</p>
|
|
<p>The slave outputs are specified in the file name given to the muxer,
|
|
separated by ’|’. If any of the slave name contains the ’|’ separator,
|
|
leading or trailing spaces or any special character, it must be
|
|
escaped (see <a href="ffmpeg-utils.html#quoting_005fand_005fescaping">(ffmpeg-utils)quoting_and_escaping</a>).
|
|
</p>
|
|
<p>Muxer options can be specified for each slave by prepending them as a list of
|
|
<var>key</var>=<var>value</var> pairs separated by ’:’, between square brackets. If
|
|
the options values contain a special character or the ’:’ separator, they
|
|
must be escaped; note that this is a second level escaping.
|
|
</p>
|
|
<p>The following special options are also recognized:
|
|
</p><dl compact="compact">
|
|
<dt> ‘<samp>f</samp>’</dt>
|
|
<dd><p>Specify the format name. Useful if it cannot be guessed from the
|
|
output name suffix.
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>bsfs[/<var>spec</var>]</samp>’</dt>
|
|
<dd><p>Specify a list of bitstream filters to apply to the specified
|
|
output.
|
|
</p>
|
|
<p>It is possible to specify to which streams a given bitstream filter
|
|
applies, by appending a stream specifier to the option separated by
|
|
<code>/</code>. <var>spec</var> must be a stream specifier (see <a href="#Format-stream-specifiers">Format stream specifiers</a>). If the stream specifier is not specified, the
|
|
bistream filters will be applied to all streams in the output.
|
|
</p>
|
|
<p>Several bitstream filters can be specified, separated by ",".
|
|
</p>
|
|
</dd>
|
|
<dt> ‘<samp>select</samp>’</dt>
|
|
<dd><p>Select the streams that should be mapped to the slave output,
|
|
specified by a stream specifier. If not specified, this defaults to
|
|
all the input streams.
|
|
</p></dd>
|
|
</dl>
|
|
|
|
<a name="Examples-2"></a>
|
|
<h3 class="subsection"><a href="ffmpeg-formats.html#toc-Examples-2">4.17.1 Examples</a></h3>
|
|
|
|
<ul>
|
|
<li>
|
|
Encode something and both archive it in a WebM file and stream it
|
|
as MPEG-TS over UDP (the streams need to be explicitly mapped):
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a
|
|
"archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/"
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
Use <code>ffmpeg</code> to encode the input, and send the output
|
|
to three different destinations. The <code>dump_extra</code> bitstream
|
|
filter is used to add extradata information to all the output video
|
|
keyframes packets, as requested by the MPEG-TS format. The select
|
|
option is applied to ‘<tt>out.aac</tt>’ in order to make it contain only
|
|
audio packets.
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac -strict experimental
|
|
-f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=a]out.aac"
|
|
</pre></td></tr></table>
|
|
|
|
</li><li>
|
|
As below, but select only stream <code>a:1</code> for the audio output. Note
|
|
that a second level escaping must be performed, as ":" is a special
|
|
character used to separate options.
|
|
<table><tr><td> </td><td><pre class="example">ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac -strict experimental
|
|
-f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=\'a:1\']out.aac"
|
|
</pre></td></tr></table>
|
|
</li></ul>
|
|
|
|
<p>Note: some codecs may need different options depending on the output format;
|
|
the auto-detection of this can not work with the tee muxer. The main example
|
|
is the ‘<samp>global_header</samp>’ flag.
|
|
</p>
|
|
<a name="Metadata-1"></a>
|
|
<h1 class="chapter"><a href="ffmpeg-formats.html#toc-Metadata-1">5. Metadata</a></h1>
|
|
|
|
<p>FFmpeg is able to dump metadata from media files into a simple UTF-8-encoded
|
|
INI-like text file and then load it back using the metadata muxer/demuxer.
|
|
</p>
|
|
<p>The file format is as follows:
|
|
</p><ol>
|
|
<li>
|
|
A file consists of a header and a number of metadata tags divided into sections,
|
|
each on its own line.
|
|
|
|
</li><li>
|
|
The header is a ’;FFMETADATA’ string, followed by a version number (now 1).
|
|
|
|
</li><li>
|
|
Metadata tags are of the form ’key=value’
|
|
|
|
</li><li>
|
|
Immediately after header follows global metadata
|
|
|
|
</li><li>
|
|
After global metadata there may be sections with per-stream/per-chapter
|
|
metadata.
|
|
|
|
</li><li>
|
|
A section starts with the section name in uppercase (i.e. STREAM or CHAPTER) in
|
|
brackets (’[’, ’]’) and ends with next section or end of file.
|
|
|
|
</li><li>
|
|
At the beginning of a chapter section there may be an optional timebase to be
|
|
used for start/end values. It must be in form ’TIMEBASE=num/den’, where num and
|
|
den are integers. If the timebase is missing then start/end times are assumed to
|
|
be in milliseconds.
|
|
Next a chapter section must contain chapter start and end times in form
|
|
’START=num’, ’END=num’, where num is a positive integer.
|
|
|
|
</li><li>
|
|
Empty lines and lines starting with ’;’ or ’#’ are ignored.
|
|
|
|
</li><li>
|
|
Metadata keys or values containing special characters (’=’, ’;’, ’#’, ’\’ and a
|
|
newline) must be escaped with a backslash ’\’.
|
|
|
|
</li><li>
|
|
Note that whitespace in metadata (e.g. foo = bar) is considered to be a part of
|
|
the tag (in the example above key is ’foo ’, value is ’ bar’).
|
|
</li></ol>
|
|
|
|
<p>A ffmetadata file might look like this:
|
|
</p><table><tr><td> </td><td><pre class="example">;FFMETADATA1
|
|
title=bike\\shed
|
|
;this is a comment
|
|
artist=FFmpeg troll team
|
|
|
|
[CHAPTER]
|
|
TIMEBASE=1/1000
|
|
START=0
|
|
#chapter ends at 0:01:00
|
|
END=60000
|
|
title=chapter \#1
|
|
[STREAM]
|
|
title=multi\
|
|
line
|
|
</pre></td></tr></table>
|
|
|
|
<p>By using the ffmetadata muxer and demuxer it is possible to extract
|
|
metadata from an input file to an ffmetadata file, and then transcode
|
|
the file into an output file with the edited ffmetadata file.
|
|
</p>
|
|
<p>Extracting an ffmetadata file with ‘<tt>ffmpeg</tt>’ goes as follows:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -f ffmetadata FFMETADATAFILE
|
|
</pre></td></tr></table>
|
|
|
|
<p>Reinserting edited metadata information from the FFMETADATAFILE file can
|
|
be done as:
|
|
</p><table><tr><td> </td><td><pre class="example">ffmpeg -i INPUT -i FFMETADATAFILE -map_metadata 1 -codec copy OUTPUT
|
|
</pre></td></tr></table>
|
|
|
|
|
|
<a name="See-Also"></a>
|
|
<h1 class="chapter"><a href="ffmpeg-formats.html#toc-See-Also">6. See Also</a></h1>
|
|
|
|
<p><a href="ffmpeg.html">ffmpeg</a>, <a href="ffplay.html">ffplay</a>, <a href="ffprobe.html">ffprobe</a>, <a href="ffserver.html">ffserver</a>,
|
|
<a href="libavformat.html">libavformat</a>
|
|
</p>
|
|
|
|
<a name="Authors"></a>
|
|
<h1 class="chapter"><a href="ffmpeg-formats.html#toc-Authors">7. Authors</a></h1>
|
|
|
|
<p>The FFmpeg developers.
|
|
</p>
|
|
<p>For details about the authorship, see the Git history of the project
|
|
(git://source.ffmpeg.org/ffmpeg), e.g. by typing the command
|
|
<code>git log</code> in the FFmpeg source directory, or browsing the
|
|
online repository at <a href="http://source.ffmpeg.org">http://source.ffmpeg.org</a>.
|
|
</p>
|
|
<p>Maintainers for the specific components are listed in the file
|
|
‘<tt>MAINTAINERS</tt>’ in the source code tree.
|
|
</p>
|
|
|
|
<footer class="footer pagination-right">
|
|
<span class="label label-info">This document was generated by <em>Kyle Schwarz</em> on <em>April 4, 2014</em> using <a href="http://www.nongnu.org/texi2html/"><em>texi2html 1.82</em></a>.</span></footer></div></div></body>
|