summaryrefslogtreecommitdiff
path: root/doc/muxers.texi (plain)
blob: 166c929369261717c1603015748c2325c7241492
1@chapter Muxers
2@c man begin MUXERS
3
4Muxers are configured elements in FFmpeg which allow writing
5multimedia streams to a particular type of file.
6
7When you configure your FFmpeg build, all the supported muxers
8are enabled by default. You can list all available muxers using the
9configure option @code{--list-muxers}.
10
11You can disable all the muxers with the configure option
12@code{--disable-muxers} and selectively enable / disable single muxers
13with the options @code{--enable-muxer=@var{MUXER}} /
14@code{--disable-muxer=@var{MUXER}}.
15
16The option @code{-muxers} of the ff* tools will display the list of
17enabled muxers. Use @code{-formats} to view a combined list of
18enabled demuxers and muxers.
19
20A description of some of the currently available muxers follows.
21
22@anchor{aiff}
23@section aiff
24
25Audio Interchange File Format muxer.
26
27@subsection Options
28
29It accepts the following options:
30
31@table @option
32@item write_id3v2
33Enable ID3v2 tags writing when set to 1. Default is 0 (disabled).
34
35@item id3v2_version
36Select ID3v2 version to write. Currently only version 3 and 4 (aka.
37ID3v2.3 and ID3v2.4) are supported. The default is version 4.
38
39@end table
40
41@anchor{asf}
42@section asf
43
44Advanced Systems Format muxer.
45
46Note that Windows Media Audio (wma) and Windows Media Video (wmv) use this
47muxer too.
48
49@subsection Options
50
51It accepts the following options:
52
53@table @option
54@item packet_size
55Set the muxer packet size. By tuning this setting you may reduce data
56fragmentation or muxer overhead depending on your source. Default value is
573200, minimum is 100, maximum is 64k.
58
59@end table
60
61@anchor{avi}
62@section avi
63
64Audio Video Interleaved muxer.
65
66@subsection Options
67
68It accepts the following options:
69
70@table @option
71@item reserve_index_space
72Reserve the specified amount of bytes for the OpenDML master index of each
73stream within the file header. By default additional master indexes are
74embedded within the data packets if there is no space left in the first master
75index and are linked together as a chain of indexes. This index structure can
76cause problems for some use cases, e.g. third-party software strictly relying
77on the OpenDML index specification or when file seeking is slow. Reserving
78enough index space in the file header avoids these problems.
79
80The required index space depends on the output file size and should be about 16
81bytes per gigabyte. When this option is omitted or set to zero the necessary
82index space is guessed.
83
84@item write_channel_mask
85Write the channel layout mask into the audio stream header.
86
87This option is enabled by default. Disabling the channel mask can be useful in
88specific scenarios, e.g. when merging multiple audio streams into one for
89compatibility with software that only supports a single audio stream in AVI
90(see @ref{amerge,,the "amerge" section in the ffmpeg-filters manual,ffmpeg-filters}).
91
92@end table
93
94@anchor{chromaprint}
95@section chromaprint
96
97Chromaprint fingerprinter
98
99This muxer feeds audio data to the Chromaprint library, which generates
100a fingerprint for the provided audio data. It takes a single signed
101native-endian 16-bit raw audio stream.
102
103@subsection Options
104
105@table @option
106@item silence_threshold
107Threshold for detecting silence, ranges from 0 to 32767. -1 for default
108(required for use with the AcoustID service).
109
110@item algorithm
111Algorithm index to fingerprint with.
112
113@item fp_format
114Format to output the fingerprint as. Accepts the following options:
115@table @samp
116@item raw
117Binary raw fingerprint
118
119@item compressed
120Binary compressed fingerprint
121
122@item base64
123Base64 compressed fingerprint
124
125@end table
126
127@end table
128
129@anchor{crc}
130@section crc
131
132CRC (Cyclic Redundancy Check) testing format.
133
134This muxer computes and prints the Adler-32 CRC of all the input audio
135and video frames. By default audio frames are converted to signed
13616-bit raw audio and video frames to raw video before computing the
137CRC.
138
139The output of the muxer consists of a single line of the form:
140CRC=0x@var{CRC}, where @var{CRC} is a hexadecimal number 0-padded to
1418 digits containing the CRC for all the decoded input frames.
142
143See also the @ref{framecrc} muxer.
144
145@subsection Examples
146
147For example to compute the CRC of the input, and store it in the file
148@file{out.crc}:
149@example
150ffmpeg -i INPUT -f crc out.crc
151@end example
152
153You can print the CRC to stdout with the command:
154@example
155ffmpeg -i INPUT -f crc -
156@end example
157
158You can select the output format of each frame with @command{ffmpeg} by
159specifying the audio and video codec and format. For example to
160compute the CRC of the input audio converted to PCM unsigned 8-bit
161and the input video converted to MPEG-2 video, use the command:
162@example
163ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f crc -
164@end example
165
166@section flv
167
168Adobe Flash Video Format muxer.
169
170This muxer accepts the following options:
171
172@table @option
173
174@item flvflags @var{flags}
175Possible values:
176
177@table @samp
178
179@item aac_seq_header_detect
180Place AAC sequence header based on audio stream data.
181
182@item no_sequence_end
183Disable sequence end tag.
184
185@item no_metadata
186Disable metadata tag.
187
188@item no_duration_filesize
189Disable duration and filesize in metadata when they are equal to zero
190at the end of stream. (Be used to non-seekable living stream).
191
192@item add_keyframe_index
193Used to facilitate seeking; particularly for HTTP pseudo streaming.
194@end table
195@end table
196
197@anchor{framecrc}
198@section framecrc
199
200Per-packet CRC (Cyclic Redundancy Check) testing format.
201
202This muxer computes and prints the Adler-32 CRC for each audio
203and video packet. By default audio frames are converted to signed
20416-bit raw audio and video frames to raw video before computing the
205CRC.
206
207The output of the muxer consists of a line for each audio and video
208packet of the form:
209@example
210@var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, 0x@var{CRC}
211@end example
212
213@var{CRC} is a hexadecimal number 0-padded to 8 digits containing the
214CRC of the packet.
215
216@subsection Examples
217
218For example to compute the CRC of the audio and video frames in
219@file{INPUT}, converted to raw audio and video packets, and store it
220in the file @file{out.crc}:
221@example
222ffmpeg -i INPUT -f framecrc out.crc
223@end example
224
225To print the information to stdout, use the command:
226@example
227ffmpeg -i INPUT -f framecrc -
228@end example
229
230With @command{ffmpeg}, you can select the output format to which the
231audio and video frames are encoded before computing the CRC for each
232packet by specifying the audio and video codec. For example, to
233compute the CRC of each decoded input audio frame converted to PCM
234unsigned 8-bit and of each decoded input video frame converted to
235MPEG-2 video, use the command:
236@example
237ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f framecrc -
238@end example
239
240See also the @ref{crc} muxer.
241
242@anchor{framehash}
243@section framehash
244
245Per-packet hash testing format.
246
247This muxer computes and prints a cryptographic hash for each audio
248and video packet. This can be used for packet-by-packet equality
249checks without having to individually do a binary comparison on each.
250
251By default audio frames are converted to signed 16-bit raw audio and
252video frames to raw video before computing the hash, but the output
253of explicit conversions to other codecs can also be used. It uses the
254SHA-256 cryptographic hash function by default, but supports several
255other algorithms.
256
257The output of the muxer consists of a line for each audio and video
258packet of the form:
259@example
260@var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, @var{hash}
261@end example
262
263@var{hash} is a hexadecimal number representing the computed hash
264for the packet.
265
266@table @option
267@item hash @var{algorithm}
268Use the cryptographic hash function specified by the string @var{algorithm}.
269Supported values include @code{MD5}, @code{murmur3}, @code{RIPEMD128},
270@code{RIPEMD160}, @code{RIPEMD256}, @code{RIPEMD320}, @code{SHA160},
271@code{SHA224}, @code{SHA256} (default), @code{SHA512/224}, @code{SHA512/256},
272@code{SHA384}, @code{SHA512}, @code{CRC32} and @code{adler32}.
273
274@end table
275
276@subsection Examples
277
278To compute the SHA-256 hash of the audio and video frames in @file{INPUT},
279converted to raw audio and video packets, and store it in the file
280@file{out.sha256}:
281@example
282ffmpeg -i INPUT -f framehash out.sha256
283@end example
284
285To print the information to stdout, using the MD5 hash function, use
286the command:
287@example
288ffmpeg -i INPUT -f framehash -hash md5 -
289@end example
290
291See also the @ref{hash} muxer.
292
293@anchor{framemd5}
294@section framemd5
295
296Per-packet MD5 testing format.
297
298This is a variant of the @ref{framehash} muxer. Unlike that muxer,
299it defaults to using the MD5 hash function.
300
301@subsection Examples
302
303To compute the MD5 hash of the audio and video frames in @file{INPUT},
304converted to raw audio and video packets, and store it in the file
305@file{out.md5}:
306@example
307ffmpeg -i INPUT -f framemd5 out.md5
308@end example
309
310To print the information to stdout, use the command:
311@example
312ffmpeg -i INPUT -f framemd5 -
313@end example
314
315See also the @ref{framehash} and @ref{md5} muxers.
316
317@anchor{gif}
318@section gif
319
320Animated GIF muxer.
321
322It accepts the following options:
323
324@table @option
325@item loop
326Set the number of times to loop the output. Use @code{-1} for no loop, @code{0}
327for looping indefinitely (default).
328
329@item final_delay
330Force the delay (expressed in centiseconds) after the last frame. Each frame
331ends with a delay until the next frame. The default is @code{-1}, which is a
332special value to tell the muxer to re-use the previous delay. In case of a
333loop, you might want to customize this value to mark a pause for instance.
334@end table
335
336For example, to encode a gif looping 10 times, with a 5 seconds delay between
337the loops:
338@example
339ffmpeg -i INPUT -loop 10 -final_delay 500 out.gif
340@end example
341
342Note 1: if you wish to extract the frames into separate GIF files, you need to
343force the @ref{image2} muxer:
344@example
345ffmpeg -i INPUT -c:v gif -f image2 "out%d.gif"
346@end example
347
348Note 2: the GIF format has a very large time base: the delay between two frames
349can therefore not be smaller than one centi second.
350
351@anchor{hash}
352@section hash
353
354Hash testing format.
355
356This muxer computes and prints a cryptographic hash of all the input
357audio and video frames. This can be used for equality checks without
358having to do a complete binary comparison.
359
360By default audio frames are converted to signed 16-bit raw audio and
361video frames to raw video before computing the hash, but the output
362of explicit conversions to other codecs can also be used. Timestamps
363are ignored. It uses the SHA-256 cryptographic hash function by default,
364but supports several other algorithms.
365
366The output of the muxer consists of a single line of the form:
367@var{algo}=@var{hash}, where @var{algo} is a short string representing
368the hash function used, and @var{hash} is a hexadecimal number
369representing the computed hash.
370
371@table @option
372@item hash @var{algorithm}
373Use the cryptographic hash function specified by the string @var{algorithm}.
374Supported values include @code{MD5}, @code{murmur3}, @code{RIPEMD128},
375@code{RIPEMD160}, @code{RIPEMD256}, @code{RIPEMD320}, @code{SHA160},
376@code{SHA224}, @code{SHA256} (default), @code{SHA512/224}, @code{SHA512/256},
377@code{SHA384}, @code{SHA512}, @code{CRC32} and @code{adler32}.
378
379@end table
380
381@subsection Examples
382
383To compute the SHA-256 hash of the input converted to raw audio and
384video, and store it in the file @file{out.sha256}:
385@example
386ffmpeg -i INPUT -f hash out.sha256
387@end example
388
389To print an MD5 hash to stdout use the command:
390@example
391ffmpeg -i INPUT -f hash -hash md5 -
392@end example
393
394See also the @ref{framehash} muxer.
395
396@anchor{hls}
397@section hls
398
399Apple HTTP Live Streaming muxer that segments MPEG-TS according to
400the HTTP Live Streaming (HLS) specification.
401
402It creates a playlist file, and one or more segment files. The output filename
403specifies the playlist filename.
404
405By default, the muxer creates a file for each segment produced. These files
406have the same name as the playlist, followed by a sequential number and a
407.ts extension.
408
409For example, to convert an input file with @command{ffmpeg}:
410@example
411ffmpeg -i in.nut out.m3u8
412@end example
413This example will produce the playlist, @file{out.m3u8}, and segment files:
414@file{out0.ts}, @file{out1.ts}, @file{out2.ts}, etc.
415
416See also the @ref{segment} muxer, which provides a more generic and
417flexible implementation of a segmenter, and can be used to perform HLS
418segmentation.
419
420@subsection Options
421
422This muxer supports the following options:
423
424@table @option
425@item hls_init_time @var{seconds}
426Set the initial target segment length in seconds. Default value is @var{0}.
427Segment will be cut on the next key frame after this time has passed on the first m3u8 list.
428After the initial playlist is filled @command{ffmpeg} will cut segments
429at duration equal to @code{hls_time}
430
431@item hls_time @var{seconds}
432Set the target segment length in seconds. Default value is 2.
433Segment will be cut on the next key frame after this time has passed.
434
435@item hls_list_size @var{size}
436Set the maximum number of playlist entries. If set to 0 the list file
437will contain all the segments. Default value is 5.
438
439@item hls_ts_options @var{options_list}
440Set output format options using a :-separated list of key=value
441parameters. Values containing @code{:} special characters must be
442escaped.
443
444@item hls_wrap @var{wrap}
445This is a deprecated option, you can use @code{hls_list_size}
446and @code{hls_flags delete_segments} instead it
447
448This option is useful to avoid to fill the disk with many segment
449files, and limits the maximum number of segment files written to disk
450to @var{wrap}.
451
452
453@item hls_start_number_source
454Start the playlist sequence number (@code{#EXT-X-MEDIA-SEQUENCE}) according to the specified source.
455Unless @code{hls_flags single_file} is set, it also specifies source of starting sequence numbers of
456segment and subtitle filenames. In any case, if @code{hls_flags append_list}
457is set and read playlist sequence number is greater than the specified start sequence number,
458then that value will be used as start value.
459
460It accepts the following values:
461
462@table @option
463
464@item generic (default)
465Set the starting sequence numbers according to @var{start_number} option value.
466
467@item epoch
468The start number will be the seconds since epoch (1970-01-01 00:00:00)
469
470@item datetime
471The start number will be based on the current date/time as YYYYmmddHHMMSS. e.g. 20161231235759.
472
473@end table
474
475@item start_number @var{number}
476Start the playlist sequence number (@code{#EXT-X-MEDIA-SEQUENCE}) from the specified @var{number}
477when @var{hls_start_number_source} value is @var{generic}. (This is the default case.)
478Unless @code{hls_flags single_file} is set, it also specifies starting sequence numbers of segment and subtitle filenames.
479Default value is 0.
480
481@item hls_allow_cache @var{allowcache}
482Explicitly set whether the client MAY (1) or MUST NOT (0) cache media segments.
483
484@item hls_base_url @var{baseurl}
485Append @var{baseurl} to every entry in the playlist.
486Useful to generate playlists with absolute paths.
487
488Note that the playlist sequence number must be unique for each segment
489and it is not to be confused with the segment filename sequence number
490which can be cyclic, for example if the @option{wrap} option is
491specified.
492
493@item hls_segment_filename @var{filename}
494Set the segment filename. Unless @code{hls_flags single_file} is set,
495@var{filename} is used as a string format with the segment number:
496@example
497ffmpeg -i in.nut -hls_segment_filename 'file%03d.ts' out.m3u8
498@end example
499This example will produce the playlist, @file{out.m3u8}, and segment files:
500@file{file000.ts}, @file{file001.ts}, @file{file002.ts}, etc.
501
502@var{filename} may contain full path or relative path specification,
503but only the file name part without any path info will be contained in the m3u8 segment list.
504Should a relative path be specified, the path of the created segment
505files will be relative to the current working directory.
506When use_localtime_mkdir is set, the whole expanded value of @var{filename} will be written into the m3u8 segment list.
507
508
509@item use_localtime
510Use strftime() on @var{filename} to expand the segment filename with localtime.
511The segment number is also available in this mode, but to use it, you need to specify second_level_segment_index
512hls_flag and %%d will be the specifier.
513@example
514ffmpeg -i in.nut -use_localtime 1 -hls_segment_filename 'file-%Y%m%d-%s.ts' out.m3u8
515@end example
516This example will produce the playlist, @file{out.m3u8}, and segment files:
517@file{file-20160215-1455569023.ts}, @file{file-20160215-1455569024.ts}, etc.
518Note: On some systems/environments, the @code{%s} specifier is not available. See
519 @code{strftime()} documentation.
520@example
521ffmpeg -i in.nut -use_localtime 1 -hls_flags second_level_segment_index -hls_segment_filename 'file-%Y%m%d-%%04d.ts' out.m3u8
522@end example
523This example will produce the playlist, @file{out.m3u8}, and segment files:
524@file{file-20160215-0001.ts}, @file{file-20160215-0002.ts}, etc.
525
526@item use_localtime_mkdir
527Used together with -use_localtime, it will create all subdirectories which
528is expanded in @var{filename}.
529@example
530ffmpeg -i in.nut -use_localtime 1 -use_localtime_mkdir 1 -hls_segment_filename '%Y%m%d/file-%Y%m%d-%s.ts' out.m3u8
531@end example
532This example will create a directory 201560215 (if it does not exist), and then
533produce the playlist, @file{out.m3u8}, and segment files:
534@file{20160215/file-20160215-1455569023.ts}, @file{20160215/file-20160215-1455569024.ts}, etc.
535
536@example
537ffmpeg -i in.nut -use_localtime 1 -use_localtime_mkdir 1 -hls_segment_filename '%Y/%m/%d/file-%Y%m%d-%s.ts' out.m3u8
538@end example
539This example will create a directory hierarchy 2016/02/15 (if any of them do not exist), and then
540produce the playlist, @file{out.m3u8}, and segment files:
541@file{2016/02/15/file-20160215-1455569023.ts}, @file{2016/02/15/file-20160215-1455569024.ts}, etc.
542
543
544@item hls_key_info_file @var{key_info_file}
545Use the information in @var{key_info_file} for segment encryption. The first
546line of @var{key_info_file} specifies the key URI written to the playlist. The
547key URL is used to access the encryption key during playback. The second line
548specifies the path to the key file used to obtain the key during the encryption
549process. The key file is read as a single packed array of 16 octets in binary
550format. The optional third line specifies the initialization vector (IV) as a
551hexadecimal string to be used instead of the segment sequence number (default)
552for encryption. Changes to @var{key_info_file} will result in segment
553encryption with the new key/IV and an entry in the playlist for the new key
554URI/IV.
555
556Key info file format:
557@example
558@var{key URI}
559@var{key file path}
560@var{IV} (optional)
561@end example
562
563Example key URIs:
564@example
565http://server/file.key
566/path/to/file.key
567file.key
568@end example
569
570Example key file paths:
571@example
572file.key
573/path/to/file.key
574@end example
575
576Example IV:
577@example
5780123456789ABCDEF0123456789ABCDEF
579@end example
580
581Key info file example:
582@example
583http://server/file.key
584/path/to/file.key
5850123456789ABCDEF0123456789ABCDEF
586@end example
587
588Example shell script:
589@example
590#!/bin/sh
591BASE_URL=$@{1:-'.'@}
592openssl rand 16 > file.key
593echo $BASE_URL/file.key > file.keyinfo
594echo file.key >> file.keyinfo
595echo $(openssl rand -hex 16) >> file.keyinfo
596ffmpeg -f lavfi -re -i testsrc -c:v h264 -hls_flags delete_segments \
597 -hls_key_info_file file.keyinfo out.m3u8
598@end example
599
600
601@item hls_flags @var{flags}
602Possible values:
603
604@table @samp
605@item single_file
606If this flag is set, the muxer will store all segments in a single MPEG-TS
607file, and will use byte ranges in the playlist. HLS playlists generated with
608this way will have the version number 4.
609For example:
610@example
611ffmpeg -i in.nut -hls_flags single_file out.m3u8
612@end example
613Will produce the playlist, @file{out.m3u8}, and a single segment file,
614@file{out.ts}.
615
616@item delete_segments
617Segment files removed from the playlist are deleted after a period of time
618equal to the duration of the segment plus the duration of the playlist.
619
620@item append_list
621Append new segments into the end of old segment list,
622and remove the @code{#EXT-X-ENDLIST} from the old segment list.
623
624@item round_durations
625Round the duration info in the playlist file segment info to integer
626values, instead of using floating point.
627
628@item discont_start
629Add the @code{#EXT-X-DISCONTINUITY} tag to the playlist, before the
630first segment's information.
631
632@item omit_endlist
633Do not append the @code{EXT-X-ENDLIST} tag at the end of the playlist.
634
635@item split_by_time
636Allow segments to start on frames other than keyframes. This improves
637behavior on some players when the time between keyframes is inconsistent,
638but may make things worse on others, and can cause some oddities during
639seeking. This flag should be used with the @code{hls_time} option.
640
641@item program_date_time
642Generate @code{EXT-X-PROGRAM-DATE-TIME} tags.
643
644@item second_level_segment_index
645Makes it possible to use segment indexes as %%d in hls_segment_filename expression
646besides date/time values when use_localtime is on.
647To get fixed width numbers with trailing zeroes, %%0xd format is available where x is the required width.
648
649@item second_level_segment_size
650Makes it possible to use segment sizes (counted in bytes) as %%s in hls_segment_filename
651expression besides date/time values when use_localtime is on.
652To get fixed width numbers with trailing zeroes, %%0xs format is available where x is the required width.
653
654@item second_level_segment_duration
655Makes it possible to use segment duration (calculated in microseconds) as %%t in hls_segment_filename
656expression besides date/time values when use_localtime is on.
657To get fixed width numbers with trailing zeroes, %%0xt format is available where x is the required width.
658
659@example
660ffmpeg -i sample.mpeg \
661 -f hls -hls_time 3 -hls_list_size 5 \
662 -hls_flags second_level_segment_index+second_level_segment_size+second_level_segment_duration \
663 -use_localtime 1 -use_localtime_mkdir 1 -hls_segment_filename "segment_%Y%m%d%H%M%S_%%04d_%%08s_%%013t.ts" stream.m3u8
664@end example
665This will produce segments like this:
666@file{segment_20170102194334_0003_00122200_0000003000000.ts}, @file{segment_20170102194334_0004_00120072_0000003000000.ts} etc.
667
668@item temp_file
669Write segment data to filename.tmp and rename to filename only once the segment is complete. A webserver
670serving up segments can be configured to reject requests to *.tmp to prevent access to in-progress segments
671before they have been added to the m3u8 playlist.
672
673@end table
674
675@item hls_playlist_type event
676Emit @code{#EXT-X-PLAYLIST-TYPE:EVENT} in the m3u8 header. Forces
677@option{hls_list_size} to 0; the playlist can only be appended to.
678
679@item hls_playlist_type vod
680Emit @code{#EXT-X-PLAYLIST-TYPE:VOD} in the m3u8 header. Forces
681@option{hls_list_size} to 0; the playlist must not change.
682
683@item method
684Use the given HTTP method to create the hls files.
685@example
686ffmpeg -re -i in.ts -f hls -method PUT http://example.com/live/out.m3u8
687@end example
688This example will upload all the mpegts segment files to the HTTP
689server using the HTTP PUT method, and update the m3u8 files every
690@code{refresh} times using the same method.
691Note that the HTTP server must support the given method for uploading
692files.
693@end table
694
695@anchor{ico}
696@section ico
697
698ICO file muxer.
699
700Microsoft's icon file format (ICO) has some strict limitations that should be noted:
701
702@itemize
703@item
704Size cannot exceed 256 pixels in any dimension
705
706@item
707Only BMP and PNG images can be stored
708
709@item
710If a BMP image is used, it must be one of the following pixel formats:
711@example
712BMP Bit Depth FFmpeg Pixel Format
7131bit pal8
7144bit pal8
7158bit pal8
71616bit rgb555le
71724bit bgr24
71832bit bgra
719@end example
720
721@item
722If a BMP image is used, it must use the BITMAPINFOHEADER DIB header
723
724@item
725If a PNG image is used, it must use the rgba pixel format
726@end itemize
727
728@anchor{image2}
729@section image2
730
731Image file muxer.
732
733The image file muxer writes video frames to image files.
734
735The output filenames are specified by a pattern, which can be used to
736produce sequentially numbered series of files.
737The pattern may contain the string "%d" or "%0@var{N}d", this string
738specifies the position of the characters representing a numbering in
739the filenames. If the form "%0@var{N}d" is used, the string
740representing the number in each filename is 0-padded to @var{N}
741digits. The literal character '%' can be specified in the pattern with
742the string "%%".
743
744If the pattern contains "%d" or "%0@var{N}d", the first filename of
745the file list specified will contain the number 1, all the following
746numbers will be sequential.
747
748The pattern may contain a suffix which is used to automatically
749determine the format of the image files to write.
750
751For example the pattern "img-%03d.bmp" will specify a sequence of
752filenames of the form @file{img-001.bmp}, @file{img-002.bmp}, ...,
753@file{img-010.bmp}, etc.
754The pattern "img%%-%d.jpg" will specify a sequence of filenames of the
755form @file{img%-1.jpg}, @file{img%-2.jpg}, ..., @file{img%-10.jpg},
756etc.
757
758@subsection Examples
759
760The following example shows how to use @command{ffmpeg} for creating a
761sequence of files @file{img-001.jpeg}, @file{img-002.jpeg}, ...,
762taking one image every second from the input video:
763@example
764ffmpeg -i in.avi -vsync cfr -r 1 -f image2 'img-%03d.jpeg'
765@end example
766
767Note that with @command{ffmpeg}, if the format is not specified with the
768@code{-f} option and the output filename specifies an image file
769format, the image2 muxer is automatically selected, so the previous
770command can be written as:
771@example
772ffmpeg -i in.avi -vsync cfr -r 1 'img-%03d.jpeg'
773@end example
774
775Note also that the pattern must not necessarily contain "%d" or
776"%0@var{N}d", for example to create a single image file
777@file{img.jpeg} from the start of the input video you can employ the command:
778@example
779ffmpeg -i in.avi -f image2 -frames:v 1 img.jpeg
780@end example
781
782The @option{strftime} option allows you to expand the filename with
783date and time information. Check the documentation of
784the @code{strftime()} function for the syntax.
785
786For example to generate image files from the @code{strftime()}
787"%Y-%m-%d_%H-%M-%S" pattern, the following @command{ffmpeg} command
788can be used:
789@example
790ffmpeg -f v4l2 -r 1 -i /dev/video0 -f image2 -strftime 1 "%Y-%m-%d_%H-%M-%S.jpg"
791@end example
792
793@subsection Options
794
795@table @option
796@item start_number
797Start the sequence from the specified number. Default value is 0.
798
799@item update
800If set to 1, the filename will always be interpreted as just a
801filename, not a pattern, and the corresponding file will be continuously
802overwritten with new images. Default value is 0.
803
804@item strftime
805If set to 1, expand the filename with date and time information from
806@code{strftime()}. Default value is 0.
807@end table
808
809The image muxer supports the .Y.U.V image file format. This format is
810special in that that each image frame consists of three files, for
811each of the YUV420P components. To read or write this image file format,
812specify the name of the '.Y' file. The muxer will automatically open the
813'.U' and '.V' files as required.
814
815@section matroska
816
817Matroska container muxer.
818
819This muxer implements the matroska and webm container specs.
820
821@subsection Metadata
822
823The recognized metadata settings in this muxer are:
824
825@table @option
826@item title
827Set title name provided to a single track.
828
829@item language
830Specify the language of the track in the Matroska languages form.
831
832The language can be either the 3 letters bibliographic ISO-639-2 (ISO
833639-2/B) form (like "fre" for French), or a language code mixed with a
834country code for specialities in languages (like "fre-ca" for Canadian
835French).
836
837@item stereo_mode
838Set stereo 3D video layout of two views in a single video track.
839
840The following values are recognized:
841@table @samp
842@item mono
843video is not stereo
844@item left_right
845Both views are arranged side by side, Left-eye view is on the left
846@item bottom_top
847Both views are arranged in top-bottom orientation, Left-eye view is at bottom
848@item top_bottom
849Both views are arranged in top-bottom orientation, Left-eye view is on top
850@item checkerboard_rl
851Each view is arranged in a checkerboard interleaved pattern, Left-eye view being first
852@item checkerboard_lr
853Each view is arranged in a checkerboard interleaved pattern, Right-eye view being first
854@item row_interleaved_rl
855Each view is constituted by a row based interleaving, Right-eye view is first row
856@item row_interleaved_lr
857Each view is constituted by a row based interleaving, Left-eye view is first row
858@item col_interleaved_rl
859Both views are arranged in a column based interleaving manner, Right-eye view is first column
860@item col_interleaved_lr
861Both views are arranged in a column based interleaving manner, Left-eye view is first column
862@item anaglyph_cyan_red
863All frames are in anaglyph format viewable through red-cyan filters
864@item right_left
865Both views are arranged side by side, Right-eye view is on the left
866@item anaglyph_green_magenta
867All frames are in anaglyph format viewable through green-magenta filters
868@item block_lr
869Both eyes laced in one Block, Left-eye view is first
870@item block_rl
871Both eyes laced in one Block, Right-eye view is first
872@end table
873@end table
874
875For example a 3D WebM clip can be created using the following command line:
876@example
877ffmpeg -i sample_left_right_clip.mpg -an -c:v libvpx -metadata stereo_mode=left_right -y stereo_clip.webm
878@end example
879
880@subsection Options
881
882This muxer supports the following options:
883
884@table @option
885@item reserve_index_space
886By default, this muxer writes the index for seeking (called cues in Matroska
887terms) at the end of the file, because it cannot know in advance how much space
888to leave for the index at the beginning of the file. However for some use cases
889-- e.g. streaming where seeking is possible but slow -- it is useful to put the
890index at the beginning of the file.
891
892If this option is set to a non-zero value, the muxer will reserve a given amount
893of space in the file header and then try to write the cues there when the muxing
894finishes. If the available space does not suffice, muxing will fail. A safe size
895for most use cases should be about 50kB per hour of video.
896
897Note that cues are only written if the output is seekable and this option will
898have no effect if it is not.
899@end table
900
901@anchor{md5}
902@section md5
903
904MD5 testing format.
905
906This is a variant of the @ref{hash} muxer. Unlike that muxer, it
907defaults to using the MD5 hash function.
908
909@subsection Examples
910
911To compute the MD5 hash of the input converted to raw
912audio and video, and store it in the file @file{out.md5}:
913@example
914ffmpeg -i INPUT -f md5 out.md5
915@end example
916
917You can print the MD5 to stdout with the command:
918@example
919ffmpeg -i INPUT -f md5 -
920@end example
921
922See also the @ref{hash} and @ref{framemd5} muxers.
923
924@section mov, mp4, ismv
925
926MOV/MP4/ISMV (Smooth Streaming) muxer.
927
928The mov/mp4/ismv muxer supports fragmentation. Normally, a MOV/MP4
929file has all the metadata about all packets stored in one location
930(written at the end of the file, it can be moved to the start for
931better playback by adding @var{faststart} to the @var{movflags}, or
932using the @command{qt-faststart} tool). A fragmented
933file consists of a number of fragments, where packets and metadata
934about these packets are stored together. Writing a fragmented
935file has the advantage that the file is decodable even if the
936writing is interrupted (while a normal MOV/MP4 is undecodable if
937it is not properly finished), and it requires less memory when writing
938very long files (since writing normal MOV/MP4 files stores info about
939every single packet in memory until the file is closed). The downside
940is that it is less compatible with other applications.
941
942@subsection Options
943
944Fragmentation is enabled by setting one of the AVOptions that define
945how to cut the file into fragments:
946
947@table @option
948@item -moov_size @var{bytes}
949Reserves space for the moov atom at the beginning of the file instead of placing the
950moov atom at the end. If the space reserved is insufficient, muxing will fail.
951@item -movflags frag_keyframe
952Start a new fragment at each video keyframe.
953@item -frag_duration @var{duration}
954Create fragments that are @var{duration} microseconds long.
955@item -frag_size @var{size}
956Create fragments that contain up to @var{size} bytes of payload data.
957@item -movflags frag_custom
958Allow the caller to manually choose when to cut fragments, by
959calling @code{av_write_frame(ctx, NULL)} to write a fragment with
960the packets written so far. (This is only useful with other
961applications integrating libavformat, not from @command{ffmpeg}.)
962@item -min_frag_duration @var{duration}
963Don't create fragments that are shorter than @var{duration} microseconds long.
964@end table
965
966If more than one condition is specified, fragments are cut when
967one of the specified conditions is fulfilled. The exception to this is
968@code{-min_frag_duration}, which has to be fulfilled for any of the other
969conditions to apply.
970
971Additionally, the way the output file is written can be adjusted
972through a few other options:
973
974@table @option
975@item -movflags empty_moov
976Write an initial moov atom directly at the start of the file, without
977describing any samples in it. Generally, an mdat/moov pair is written
978at the start of the file, as a normal MOV/MP4 file, containing only
979a short portion of the file. With this option set, there is no initial
980mdat atom, and the moov atom only describes the tracks but has
981a zero duration.
982
983This option is implicitly set when writing ismv (Smooth Streaming) files.
984@item -movflags separate_moof
985Write a separate moof (movie fragment) atom for each track. Normally,
986packets for all tracks are written in a moof atom (which is slightly
987more efficient), but with this option set, the muxer writes one moof/mdat
988pair for each track, making it easier to separate tracks.
989
990This option is implicitly set when writing ismv (Smooth Streaming) files.
991@item -movflags faststart
992Run a second pass moving the index (moov atom) to the beginning of the file.
993This operation can take a while, and will not work in various situations such
994as fragmented output, thus it is not enabled by default.
995@item -movflags rtphint
996Add RTP hinting tracks to the output file.
997@item -movflags disable_chpl
998Disable Nero chapter markers (chpl atom). Normally, both Nero chapters
999and a QuickTime chapter track are written to the file. With this option
1000set, only the QuickTime chapter track will be written. Nero chapters can
1001cause failures when the file is reprocessed with certain tagging programs, like
1002mp3Tag 2.61a and iTunes 11.3, most likely other versions are affected as well.
1003@item -movflags omit_tfhd_offset
1004Do not write any absolute base_data_offset in tfhd atoms. This avoids
1005tying fragments to absolute byte positions in the file/streams.
1006@item -movflags default_base_moof
1007Similarly to the omit_tfhd_offset, this flag avoids writing the
1008absolute base_data_offset field in tfhd atoms, but does so by using
1009the new default-base-is-moof flag instead. This flag is new from
101014496-12:2012. This may make the fragments easier to parse in certain
1011circumstances (avoiding basing track fragment location calculations
1012on the implicit end of the previous track fragment).
1013@item -write_tmcd
1014Specify @code{on} to force writing a timecode track, @code{off} to disable it
1015and @code{auto} to write a timecode track only for mov and mp4 output (default).
1016@end table
1017
1018@subsection Example
1019
1020Smooth Streaming content can be pushed in real time to a publishing
1021point on IIS with this muxer. Example:
1022@example
1023ffmpeg -re @var{<normal input/transcoding options>} -movflags isml+frag_keyframe -f ismv http://server/publishingpoint.isml/Streams(Encoder1)
1024@end example
1025
1026@subsection Audible AAX
1027
1028Audible AAX files are encrypted M4B files, and they can be decrypted by specifying a 4 byte activation secret.
1029@example
1030ffmpeg -activation_bytes 1CEB00DA -i test.aax -vn -c:a copy output.mp4
1031@end example
1032
1033@section mp3
1034
1035The MP3 muxer writes a raw MP3 stream with the following optional features:
1036@itemize @bullet
1037@item
1038An ID3v2 metadata header at the beginning (enabled by default). Versions 2.3 and
10392.4 are supported, the @code{id3v2_version} private option controls which one is
1040used (3 or 4). Setting @code{id3v2_version} to 0 disables the ID3v2 header
1041completely.
1042
1043The muxer supports writing attached pictures (APIC frames) to the ID3v2 header.
1044The pictures are supplied to the muxer in form of a video stream with a single
1045packet. There can be any number of those streams, each will correspond to a
1046single APIC frame. The stream metadata tags @var{title} and @var{comment} map
1047to APIC @var{description} and @var{picture type} respectively. See
1048@url{http://id3.org/id3v2.4.0-frames} for allowed picture types.
1049
1050Note that the APIC frames must be written at the beginning, so the muxer will
1051buffer the audio frames until it gets all the pictures. It is therefore advised
1052to provide the pictures as soon as possible to avoid excessive buffering.
1053
1054@item
1055A Xing/LAME frame right after the ID3v2 header (if present). It is enabled by
1056default, but will be written only if the output is seekable. The
1057@code{write_xing} private option can be used to disable it. The frame contains
1058various information that may be useful to the decoder, like the audio duration
1059or encoder delay.
1060
1061@item
1062A legacy ID3v1 tag at the end of the file (disabled by default). It may be
1063enabled with the @code{write_id3v1} private option, but as its capabilities are
1064very limited, its usage is not recommended.
1065@end itemize
1066
1067Examples:
1068
1069Write an mp3 with an ID3v2.3 header and an ID3v1 footer:
1070@example
1071ffmpeg -i INPUT -id3v2_version 3 -write_id3v1 1 out.mp3
1072@end example
1073
1074To attach a picture to an mp3 file select both the audio and the picture stream
1075with @code{map}:
1076@example
1077ffmpeg -i input.mp3 -i cover.png -c copy -map 0 -map 1
1078-metadata:s:v title="Album cover" -metadata:s:v comment="Cover (Front)" out.mp3
1079@end example
1080
1081Write a "clean" MP3 without any extra features:
1082@example
1083ffmpeg -i input.wav -write_xing 0 -id3v2_version 0 out.mp3
1084@end example
1085
1086@section mpegts
1087
1088MPEG transport stream muxer.
1089
1090This muxer implements ISO 13818-1 and part of ETSI EN 300 468.
1091
1092The recognized metadata settings in mpegts muxer are @code{service_provider}
1093and @code{service_name}. If they are not set the default for
1094@code{service_provider} is @samp{FFmpeg} and the default for
1095@code{service_name} is @samp{Service01}.
1096
1097@subsection Options
1098
1099The muxer options are:
1100
1101@table @option
1102@item mpegts_transport_stream_id @var{integer}
1103Set the @samp{transport_stream_id}. This identifies a transponder in DVB.
1104Default is @code{0x0001}.
1105
1106@item mpegts_original_network_id @var{integer}
1107Set the @samp{original_network_id}. This is unique identifier of a
1108network in DVB. Its main use is in the unique identification of a service
1109through the path @samp{Original_Network_ID, Transport_Stream_ID}. Default
1110is @code{0x0001}.
1111
1112@item mpegts_service_id @var{integer}
1113Set the @samp{service_id}, also known as program in DVB. Default is
1114@code{0x0001}.
1115
1116@item mpegts_service_type @var{integer}
1117Set the program @samp{service_type}. Default is @code{digital_tv}.
1118Accepts the following options:
1119@table @samp
1120@item hex_value
1121Any hexdecimal value between @code{0x01} to @code{0xff} as defined in
1122ETSI 300 468.
1123@item digital_tv
1124Digital TV service.
1125@item digital_radio
1126Digital Radio service.
1127@item teletext
1128Teletext service.
1129@item advanced_codec_digital_radio
1130Advanced Codec Digital Radio service.
1131@item mpeg2_digital_hdtv
1132MPEG2 Digital HDTV service.
1133@item advanced_codec_digital_sdtv
1134Advanced Codec Digital SDTV service.
1135@item advanced_codec_digital_hdtv
1136Advanced Codec Digital HDTV service.
1137@end table
1138
1139@item mpegts_pmt_start_pid @var{integer}
1140Set the first PID for PMT. Default is @code{0x1000}. Max is @code{0x1f00}.
1141
1142@item mpegts_start_pid @var{integer}
1143Set the first PID for data packets. Default is @code{0x0100}. Max is
1144@code{0x0f00}.
1145
1146@item mpegts_m2ts_mode @var{boolean}
1147Enable m2ts mode if set to @code{1}. Default value is @code{-1} which
1148disables m2ts mode.
1149
1150@item muxrate @var{integer}
1151Set a constant muxrate. Default is VBR.
1152
1153@item pes_payload_size @var{integer}
1154Set minimum PES packet payload in bytes. Default is @code{2930}.
1155
1156@item mpegts_flags @var{flags}
1157Set mpegts flags. Accepts the following options:
1158@table @samp
1159@item resend_headers
1160Reemit PAT/PMT before writing the next packet.
1161@item latm
1162Use LATM packetization for AAC.
1163@item pat_pmt_at_frames
1164Reemit PAT and PMT at each video frame.
1165@item system_b
1166Conform to System B (DVB) instead of System A (ATSC).
1167@item initial_discontinuity
1168Mark the initial packet of each stream as discontinuity.
1169@end table
1170
1171@item resend_headers @var{integer}
1172Reemit PAT/PMT before writing the next packet. This option is deprecated:
1173use @option{mpegts_flags} instead.
1174
1175@item mpegts_copyts @var{boolean}
1176Preserve original timestamps, if value is set to @code{1}. Default value
1177is @code{-1}, which results in shifting timestamps so that they start from 0.
1178
1179@item omit_video_pes_length @var{boolean}
1180Omit the PES packet length for video packets. Default is @code{1} (true).
1181
1182@item pcr_period @var{integer}
1183Override the default PCR retransmission time in milliseconds. Ignored if
1184variable muxrate is selected. Default is @code{20}.
1185
1186@item pat_period @var{double}
1187Maximum time in seconds between PAT/PMT tables.
1188
1189@item sdt_period @var{double}
1190Maximum time in seconds between SDT tables.
1191
1192@item tables_version @var{integer}
1193Set PAT, PMT and SDT version (default @code{0}, valid values are from 0 to 31, inclusively).
1194This option allows updating stream structure so that standard consumer may
1195detect the change. To do so, reopen output @code{AVFormatContext} (in case of API
1196usage) or restart @command{ffmpeg} instance, cyclically changing
1197@option{tables_version} value:
1198
1199@example
1200ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
1201ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
1202...
1203ffmpeg -i source3.ts -codec copy -f mpegts -tables_version 31 udp://1.1.1.1:1111
1204ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
1205ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
1206...
1207@end example
1208@end table
1209
1210@subsection Example
1211
1212@example
1213ffmpeg -i file.mpg -c copy \
1214 -mpegts_original_network_id 0x1122 \
1215 -mpegts_transport_stream_id 0x3344 \
1216 -mpegts_service_id 0x5566 \
1217 -mpegts_pmt_start_pid 0x1500 \
1218 -mpegts_start_pid 0x150 \
1219 -metadata service_provider="Some provider" \
1220 -metadata service_name="Some Channel" \
1221 out.ts
1222@end example
1223
1224@section mxf, mxf_d10
1225
1226MXF muxer.
1227
1228@subsection Options
1229
1230The muxer options are:
1231
1232@table @option
1233@item store_user_comments @var{bool}
1234Set if user comments should be stored if available or never.
1235IRT D-10 does not allow user comments. The default is thus to write them for
1236mxf but not for mxf_d10
1237@end table
1238
1239@section null
1240
1241Null muxer.
1242
1243This muxer does not generate any output file, it is mainly useful for
1244testing or benchmarking purposes.
1245
1246For example to benchmark decoding with @command{ffmpeg} you can use the
1247command:
1248@example
1249ffmpeg -benchmark -i INPUT -f null out.null
1250@end example
1251
1252Note that the above command does not read or write the @file{out.null}
1253file, but specifying the output file is required by the @command{ffmpeg}
1254syntax.
1255
1256Alternatively you can write the command as:
1257@example
1258ffmpeg -benchmark -i INPUT -f null -
1259@end example
1260
1261@section nut
1262
1263@table @option
1264@item -syncpoints @var{flags}
1265Change the syncpoint usage in nut:
1266@table @option
1267@item @var{default} use the normal low-overhead seeking aids.
1268@item @var{none} do not use the syncpoints at all, reducing the overhead but making the stream non-seekable;
1269 Use of this option is not recommended, as the resulting files are very damage
1270 sensitive and seeking is not possible. Also in general the overhead from
1271 syncpoints is negligible. Note, -@code{write_index} 0 can be used to disable
1272 all growing data tables, allowing to mux endless streams with limited memory
1273 and without these disadvantages.
1274@item @var{timestamped} extend the syncpoint with a wallclock field.
1275@end table
1276The @var{none} and @var{timestamped} flags are experimental.
1277@item -write_index @var{bool}
1278Write index at the end, the default is to write an index.
1279@end table
1280
1281@example
1282ffmpeg -i INPUT -f_strict experimental -syncpoints none - | processor
1283@end example
1284
1285@section ogg
1286
1287Ogg container muxer.
1288
1289@table @option
1290@item -page_duration @var{duration}
1291Preferred page duration, in microseconds. The muxer will attempt to create
1292pages that are approximately @var{duration} microseconds long. This allows the
1293user to compromise between seek granularity and container overhead. The default
1294is 1 second. A value of 0 will fill all segments, making pages as large as
1295possible. A value of 1 will effectively use 1 packet-per-page in most
1296situations, giving a small seek granularity at the cost of additional container
1297overhead.
1298@item -serial_offset @var{value}
1299Serial value from which to set the streams serial number.
1300Setting it to different and sufficiently large values ensures that the produced
1301ogg files can be safely chained.
1302
1303@end table
1304
1305@anchor{segment}
1306@section segment, stream_segment, ssegment
1307
1308Basic stream segmenter.
1309
1310This muxer outputs streams to a number of separate files of nearly
1311fixed duration. Output filename pattern can be set in a fashion
1312similar to @ref{image2}, or by using a @code{strftime} template if
1313the @option{strftime} option is enabled.
1314
1315@code{stream_segment} is a variant of the muxer used to write to
1316streaming output formats, i.e. which do not require global headers,
1317and is recommended for outputting e.g. to MPEG transport stream segments.
1318@code{ssegment} is a shorter alias for @code{stream_segment}.
1319
1320Every segment starts with a keyframe of the selected reference stream,
1321which is set through the @option{reference_stream} option.
1322
1323Note that if you want accurate splitting for a video file, you need to
1324make the input key frames correspond to the exact splitting times
1325expected by the segmenter, or the segment muxer will start the new
1326segment with the key frame found next after the specified start
1327time.
1328
1329The segment muxer works best with a single constant frame rate video.
1330
1331Optionally it can generate a list of the created segments, by setting
1332the option @var{segment_list}. The list type is specified by the
1333@var{segment_list_type} option. The entry filenames in the segment
1334list are set by default to the basename of the corresponding segment
1335files.
1336
1337See also the @ref{hls} muxer, which provides a more specific
1338implementation for HLS segmentation.
1339
1340@subsection Options
1341
1342The segment muxer supports the following options:
1343
1344@table @option
1345@item increment_tc @var{1|0}
1346if set to @code{1}, increment timecode between each segment
1347If this is selected, the input need to have
1348a timecode in the first video stream. Default value is
1349@code{0}.
1350
1351@item reference_stream @var{specifier}
1352Set the reference stream, as specified by the string @var{specifier}.
1353If @var{specifier} is set to @code{auto}, the reference is chosen
1354automatically. Otherwise it must be a stream specifier (see the ``Stream
1355specifiers'' chapter in the ffmpeg manual) which specifies the
1356reference stream. The default value is @code{auto}.
1357
1358@item segment_format @var{format}
1359Override the inner container format, by default it is guessed by the filename
1360extension.
1361
1362@item segment_format_options @var{options_list}
1363Set output format options using a :-separated list of key=value
1364parameters. Values containing the @code{:} special character must be
1365escaped.
1366
1367@item segment_list @var{name}
1368Generate also a listfile named @var{name}. If not specified no
1369listfile is generated.
1370
1371@item segment_list_flags @var{flags}
1372Set flags affecting the segment list generation.
1373
1374It currently supports the following flags:
1375@table @samp
1376@item cache
1377Allow caching (only affects M3U8 list files).
1378
1379@item live
1380Allow live-friendly file generation.
1381@end table
1382
1383@item segment_list_size @var{size}
1384Update the list file so that it contains at most @var{size}
1385segments. If 0 the list file will contain all the segments. Default
1386value is 0.
1387
1388@item segment_list_entry_prefix @var{prefix}
1389Prepend @var{prefix} to each entry. Useful to generate absolute paths.
1390By default no prefix is applied.
1391
1392@item segment_list_type @var{type}
1393Select the listing format.
1394
1395The following values are recognized:
1396@table @samp
1397@item flat
1398Generate a flat list for the created segments, one segment per line.
1399
1400@item csv, ext
1401Generate a list for the created segments, one segment per line,
1402each line matching the format (comma-separated values):
1403@example
1404@var{segment_filename},@var{segment_start_time},@var{segment_end_time}
1405@end example
1406
1407@var{segment_filename} is the name of the output file generated by the
1408muxer according to the provided pattern. CSV escaping (according to
1409RFC4180) is applied if required.
1410
1411@var{segment_start_time} and @var{segment_end_time} specify
1412the segment start and end time expressed in seconds.
1413
1414A list file with the suffix @code{".csv"} or @code{".ext"} will
1415auto-select this format.
1416
1417@samp{ext} is deprecated in favor or @samp{csv}.
1418
1419@item ffconcat
1420Generate an ffconcat file for the created segments. The resulting file
1421can be read using the FFmpeg @ref{concat} demuxer.
1422
1423A list file with the suffix @code{".ffcat"} or @code{".ffconcat"} will
1424auto-select this format.
1425
1426@item m3u8
1427Generate an extended M3U8 file, version 3, compliant with
1428@url{http://tools.ietf.org/id/draft-pantos-http-live-streaming}.
1429
1430A list file with the suffix @code{".m3u8"} will auto-select this format.
1431@end table
1432
1433If not specified the type is guessed from the list file name suffix.
1434
1435@item segment_time @var{time}
1436Set segment duration to @var{time}, the value must be a duration
1437specification. Default value is "2". See also the
1438@option{segment_times} option.
1439
1440Note that splitting may not be accurate, unless you force the
1441reference stream key-frames at the given time. See the introductory
1442notice and the examples below.
1443
1444@item segment_atclocktime @var{1|0}
1445If set to "1" split at regular clock time intervals starting from 00:00
1446o'clock. The @var{time} value specified in @option{segment_time} is
1447used for setting the length of the splitting interval.
1448
1449For example with @option{segment_time} set to "900" this makes it possible
1450to create files at 12:00 o'clock, 12:15, 12:30, etc.
1451
1452Default value is "0".
1453
1454@item segment_clocktime_offset @var{duration}
1455Delay the segment splitting times with the specified duration when using
1456@option{segment_atclocktime}.
1457
1458For example with @option{segment_time} set to "900" and
1459@option{segment_clocktime_offset} set to "300" this makes it possible to
1460create files at 12:05, 12:20, 12:35, etc.
1461
1462Default value is "0".
1463
1464@item segment_clocktime_wrap_duration @var{duration}
1465Force the segmenter to only start a new segment if a packet reaches the muxer
1466within the specified duration after the segmenting clock time. This way you
1467can make the segmenter more resilient to backward local time jumps, such as
1468leap seconds or transition to standard time from daylight savings time.
1469
1470Default is the maximum possible duration which means starting a new segment
1471regardless of the elapsed time since the last clock time.
1472
1473@item segment_time_delta @var{delta}
1474Specify the accuracy time when selecting the start time for a
1475segment, expressed as a duration specification. Default value is "0".
1476
1477When delta is specified a key-frame will start a new segment if its
1478PTS satisfies the relation:
1479@example
1480PTS >= start_time - time_delta
1481@end example
1482
1483This option is useful when splitting video content, which is always
1484split at GOP boundaries, in case a key frame is found just before the
1485specified split time.
1486
1487In particular may be used in combination with the @file{ffmpeg} option
1488@var{force_key_frames}. The key frame times specified by
1489@var{force_key_frames} may not be set accurately because of rounding
1490issues, with the consequence that a key frame time may result set just
1491before the specified time. For constant frame rate videos a value of
14921/(2*@var{frame_rate}) should address the worst case mismatch between
1493the specified time and the time set by @var{force_key_frames}.
1494
1495@item segment_times @var{times}
1496Specify a list of split points. @var{times} contains a list of comma
1497separated duration specifications, in increasing order. See also
1498the @option{segment_time} option.
1499
1500@item segment_frames @var{frames}
1501Specify a list of split video frame numbers. @var{frames} contains a
1502list of comma separated integer numbers, in increasing order.
1503
1504This option specifies to start a new segment whenever a reference
1505stream key frame is found and the sequential number (starting from 0)
1506of the frame is greater or equal to the next value in the list.
1507
1508@item segment_wrap @var{limit}
1509Wrap around segment index once it reaches @var{limit}.
1510
1511@item segment_start_number @var{number}
1512Set the sequence number of the first segment. Defaults to @code{0}.
1513
1514@item strftime @var{1|0}
1515Use the @code{strftime} function to define the name of the new
1516segments to write. If this is selected, the output segment name must
1517contain a @code{strftime} function template. Default value is
1518@code{0}.
1519
1520@item break_non_keyframes @var{1|0}
1521If enabled, allow segments to start on frames other than keyframes. This
1522improves behavior on some players when the time between keyframes is
1523inconsistent, but may make things worse on others, and can cause some oddities
1524during seeking. Defaults to @code{0}.
1525
1526@item reset_timestamps @var{1|0}
1527Reset timestamps at the begin of each segment, so that each segment
1528will start with near-zero timestamps. It is meant to ease the playback
1529of the generated segments. May not work with some combinations of
1530muxers/codecs. It is set to @code{0} by default.
1531
1532@item initial_offset @var{offset}
1533Specify timestamp offset to apply to the output packet timestamps. The
1534argument must be a time duration specification, and defaults to 0.
1535
1536@item write_empty_segments @var{1|0}
1537If enabled, write an empty segment if there are no packets during the period a
1538segment would usually span. Otherwise, the segment will be filled with the next
1539packet written. Defaults to @code{0}.
1540@end table
1541
1542@subsection Examples
1543
1544@itemize
1545@item
1546Remux the content of file @file{in.mkv} to a list of segments
1547@file{out-000.nut}, @file{out-001.nut}, etc., and write the list of
1548generated segments to @file{out.list}:
1549@example
1550ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.list out%03d.nut
1551@end example
1552
1553@item
1554Segment input and set output format options for the output segments:
1555@example
1556ffmpeg -i in.mkv -f segment -segment_time 10 -segment_format_options movflags=+faststart out%03d.mp4
1557@end example
1558
1559@item
1560Segment the input file according to the split points specified by the
1561@var{segment_times} option:
1562@example
1563ffmpeg -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
1564@end example
1565
1566@item
1567Use the @command{ffmpeg} @option{force_key_frames}
1568option to force key frames in the input at the specified location, together
1569with the segment option @option{segment_time_delta} to account for
1570possible roundings operated when setting key frame times.
1571@example
1572ffmpeg -i in.mkv -force_key_frames 1,2,3,5,8,13,21 -codec:v mpeg4 -codec:a pcm_s16le -map 0 \
1573-f segment -segment_list out.csv -segment_times 1,2,3,5,8,13,21 -segment_time_delta 0.05 out%03d.nut
1574@end example
1575In order to force key frames on the input file, transcoding is
1576required.
1577
1578@item
1579Segment the input file by splitting the input file according to the
1580frame numbers sequence specified with the @option{segment_frames} option:
1581@example
1582ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.csv -segment_frames 100,200,300,500,800 out%03d.nut
1583@end example
1584
1585@item
1586Convert the @file{in.mkv} to TS segments using the @code{libx264}
1587and @code{aac} encoders:
1588@example
1589ffmpeg -i in.mkv -map 0 -codec:v libx264 -codec:a aac -f ssegment -segment_list out.list out%03d.ts
1590@end example
1591
1592@item
1593Segment the input file, and create an M3U8 live playlist (can be used
1594as live HLS source):
1595@example
1596ffmpeg -re -i in.mkv -codec copy -map 0 -f segment -segment_list playlist.m3u8 \
1597-segment_list_flags +live -segment_time 10 out%03d.mkv
1598@end example
1599@end itemize
1600
1601@section smoothstreaming
1602
1603Smooth Streaming muxer generates a set of files (Manifest, chunks) suitable for serving with conventional web server.
1604
1605@table @option
1606@item window_size
1607Specify the number of fragments kept in the manifest. Default 0 (keep all).
1608
1609@item extra_window_size
1610Specify the number of fragments kept outside of the manifest before removing from disk. Default 5.
1611
1612@item lookahead_count
1613Specify the number of lookahead fragments. Default 2.
1614
1615@item min_frag_duration
1616Specify the minimum fragment duration (in microseconds). Default 5000000.
1617
1618@item remove_at_exit
1619Specify whether to remove all fragments when finished. Default 0 (do not remove).
1620
1621@end table
1622
1623@anchor{fifo}
1624@section fifo
1625
1626The fifo pseudo-muxer allows the separation of encoding and muxing by using
1627first-in-first-out queue and running the actual muxer in a separate thread. This
1628is especially useful in combination with the @ref{tee} muxer and can be used to
1629send data to several destinations with different reliability/writing speed/latency.
1630
1631API users should be aware that callback functions (interrupt_callback,
1632io_open and io_close) used within its AVFormatContext must be thread-safe.
1633
1634The behavior of the fifo muxer if the queue fills up or if the output fails is
1635selectable,
1636
1637@itemize @bullet
1638
1639@item
1640output can be transparently restarted with configurable delay between retries
1641based on real time or time of the processed stream.
1642
1643@item
1644encoding can be blocked during temporary failure, or continue transparently
1645dropping packets in case fifo queue fills up.
1646
1647@end itemize
1648
1649@table @option
1650
1651@item fifo_format
1652Specify the format name. Useful if it cannot be guessed from the
1653output name suffix.
1654
1655@item queue_size
1656Specify size of the queue (number of packets). Default value is 60.
1657
1658@item format_opts
1659Specify format options for the underlying muxer. Muxer options can be specified
1660as a list of @var{key}=@var{value} pairs separated by ':'.
1661
1662@item drop_pkts_on_overflow @var{bool}
1663If set to 1 (true), in case the fifo queue fills up, packets will be dropped
1664rather than blocking the encoder. This makes it possible to continue streaming without
1665delaying the input, at the cost of omitting part of the stream. By default
1666this option is set to 0 (false), so in such cases the encoder will be blocked
1667until the muxer processes some of the packets and none of them is lost.
1668
1669@item attempt_recovery @var{bool}
1670If failure occurs, attempt to recover the output. This is especially useful
1671when used with network output, since it makes it possible to restart streaming transparently.
1672By default this option is set to 0 (false).
1673
1674@item max_recovery_attempts
1675Sets maximum number of successive unsuccessful recovery attempts after which
1676the output fails permanently. By default this option is set to 0 (unlimited).
1677
1678@item recovery_wait_time @var{duration}
1679Waiting time before the next recovery attempt after previous unsuccessful
1680recovery attempt. Default value is 5 seconds.
1681
1682@item recovery_wait_streamtime @var{bool}
1683If set to 0 (false), the real time is used when waiting for the recovery
1684attempt (i.e. the recovery will be attempted after at least
1685recovery_wait_time seconds).
1686If set to 1 (true), the time of the processed stream is taken into account
1687instead (i.e. the recovery will be attempted after at least @var{recovery_wait_time}
1688seconds of the stream is omitted).
1689By default, this option is set to 0 (false).
1690
1691@item recover_any_error @var{bool}
1692If set to 1 (true), recovery will be attempted regardless of type of the error
1693causing the failure. By default this option is set to 0 (false) and in case of
1694certain (usually permanent) errors the recovery is not attempted even when
1695@var{attempt_recovery} is set to 1.
1696
1697@item restart_with_keyframe @var{bool}
1698Specify whether to wait for the keyframe after recovering from
1699queue overflow or failure. This option is set to 0 (false) by default.
1700
1701@end table
1702
1703@subsection Examples
1704
1705@itemize
1706
1707@item
1708Stream something to rtmp server, continue processing the stream at real-time
1709rate even in case of temporary failure (network outage) and attempt to recover
1710streaming every second indefinitely.
1711@example
1712ffmpeg -re -i ... -c:v libx264 -c:a aac -f fifo -fifo_format flv -map 0:v -map 0:a
1713 -drop_pkts_on_overflow 1 -attempt_recovery 1 -recovery_wait_time 1 rtmp://example.com/live/stream_name
1714@end example
1715
1716@end itemize
1717
1718@anchor{tee}
1719@section tee
1720
1721The tee muxer can be used to write the same data to several files or any
1722other kind of muxer. It can be used, for example, to both stream a video to
1723the network and save it to disk at the same time.
1724
1725It is different from specifying several outputs to the @command{ffmpeg}
1726command-line tool because the audio and video data will be encoded only once
1727with the tee muxer; encoding can be a very expensive process. It is not
1728useful when using the libavformat API directly because it is then possible
1729to feed the same packets to several muxers directly.
1730
1731@table @option
1732
1733@item use_fifo @var{bool}
1734If set to 1, slave outputs will be processed in separate thread using @ref{fifo}
1735muxer. This allows to compensate for different speed/latency/reliability of
1736outputs and setup transparent recovery. By default this feature is turned off.
1737
1738@item fifo_options
1739Options to pass to fifo pseudo-muxer instances. See @ref{fifo}.
1740
1741@end table
1742
1743The slave outputs are specified in the file name given to the muxer,
1744separated by '|'. If any of the slave name contains the '|' separator,
1745leading or trailing spaces or any special character, it must be
1746escaped (see @ref{quoting_and_escaping,,the "Quoting and escaping"
1747section in the ffmpeg-utils(1) manual,ffmpeg-utils}).
1748
1749Muxer options can be specified for each slave by prepending them as a list of
1750@var{key}=@var{value} pairs separated by ':', between square brackets. If
1751the options values contain a special character or the ':' separator, they
1752must be escaped; note that this is a second level escaping.
1753
1754The following special options are also recognized:
1755@table @option
1756@item f
1757Specify the format name. Useful if it cannot be guessed from the
1758output name suffix.
1759
1760@item bsfs[/@var{spec}]
1761Specify a list of bitstream filters to apply to the specified
1762output.
1763
1764@item use_fifo @var{bool}
1765This allows to override tee muxer use_fifo option for individual slave muxer.
1766
1767@item fifo_options
1768This allows to override tee muxer fifo_options for individual slave muxer.
1769See @ref{fifo}.
1770
1771It is possible to specify to which streams a given bitstream filter
1772applies, by appending a stream specifier to the option separated by
1773@code{/}. @var{spec} must be a stream specifier (see @ref{Format
1774stream specifiers}). If the stream specifier is not specified, the
1775bitstream filters will be applied to all streams in the output.
1776
1777Several bitstream filters can be specified, separated by ",".
1778
1779@item select
1780Select the streams that should be mapped to the slave output,
1781specified by a stream specifier. If not specified, this defaults to
1782all the input streams. You may use multiple stream specifiers
1783separated by commas (@code{,}) e.g.: @code{a:0,v}
1784
1785@item onfail
1786Specify behaviour on output failure. This can be set to either @code{abort} (which is
1787default) or @code{ignore}. @code{abort} will cause whole process to fail in case of failure
1788on this slave output. @code{ignore} will ignore failure on this output, so other outputs
1789will continue without being affected.
1790@end table
1791
1792@subsection Examples
1793
1794@itemize
1795@item
1796Encode something and both archive it in a WebM file and stream it
1797as MPEG-TS over UDP (the streams need to be explicitly mapped):
1798@example
1799ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a
1800 "archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/"
1801@end example
1802
1803@item
1804As above, but continue streaming even if output to local file fails
1805(for example local drive fills up):
1806@example
1807ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a
1808 "[onfail=ignore]archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/"
1809@end example
1810
1811@item
1812Use @command{ffmpeg} to encode the input, and send the output
1813to three different destinations. The @code{dump_extra} bitstream
1814filter is used to add extradata information to all the output video
1815keyframes packets, as requested by the MPEG-TS format. The select
1816option is applied to @file{out.aac} in order to make it contain only
1817audio packets.
1818@example
1819ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac
1820 -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=a]out.aac"
1821@end example
1822
1823@item
1824As below, but select only stream @code{a:1} for the audio output. Note
1825that a second level escaping must be performed, as ":" is a special
1826character used to separate options.
1827@example
1828ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac
1829 -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=\'a:1\']out.aac"
1830@end example
1831@end itemize
1832
1833Note: some codecs may need different options depending on the output format;
1834the auto-detection of this can not work with the tee muxer. The main example
1835is the @option{global_header} flag.
1836
1837@section webm_dash_manifest
1838
1839WebM DASH Manifest muxer.
1840
1841This muxer implements the WebM DASH Manifest specification to generate the DASH
1842manifest XML. It also supports manifest generation for DASH live streams.
1843
1844For more information see:
1845
1846@itemize @bullet
1847@item
1848WebM DASH Specification: @url{https://sites.google.com/a/webmproject.org/wiki/adaptive-streaming/webm-dash-specification}
1849@item
1850ISO DASH Specification: @url{http://standards.iso.org/ittf/PubliclyAvailableStandards/c065274_ISO_IEC_23009-1_2014.zip}
1851@end itemize
1852
1853@subsection Options
1854
1855This muxer supports the following options:
1856
1857@table @option
1858@item adaptation_sets
1859This option has the following syntax: "id=x,streams=a,b,c id=y,streams=d,e" where x and y are the
1860unique identifiers of the adaptation sets and a,b,c,d and e are the indices of the corresponding
1861audio and video streams. Any number of adaptation sets can be added using this option.
1862
1863@item live
1864Set this to 1 to create a live stream DASH Manifest. Default: 0.
1865
1866@item chunk_start_index
1867Start index of the first chunk. This will go in the @samp{startNumber} attribute
1868of the @samp{SegmentTemplate} element in the manifest. Default: 0.
1869
1870@item chunk_duration_ms
1871Duration of each chunk in milliseconds. This will go in the @samp{duration}
1872attribute of the @samp{SegmentTemplate} element in the manifest. Default: 1000.
1873
1874@item utc_timing_url
1875URL of the page that will return the UTC timestamp in ISO format. This will go
1876in the @samp{value} attribute of the @samp{UTCTiming} element in the manifest.
1877Default: None.
1878
1879@item time_shift_buffer_depth
1880Smallest time (in seconds) shifting buffer for which any Representation is
1881guaranteed to be available. This will go in the @samp{timeShiftBufferDepth}
1882attribute of the @samp{MPD} element. Default: 60.
1883
1884@item minimum_update_period
1885Minimum update period (in seconds) of the manifest. This will go in the
1886@samp{minimumUpdatePeriod} attribute of the @samp{MPD} element. Default: 0.
1887
1888@end table
1889
1890@subsection Example
1891@example
1892ffmpeg -f webm_dash_manifest -i video1.webm \
1893 -f webm_dash_manifest -i video2.webm \
1894 -f webm_dash_manifest -i audio1.webm \
1895 -f webm_dash_manifest -i audio2.webm \
1896 -map 0 -map 1 -map 2 -map 3 \
1897 -c copy \
1898 -f webm_dash_manifest \
1899 -adaptation_sets "id=0,streams=0,1 id=1,streams=2,3" \
1900 manifest.xml
1901@end example
1902
1903@section webm_chunk
1904
1905WebM Live Chunk Muxer.
1906
1907This muxer writes out WebM headers and chunks as separate files which can be
1908consumed by clients that support WebM Live streams via DASH.
1909
1910@subsection Options
1911
1912This muxer supports the following options:
1913
1914@table @option
1915@item chunk_start_index
1916Index of the first chunk (defaults to 0).
1917
1918@item header
1919Filename of the header where the initialization data will be written.
1920
1921@item audio_chunk_duration
1922Duration of each audio chunk in milliseconds (defaults to 5000).
1923@end table
1924
1925@subsection Example
1926@example
1927ffmpeg -f v4l2 -i /dev/video0 \
1928 -f alsa -i hw:0 \
1929 -map 0:0 \
1930 -c:v libvpx-vp9 \
1931 -s 640x360 -keyint_min 30 -g 30 \
1932 -f webm_chunk \
1933 -header webm_live_video_360.hdr \
1934 -chunk_start_index 1 \
1935 webm_live_video_360_%d.chk \
1936 -map 1:0 \
1937 -c:a libvorbis \
1938 -b:a 128k \
1939 -f webm_chunk \
1940 -header webm_live_audio_128.hdr \
1941 -chunk_start_index 1 \
1942 -audio_chunk_duration 1000 \
1943 webm_live_audio_128_%d.chk
1944@end example
1945
1946@c man end MUXERS
1947