4 Muxers are configured elements in FFmpeg which allow writing
5 multimedia streams to a particular type of file.
7 When you configure your FFmpeg build, all the supported muxers
8 are enabled by default. You can list all available muxers using the
9 configure option @code{--list-muxers}.
11 You can disable all the muxers with the configure option
12 @code{--disable-muxers} and selectively enable / disable single muxers
13 with the options @code{--enable-muxer=@var{MUXER}} /
14 @code{--disable-muxer=@var{MUXER}}.
16 The option @code{-formats} of the ff* tools will display the list of
19 A description of some of the currently available muxers follows.
24 Audio Interchange File Format muxer.
28 It accepts the following options:
32 Enable ID3v2 tags writing when set to 1. Default is 0 (disabled).
35 Select ID3v2 version to write. Currently only version 3 and 4 (aka.
36 ID3v2.3 and ID3v2.4) are supported. The default is version 4.
43 Advanced Systems Format muxer.
45 Note that Windows Media Audio (wma) and Windows Media Video (wmv) use this
50 It accepts the following options:
54 Set the muxer packet size. By tuning this setting you may reduce data
55 fragmentation or muxer overhead depending on your source. Default value is
56 3200, minimum is 100, maximum is 64k.
63 Chromaprint fingerprinter
65 This muxer feeds audio data to the Chromaprint library, which generates
66 a fingerprint for the provided audio data. It takes a single signed
67 native-endian 16-bit raw audio stream.
72 @item silence_threshold
73 Threshold for detecting silence, ranges from 0 to 32767. -1 for default
74 (required for use with the AcoustID service).
77 Algorithm index to fingerprint with.
80 Format to output the fingerprint as. Accepts the following options:
83 Binary raw fingerprint
86 Binary compressed fingerprint
89 Base64 compressed fingerprint
98 CRC (Cyclic Redundancy Check) testing format.
100 This muxer computes and prints the Adler-32 CRC of all the input audio
101 and video frames. By default audio frames are converted to signed
102 16-bit raw audio and video frames to raw video before computing the
105 The output of the muxer consists of a single line of the form:
106 CRC=0x@var{CRC}, where @var{CRC} is a hexadecimal number 0-padded to
107 8 digits containing the CRC for all the decoded input frames.
109 See also the @ref{framecrc} muxer.
113 For example to compute the CRC of the input, and store it in the file
116 ffmpeg -i INPUT -f crc out.crc
119 You can print the CRC to stdout with the command:
121 ffmpeg -i INPUT -f crc -
124 You can select the output format of each frame with @command{ffmpeg} by
125 specifying the audio and video codec and format. For example to
126 compute the CRC of the input audio converted to PCM unsigned 8-bit
127 and the input video converted to MPEG-2 video, use the command:
129 ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f crc -
134 Adobe Flash Video Format muxer.
136 This muxer accepts the following options:
140 @item flvflags @var{flags}
145 @item aac_seq_header_detect
146 Place AAC sequence header based on audio stream data.
148 @item no_sequence_end
149 Disable sequence end tag.
152 Disable metadata tag.
154 @item no_duration_filesize
155 Disable duration and filesize in metadata when they are equal to zero
156 at the end of stream. (Be used to non-seekable living stream).
158 @item add_keyframe_index
159 Used to facilitate seeking; particularly for HTTP pseudo streaming.
166 Per-packet CRC (Cyclic Redundancy Check) testing format.
168 This muxer computes and prints the Adler-32 CRC for each audio
169 and video packet. By default audio frames are converted to signed
170 16-bit raw audio and video frames to raw video before computing the
173 The output of the muxer consists of a line for each audio and video
176 @var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, 0x@var{CRC}
179 @var{CRC} is a hexadecimal number 0-padded to 8 digits containing the
184 For example to compute the CRC of the audio and video frames in
185 @file{INPUT}, converted to raw audio and video packets, and store it
186 in the file @file{out.crc}:
188 ffmpeg -i INPUT -f framecrc out.crc
191 To print the information to stdout, use the command:
193 ffmpeg -i INPUT -f framecrc -
196 With @command{ffmpeg}, you can select the output format to which the
197 audio and video frames are encoded before computing the CRC for each
198 packet by specifying the audio and video codec. For example, to
199 compute the CRC of each decoded input audio frame converted to PCM
200 unsigned 8-bit and of each decoded input video frame converted to
201 MPEG-2 video, use the command:
203 ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f framecrc -
206 See also the @ref{crc} muxer.
211 Per-packet hash testing format.
213 This muxer computes and prints a cryptographic hash for each audio
214 and video packet. This can be used for packet-by-packet equality
215 checks without having to individually do a binary comparison on each.
217 By default audio frames are converted to signed 16-bit raw audio and
218 video frames to raw video before computing the hash, but the output
219 of explicit conversions to other codecs can also be used. It uses the
220 SHA-256 cryptographic hash function by default, but supports several
223 The output of the muxer consists of a line for each audio and video
226 @var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, @var{hash}
229 @var{hash} is a hexadecimal number representing the computed hash
233 @item hash @var{algorithm}
234 Use the cryptographic hash function specified by the string @var{algorithm}.
235 Supported values include @code{MD5}, @code{murmur3}, @code{RIPEMD128},
236 @code{RIPEMD160}, @code{RIPEMD256}, @code{RIPEMD320}, @code{SHA160},
237 @code{SHA224}, @code{SHA256} (default), @code{SHA512/224}, @code{SHA512/256},
238 @code{SHA384}, @code{SHA512}, @code{CRC32} and @code{adler32}.
244 To compute the SHA-256 hash of the audio and video frames in @file{INPUT},
245 converted to raw audio and video packets, and store it in the file
248 ffmpeg -i INPUT -f framehash out.sha256
251 To print the information to stdout, using the MD5 hash function, use
254 ffmpeg -i INPUT -f framehash -hash md5 -
257 See also the @ref{hash} muxer.
262 Per-packet MD5 testing format.
264 This is a variant of the @ref{framehash} muxer. Unlike that muxer,
265 it defaults to using the MD5 hash function.
269 To compute the MD5 hash of the audio and video frames in @file{INPUT},
270 converted to raw audio and video packets, and store it in the file
273 ffmpeg -i INPUT -f framemd5 out.md5
276 To print the information to stdout, use the command:
278 ffmpeg -i INPUT -f framemd5 -
281 See also the @ref{framehash} and @ref{md5} muxers.
288 It accepts the following options:
292 Set the number of times to loop the output. Use @code{-1} for no loop, @code{0}
293 for looping indefinitely (default).
296 Force the delay (expressed in centiseconds) after the last frame. Each frame
297 ends with a delay until the next frame. The default is @code{-1}, which is a
298 special value to tell the muxer to re-use the previous delay. In case of a
299 loop, you might want to customize this value to mark a pause for instance.
302 For example, to encode a gif looping 10 times, with a 5 seconds delay between
305 ffmpeg -i INPUT -loop 10 -final_delay 500 out.gif
308 Note 1: if you wish to extract the frames into separate GIF files, you need to
309 force the @ref{image2} muxer:
311 ffmpeg -i INPUT -c:v gif -f image2 "out%d.gif"
314 Note 2: the GIF format has a very large time base: the delay between two frames
315 can therefore not be smaller than one centi second.
322 This muxer computes and prints a cryptographic hash of all the input
323 audio and video frames. This can be used for equality checks without
324 having to do a complete binary comparison.
326 By default audio frames are converted to signed 16-bit raw audio and
327 video frames to raw video before computing the hash, but the output
328 of explicit conversions to other codecs can also be used. Timestamps
329 are ignored. It uses the SHA-256 cryptographic hash function by default,
330 but supports several other algorithms.
332 The output of the muxer consists of a single line of the form:
333 @var{algo}=@var{hash}, where @var{algo} is a short string representing
334 the hash function used, and @var{hash} is a hexadecimal number
335 representing the computed hash.
338 @item hash @var{algorithm}
339 Use the cryptographic hash function specified by the string @var{algorithm}.
340 Supported values include @code{MD5}, @code{murmur3}, @code{RIPEMD128},
341 @code{RIPEMD160}, @code{RIPEMD256}, @code{RIPEMD320}, @code{SHA160},
342 @code{SHA224}, @code{SHA256} (default), @code{SHA512/224}, @code{SHA512/256},
343 @code{SHA384}, @code{SHA512}, @code{CRC32} and @code{adler32}.
349 To compute the SHA-256 hash of the input converted to raw audio and
350 video, and store it in the file @file{out.sha256}:
352 ffmpeg -i INPUT -f hash out.sha256
355 To print an MD5 hash to stdout use the command:
357 ffmpeg -i INPUT -f hash -hash md5 -
360 See also the @ref{framehash} muxer.
365 Apple HTTP Live Streaming muxer that segments MPEG-TS according to
366 the HTTP Live Streaming (HLS) specification.
368 It creates a playlist file, and one or more segment files. The output filename
369 specifies the playlist filename.
371 By default, the muxer creates a file for each segment produced. These files
372 have the same name as the playlist, followed by a sequential number and a
375 For example, to convert an input file with @command{ffmpeg}:
377 ffmpeg -i in.nut out.m3u8
379 This example will produce the playlist, @file{out.m3u8}, and segment files:
380 @file{out0.ts}, @file{out1.ts}, @file{out2.ts}, etc.
382 See also the @ref{segment} muxer, which provides a more generic and
383 flexible implementation of a segmenter, and can be used to perform HLS
388 This muxer supports the following options:
391 @item hls_init_time @var{seconds}
392 Set the initial target segment length in seconds. Default value is @var{0}.
393 Segment will be cut on the next key frame after this time has passed on the first m3u8 list.
394 After the initial playlist is filled @command{ffmpeg} will cut segments
395 at duration equal to @code{hls_time}
397 @item hls_time @var{seconds}
398 Set the target segment length in seconds. Default value is 2.
399 Segment will be cut on the next key frame after this time has passed.
401 @item hls_list_size @var{size}
402 Set the maximum number of playlist entries. If set to 0 the list file
403 will contain all the segments. Default value is 5.
405 @item hls_ts_options @var{options_list}
406 Set output format options using a :-separated list of key=value
407 parameters. Values containing @code{:} special characters must be
410 @item hls_wrap @var{wrap}
411 Set the number after which the segment filename number (the number
412 specified in each segment file) wraps. If set to 0 the number will be
413 never wrapped. Default value is 0.
415 This option is useful to avoid to fill the disk with many segment
416 files, and limits the maximum number of segment files written to disk
419 @item start_number @var{number}
420 Start the playlist sequence number from @var{number}. Default value is
423 @item hls_allow_cache @var{allowcache}
424 Explicitly set whether the client MAY (1) or MUST NOT (0) cache media segments.
426 @item hls_base_url @var{baseurl}
427 Append @var{baseurl} to every entry in the playlist.
428 Useful to generate playlists with absolute paths.
430 Note that the playlist sequence number must be unique for each segment
431 and it is not to be confused with the segment filename sequence number
432 which can be cyclic, for example if the @option{wrap} option is
435 @item hls_segment_filename @var{filename}
436 Set the segment filename. Unless @code{hls_flags single_file} is set,
437 @var{filename} is used as a string format with the segment number:
439 ffmpeg -i in.nut -hls_segment_filename 'file%03d.ts' out.m3u8
441 This example will produce the playlist, @file{out.m3u8}, and segment files:
442 @file{file000.ts}, @file{file001.ts}, @file{file002.ts}, etc.
445 Use strftime on @var{filename} to expand the segment filename with localtime.
446 The segment number (%d) is not available in this mode.
448 ffmpeg -i in.nut -use_localtime 1 -hls_segment_filename 'file-%Y%m%d-%s.ts' out.m3u8
450 This example will produce the playlist, @file{out.m3u8}, and segment files:
451 @file{file-20160215-1455569023.ts}, @file{file-20160215-1455569024.ts}, etc.
453 @item use_localtime_mkdir
454 Used together with -use_localtime, it will create up to one subdirectory which
455 is expanded in @var{filename}.
457 ffmpeg -i in.nut -use_localtime 1 -use_localtime_mkdir 1 -hls_segment_filename '%Y%m%d/file-%Y%m%d-%s.ts' out.m3u8
459 This example will create a directory 201560215 (if it does not exist), and then
460 produce the playlist, @file{out.m3u8}, and segment files:
461 @file{201560215/file-20160215-1455569023.ts}, @file{201560215/file-20160215-1455569024.ts}, etc.
464 @item hls_key_info_file @var{key_info_file}
465 Use the information in @var{key_info_file} for segment encryption. The first
466 line of @var{key_info_file} specifies the key URI written to the playlist. The
467 key URL is used to access the encryption key during playback. The second line
468 specifies the path to the key file used to obtain the key during the encryption
469 process. The key file is read as a single packed array of 16 octets in binary
470 format. The optional third line specifies the initialization vector (IV) as a
471 hexadecimal string to be used instead of the segment sequence number (default)
472 for encryption. Changes to @var{key_info_file} will result in segment
473 encryption with the new key/IV and an entry in the playlist for the new key
476 Key info file format:
485 http://server/file.key
490 Example key file paths:
498 0123456789ABCDEF0123456789ABCDEF
501 Key info file example:
503 http://server/file.key
505 0123456789ABCDEF0123456789ABCDEF
508 Example shell script:
512 openssl rand 16 > file.key
513 echo $BASE_URL/file.key > file.keyinfo
514 echo file.key >> file.keyinfo
515 echo $(openssl rand -hex 16) >> file.keyinfo
516 ffmpeg -f lavfi -re -i testsrc -c:v h264 -hls_flags delete_segments \
517 -hls_key_info_file file.keyinfo out.m3u8
520 @item hls_flags single_file
521 If this flag is set, the muxer will store all segments in a single MPEG-TS
522 file, and will use byte ranges in the playlist. HLS playlists generated with
523 this way will have the version number 4.
526 ffmpeg -i in.nut -hls_flags single_file out.m3u8
528 Will produce the playlist, @file{out.m3u8}, and a single segment file,
531 @item hls_flags delete_segments
532 Segment files removed from the playlist are deleted after a period of time
533 equal to the duration of the segment plus the duration of the playlist.
535 @item hls_flags append_list
536 Append new segments into the end of old segment list,
537 and remove the @code{#EXT-X-ENDLIST} from the old segment list.
539 @item hls_flags round_durations
540 Round the duration info in the playlist file segment info to integer
541 values, instead of using floating point.
543 @item hls_flags discont_starts
544 Add the @code{#EXT-X-DISCONTINUITY} tag to the playlist, before the
545 first segment's information.
547 @item hls_flags omit_endlist
548 Do not append the @code{EXT-X-ENDLIST} tag at the end of the playlist.
550 @item hls_flags split_by_time
551 Allow segments to start on frames other than keyframes. This improves
552 behavior on some players when the time between keyframes is inconsistent,
553 but may make things worse on others, and can cause some oddities during
554 seeking. This flag should be used with the @code{hls_time} option.
556 @item hls_flags program_date_time
557 Generate @code{EXT-X-PROGRAM-DATE-TIME} tags.
559 @item hls_playlist_type event
560 Emit @code{#EXT-X-PLAYLIST-TYPE:EVENT} in the m3u8 header. Forces
561 @option{hls_list_size} to 0; the playlist can only be appended to.
563 @item hls_playlist_type vod
564 Emit @code{#EXT-X-PLAYLIST-TYPE:VOD} in the m3u8 header. Forces
565 @option{hls_list_size} to 0; the playlist must not change.
568 Use the given HTTP method to create the hls files.
570 ffmpeg -re -i in.ts -f hls -method PUT http://example.com/live/out.m3u8
572 This example will upload all the mpegts segment files to the HTTP
573 server using the HTTP PUT method, and update the m3u8 files every
574 @code{refresh} times using the same method.
575 Note that the HTTP server must support the given method for uploading
584 Microsoft's icon file format (ICO) has some strict limitations that should be noted:
588 Size cannot exceed 256 pixels in any dimension
591 Only BMP and PNG images can be stored
594 If a BMP image is used, it must be one of the following pixel formats:
596 BMP Bit Depth FFmpeg Pixel Format
606 If a BMP image is used, it must use the BITMAPINFOHEADER DIB header
609 If a PNG image is used, it must use the rgba pixel format
617 The image file muxer writes video frames to image files.
619 The output filenames are specified by a pattern, which can be used to
620 produce sequentially numbered series of files.
621 The pattern may contain the string "%d" or "%0@var{N}d", this string
622 specifies the position of the characters representing a numbering in
623 the filenames. If the form "%0@var{N}d" is used, the string
624 representing the number in each filename is 0-padded to @var{N}
625 digits. The literal character '%' can be specified in the pattern with
628 If the pattern contains "%d" or "%0@var{N}d", the first filename of
629 the file list specified will contain the number 1, all the following
630 numbers will be sequential.
632 The pattern may contain a suffix which is used to automatically
633 determine the format of the image files to write.
635 For example the pattern "img-%03d.bmp" will specify a sequence of
636 filenames of the form @file{img-001.bmp}, @file{img-002.bmp}, ...,
637 @file{img-010.bmp}, etc.
638 The pattern "img%%-%d.jpg" will specify a sequence of filenames of the
639 form @file{img%-1.jpg}, @file{img%-2.jpg}, ..., @file{img%-10.jpg},
644 The following example shows how to use @command{ffmpeg} for creating a
645 sequence of files @file{img-001.jpeg}, @file{img-002.jpeg}, ...,
646 taking one image every second from the input video:
648 ffmpeg -i in.avi -vsync cfr -r 1 -f image2 'img-%03d.jpeg'
651 Note that with @command{ffmpeg}, if the format is not specified with the
652 @code{-f} option and the output filename specifies an image file
653 format, the image2 muxer is automatically selected, so the previous
654 command can be written as:
656 ffmpeg -i in.avi -vsync cfr -r 1 'img-%03d.jpeg'
659 Note also that the pattern must not necessarily contain "%d" or
660 "%0@var{N}d", for example to create a single image file
661 @file{img.jpeg} from the start of the input video you can employ the command:
663 ffmpeg -i in.avi -f image2 -frames:v 1 img.jpeg
666 The @option{strftime} option allows you to expand the filename with
667 date and time information. Check the documentation of
668 the @code{strftime()} function for the syntax.
670 For example to generate image files from the @code{strftime()}
671 "%Y-%m-%d_%H-%M-%S" pattern, the following @command{ffmpeg} command
674 ffmpeg -f v4l2 -r 1 -i /dev/video0 -f image2 -strftime 1 "%Y-%m-%d_%H-%M-%S.jpg"
681 Start the sequence from the specified number. Default value is 0.
684 If set to 1, the filename will always be interpreted as just a
685 filename, not a pattern, and the corresponding file will be continuously
686 overwritten with new images. Default value is 0.
689 If set to 1, expand the filename with date and time information from
690 @code{strftime()}. Default value is 0.
693 The image muxer supports the .Y.U.V image file format. This format is
694 special in that that each image frame consists of three files, for
695 each of the YUV420P components. To read or write this image file format,
696 specify the name of the '.Y' file. The muxer will automatically open the
697 '.U' and '.V' files as required.
701 Matroska container muxer.
703 This muxer implements the matroska and webm container specs.
707 The recognized metadata settings in this muxer are:
711 Set title name provided to a single track.
714 Specify the language of the track in the Matroska languages form.
716 The language can be either the 3 letters bibliographic ISO-639-2 (ISO
717 639-2/B) form (like "fre" for French), or a language code mixed with a
718 country code for specialities in languages (like "fre-ca" for Canadian
722 Set stereo 3D video layout of two views in a single video track.
724 The following values are recognized:
729 Both views are arranged side by side, Left-eye view is on the left
731 Both views are arranged in top-bottom orientation, Left-eye view is at bottom
733 Both views are arranged in top-bottom orientation, Left-eye view is on top
734 @item checkerboard_rl
735 Each view is arranged in a checkerboard interleaved pattern, Left-eye view being first
736 @item checkerboard_lr
737 Each view is arranged in a checkerboard interleaved pattern, Right-eye view being first
738 @item row_interleaved_rl
739 Each view is constituted by a row based interleaving, Right-eye view is first row
740 @item row_interleaved_lr
741 Each view is constituted by a row based interleaving, Left-eye view is first row
742 @item col_interleaved_rl
743 Both views are arranged in a column based interleaving manner, Right-eye view is first column
744 @item col_interleaved_lr
745 Both views are arranged in a column based interleaving manner, Left-eye view is first column
746 @item anaglyph_cyan_red
747 All frames are in anaglyph format viewable through red-cyan filters
749 Both views are arranged side by side, Right-eye view is on the left
750 @item anaglyph_green_magenta
751 All frames are in anaglyph format viewable through green-magenta filters
753 Both eyes laced in one Block, Left-eye view is first
755 Both eyes laced in one Block, Right-eye view is first
759 For example a 3D WebM clip can be created using the following command line:
761 ffmpeg -i sample_left_right_clip.mpg -an -c:v libvpx -metadata stereo_mode=left_right -y stereo_clip.webm
766 This muxer supports the following options:
769 @item reserve_index_space
770 By default, this muxer writes the index for seeking (called cues in Matroska
771 terms) at the end of the file, because it cannot know in advance how much space
772 to leave for the index at the beginning of the file. However for some use cases
773 -- e.g. streaming where seeking is possible but slow -- it is useful to put the
774 index at the beginning of the file.
776 If this option is set to a non-zero value, the muxer will reserve a given amount
777 of space in the file header and then try to write the cues there when the muxing
778 finishes. If the available space does not suffice, muxing will fail. A safe size
779 for most use cases should be about 50kB per hour of video.
781 Note that cues are only written if the output is seekable and this option will
782 have no effect if it is not.
790 This is a variant of the @ref{hash} muxer. Unlike that muxer, it
791 defaults to using the MD5 hash function.
795 To compute the MD5 hash of the input converted to raw
796 audio and video, and store it in the file @file{out.md5}:
798 ffmpeg -i INPUT -f md5 out.md5
801 You can print the MD5 to stdout with the command:
803 ffmpeg -i INPUT -f md5 -
806 See also the @ref{hash} and @ref{framemd5} muxers.
808 @section mov, mp4, ismv
810 MOV/MP4/ISMV (Smooth Streaming) muxer.
812 The mov/mp4/ismv muxer supports fragmentation. Normally, a MOV/MP4
813 file has all the metadata about all packets stored in one location
814 (written at the end of the file, it can be moved to the start for
815 better playback by adding @var{faststart} to the @var{movflags}, or
816 using the @command{qt-faststart} tool). A fragmented
817 file consists of a number of fragments, where packets and metadata
818 about these packets are stored together. Writing a fragmented
819 file has the advantage that the file is decodable even if the
820 writing is interrupted (while a normal MOV/MP4 is undecodable if
821 it is not properly finished), and it requires less memory when writing
822 very long files (since writing normal MOV/MP4 files stores info about
823 every single packet in memory until the file is closed). The downside
824 is that it is less compatible with other applications.
828 Fragmentation is enabled by setting one of the AVOptions that define
829 how to cut the file into fragments:
832 @item -moov_size @var{bytes}
833 Reserves space for the moov atom at the beginning of the file instead of placing the
834 moov atom at the end. If the space reserved is insufficient, muxing will fail.
835 @item -movflags frag_keyframe
836 Start a new fragment at each video keyframe.
837 @item -frag_duration @var{duration}
838 Create fragments that are @var{duration} microseconds long.
839 @item -frag_size @var{size}
840 Create fragments that contain up to @var{size} bytes of payload data.
841 @item -movflags frag_custom
842 Allow the caller to manually choose when to cut fragments, by
843 calling @code{av_write_frame(ctx, NULL)} to write a fragment with
844 the packets written so far. (This is only useful with other
845 applications integrating libavformat, not from @command{ffmpeg}.)
846 @item -min_frag_duration @var{duration}
847 Don't create fragments that are shorter than @var{duration} microseconds long.
850 If more than one condition is specified, fragments are cut when
851 one of the specified conditions is fulfilled. The exception to this is
852 @code{-min_frag_duration}, which has to be fulfilled for any of the other
855 Additionally, the way the output file is written can be adjusted
856 through a few other options:
859 @item -movflags empty_moov
860 Write an initial moov atom directly at the start of the file, without
861 describing any samples in it. Generally, an mdat/moov pair is written
862 at the start of the file, as a normal MOV/MP4 file, containing only
863 a short portion of the file. With this option set, there is no initial
864 mdat atom, and the moov atom only describes the tracks but has
867 This option is implicitly set when writing ismv (Smooth Streaming) files.
868 @item -movflags separate_moof
869 Write a separate moof (movie fragment) atom for each track. Normally,
870 packets for all tracks are written in a moof atom (which is slightly
871 more efficient), but with this option set, the muxer writes one moof/mdat
872 pair for each track, making it easier to separate tracks.
874 This option is implicitly set when writing ismv (Smooth Streaming) files.
875 @item -movflags faststart
876 Run a second pass moving the index (moov atom) to the beginning of the file.
877 This operation can take a while, and will not work in various situations such
878 as fragmented output, thus it is not enabled by default.
879 @item -movflags rtphint
880 Add RTP hinting tracks to the output file.
881 @item -movflags disable_chpl
882 Disable Nero chapter markers (chpl atom). Normally, both Nero chapters
883 and a QuickTime chapter track are written to the file. With this option
884 set, only the QuickTime chapter track will be written. Nero chapters can
885 cause failures when the file is reprocessed with certain tagging programs, like
886 mp3Tag 2.61a and iTunes 11.3, most likely other versions are affected as well.
887 @item -movflags omit_tfhd_offset
888 Do not write any absolute base_data_offset in tfhd atoms. This avoids
889 tying fragments to absolute byte positions in the file/streams.
890 @item -movflags default_base_moof
891 Similarly to the omit_tfhd_offset, this flag avoids writing the
892 absolute base_data_offset field in tfhd atoms, but does so by using
893 the new default-base-is-moof flag instead. This flag is new from
894 14496-12:2012. This may make the fragments easier to parse in certain
895 circumstances (avoiding basing track fragment location calculations
896 on the implicit end of the previous track fragment).
898 Specify @code{on} to force writing a timecode track, @code{off} to disable it
899 and @code{auto} to write a timecode track only for mov and mp4 output (default).
904 Smooth Streaming content can be pushed in real time to a publishing
905 point on IIS with this muxer. Example:
907 ffmpeg -re @var{<normal input/transcoding options>} -movflags isml+frag_keyframe -f ismv http://server/publishingpoint.isml/Streams(Encoder1)
910 @subsection Audible AAX
912 Audible AAX files are encrypted M4B files, and they can be decrypted by specifying a 4 byte activation secret.
914 ffmpeg -activation_bytes 1CEB00DA -i test.aax -vn -c:a copy output.mp4
919 The MP3 muxer writes a raw MP3 stream with the following optional features:
922 An ID3v2 metadata header at the beginning (enabled by default). Versions 2.3 and
923 2.4 are supported, the @code{id3v2_version} private option controls which one is
924 used (3 or 4). Setting @code{id3v2_version} to 0 disables the ID3v2 header
927 The muxer supports writing attached pictures (APIC frames) to the ID3v2 header.
928 The pictures are supplied to the muxer in form of a video stream with a single
929 packet. There can be any number of those streams, each will correspond to a
930 single APIC frame. The stream metadata tags @var{title} and @var{comment} map
931 to APIC @var{description} and @var{picture type} respectively. See
932 @url{http://id3.org/id3v2.4.0-frames} for allowed picture types.
934 Note that the APIC frames must be written at the beginning, so the muxer will
935 buffer the audio frames until it gets all the pictures. It is therefore advised
936 to provide the pictures as soon as possible to avoid excessive buffering.
939 A Xing/LAME frame right after the ID3v2 header (if present). It is enabled by
940 default, but will be written only if the output is seekable. The
941 @code{write_xing} private option can be used to disable it. The frame contains
942 various information that may be useful to the decoder, like the audio duration
946 A legacy ID3v1 tag at the end of the file (disabled by default). It may be
947 enabled with the @code{write_id3v1} private option, but as its capabilities are
948 very limited, its usage is not recommended.
953 Write an mp3 with an ID3v2.3 header and an ID3v1 footer:
955 ffmpeg -i INPUT -id3v2_version 3 -write_id3v1 1 out.mp3
958 To attach a picture to an mp3 file select both the audio and the picture stream
961 ffmpeg -i input.mp3 -i cover.png -c copy -map 0 -map 1
962 -metadata:s:v title="Album cover" -metadata:s:v comment="Cover (Front)" out.mp3
965 Write a "clean" MP3 without any extra features:
967 ffmpeg -i input.wav -write_xing 0 -id3v2_version 0 out.mp3
972 MPEG transport stream muxer.
974 This muxer implements ISO 13818-1 and part of ETSI EN 300 468.
976 The recognized metadata settings in mpegts muxer are @code{service_provider}
977 and @code{service_name}. If they are not set the default for
978 @code{service_provider} is "FFmpeg" and the default for
979 @code{service_name} is "Service01".
983 The muxer options are:
986 @item mpegts_original_network_id @var{number}
987 Set the original_network_id (default 0x0001). This is unique identifier
988 of a network in DVB. Its main use is in the unique identification of a
989 service through the path Original_Network_ID, Transport_Stream_ID.
990 @item mpegts_transport_stream_id @var{number}
991 Set the transport_stream_id (default 0x0001). This identifies a
993 @item mpegts_service_id @var{number}
994 Set the service_id (default 0x0001) also known as program in DVB.
995 @item mpegts_service_type @var{number}
996 Set the program service_type (default @var{digital_tv}), see below
997 a list of pre defined values.
998 @item mpegts_pmt_start_pid @var{number}
999 Set the first PID for PMT (default 0x1000, max 0x1f00).
1000 @item mpegts_start_pid @var{number}
1001 Set the first PID for data packets (default 0x0100, max 0x0f00).
1002 @item mpegts_m2ts_mode @var{number}
1003 Enable m2ts mode if set to 1. Default value is -1 which disables m2ts mode.
1004 @item muxrate @var{number}
1005 Set a constant muxrate (default VBR).
1006 @item pcr_period @var{numer}
1007 Override the default PCR retransmission time (default 20ms), ignored
1008 if variable muxrate is selected.
1009 @item pat_period @var{number}
1010 Maximal time in seconds between PAT/PMT tables.
1011 @item sdt_period @var{number}
1012 Maximal time in seconds between SDT tables.
1013 @item pes_payload_size @var{number}
1014 Set minimum PES packet payload in bytes.
1015 @item mpegts_flags @var{flags}
1016 Set flags (see below).
1017 @item mpegts_copyts @var{number}
1018 Preserve original timestamps, if value is set to 1. Default value is -1, which
1019 results in shifting timestamps so that they start from 0.
1020 @item tables_version @var{number}
1021 Set PAT, PMT and SDT version (default 0, valid values are from 0 to 31, inclusively).
1022 This option allows updating stream structure so that standard consumer may
1023 detect the change. To do so, reopen output AVFormatContext (in case of API
1024 usage) or restart ffmpeg instance, cyclically changing tables_version value:
1026 ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
1027 ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
1029 ffmpeg -i source3.ts -codec copy -f mpegts -tables_version 31 udp://1.1.1.1:1111
1030 ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
1031 ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
1036 Option @option{mpegts_service_type} accepts the following values:
1040 Any hexdecimal value between 0x01 to 0xff as defined in ETSI 300 468.
1044 Digital Radio service.
1047 @item advanced_codec_digital_radio
1048 Advanced Codec Digital Radio service.
1049 @item mpeg2_digital_hdtv
1050 MPEG2 Digital HDTV service.
1051 @item advanced_codec_digital_sdtv
1052 Advanced Codec Digital SDTV service.
1053 @item advanced_codec_digital_hdtv
1054 Advanced Codec Digital HDTV service.
1057 Option @option{mpegts_flags} may take a set of such flags:
1060 @item resend_headers
1061 Reemit PAT/PMT before writing the next packet.
1063 Use LATM packetization for AAC.
1064 @item pat_pmt_at_frames
1065 Reemit PAT and PMT at each video frame.
1067 Conform to System B (DVB) instead of System A (ATSC).
1068 @item initial_discontinuity
1069 Mark the initial packet of each stream as discontinuity.
1075 ffmpeg -i file.mpg -c copy \
1076 -mpegts_original_network_id 0x1122 \
1077 -mpegts_transport_stream_id 0x3344 \
1078 -mpegts_service_id 0x5566 \
1079 -mpegts_pmt_start_pid 0x1500 \
1080 -mpegts_start_pid 0x150 \
1081 -metadata service_provider="Some provider" \
1082 -metadata service_name="Some Channel" \
1086 @section mxf, mxf_d10
1092 The muxer options are:
1095 @item store_user_comments @var{bool}
1096 Set if user comments should be stored if available or never.
1097 IRT D-10 does not allow user comments. The default is thus to write them for
1098 mxf but not for mxf_d10
1105 This muxer does not generate any output file, it is mainly useful for
1106 testing or benchmarking purposes.
1108 For example to benchmark decoding with @command{ffmpeg} you can use the
1111 ffmpeg -benchmark -i INPUT -f null out.null
1114 Note that the above command does not read or write the @file{out.null}
1115 file, but specifying the output file is required by the @command{ffmpeg}
1118 Alternatively you can write the command as:
1120 ffmpeg -benchmark -i INPUT -f null -
1126 @item -syncpoints @var{flags}
1127 Change the syncpoint usage in nut:
1129 @item @var{default} use the normal low-overhead seeking aids.
1130 @item @var{none} do not use the syncpoints at all, reducing the overhead but making the stream non-seekable;
1131 Use of this option is not recommended, as the resulting files are very damage
1132 sensitive and seeking is not possible. Also in general the overhead from
1133 syncpoints is negligible. Note, -@code{write_index} 0 can be used to disable
1134 all growing data tables, allowing to mux endless streams with limited memory
1135 and without these disadvantages.
1136 @item @var{timestamped} extend the syncpoint with a wallclock field.
1138 The @var{none} and @var{timestamped} flags are experimental.
1139 @item -write_index @var{bool}
1140 Write index at the end, the default is to write an index.
1144 ffmpeg -i INPUT -f_strict experimental -syncpoints none - | processor
1149 Ogg container muxer.
1152 @item -page_duration @var{duration}
1153 Preferred page duration, in microseconds. The muxer will attempt to create
1154 pages that are approximately @var{duration} microseconds long. This allows the
1155 user to compromise between seek granularity and container overhead. The default
1156 is 1 second. A value of 0 will fill all segments, making pages as large as
1157 possible. A value of 1 will effectively use 1 packet-per-page in most
1158 situations, giving a small seek granularity at the cost of additional container
1160 @item -serial_offset @var{value}
1161 Serial value from which to set the streams serial number.
1162 Setting it to different and sufficiently large values ensures that the produced
1163 ogg files can be safely chained.
1168 @section segment, stream_segment, ssegment
1170 Basic stream segmenter.
1172 This muxer outputs streams to a number of separate files of nearly
1173 fixed duration. Output filename pattern can be set in a fashion
1174 similar to @ref{image2}, or by using a @code{strftime} template if
1175 the @option{strftime} option is enabled.
1177 @code{stream_segment} is a variant of the muxer used to write to
1178 streaming output formats, i.e. which do not require global headers,
1179 and is recommended for outputting e.g. to MPEG transport stream segments.
1180 @code{ssegment} is a shorter alias for @code{stream_segment}.
1182 Every segment starts with a keyframe of the selected reference stream,
1183 which is set through the @option{reference_stream} option.
1185 Note that if you want accurate splitting for a video file, you need to
1186 make the input key frames correspond to the exact splitting times
1187 expected by the segmenter, or the segment muxer will start the new
1188 segment with the key frame found next after the specified start
1191 The segment muxer works best with a single constant frame rate video.
1193 Optionally it can generate a list of the created segments, by setting
1194 the option @var{segment_list}. The list type is specified by the
1195 @var{segment_list_type} option. The entry filenames in the segment
1196 list are set by default to the basename of the corresponding segment
1199 See also the @ref{hls} muxer, which provides a more specific
1200 implementation for HLS segmentation.
1204 The segment muxer supports the following options:
1207 @item increment_tc @var{1|0}
1208 if set to @code{1}, increment timecode between each segment
1209 If this is selected, the input need to have
1210 a timecode in the first video stream. Default value is
1213 @item reference_stream @var{specifier}
1214 Set the reference stream, as specified by the string @var{specifier}.
1215 If @var{specifier} is set to @code{auto}, the reference is chosen
1216 automatically. Otherwise it must be a stream specifier (see the ``Stream
1217 specifiers'' chapter in the ffmpeg manual) which specifies the
1218 reference stream. The default value is @code{auto}.
1220 @item segment_format @var{format}
1221 Override the inner container format, by default it is guessed by the filename
1224 @item segment_format_options @var{options_list}
1225 Set output format options using a :-separated list of key=value
1226 parameters. Values containing the @code{:} special character must be
1229 @item segment_list @var{name}
1230 Generate also a listfile named @var{name}. If not specified no
1231 listfile is generated.
1233 @item segment_list_flags @var{flags}
1234 Set flags affecting the segment list generation.
1236 It currently supports the following flags:
1239 Allow caching (only affects M3U8 list files).
1242 Allow live-friendly file generation.
1245 @item segment_list_size @var{size}
1246 Update the list file so that it contains at most @var{size}
1247 segments. If 0 the list file will contain all the segments. Default
1250 @item segment_list_entry_prefix @var{prefix}
1251 Prepend @var{prefix} to each entry. Useful to generate absolute paths.
1252 By default no prefix is applied.
1254 @item segment_list_type @var{type}
1255 Select the listing format.
1257 The following values are recognized:
1260 Generate a flat list for the created segments, one segment per line.
1263 Generate a list for the created segments, one segment per line,
1264 each line matching the format (comma-separated values):
1266 @var{segment_filename},@var{segment_start_time},@var{segment_end_time}
1269 @var{segment_filename} is the name of the output file generated by the
1270 muxer according to the provided pattern. CSV escaping (according to
1271 RFC4180) is applied if required.
1273 @var{segment_start_time} and @var{segment_end_time} specify
1274 the segment start and end time expressed in seconds.
1276 A list file with the suffix @code{".csv"} or @code{".ext"} will
1277 auto-select this format.
1279 @samp{ext} is deprecated in favor or @samp{csv}.
1282 Generate an ffconcat file for the created segments. The resulting file
1283 can be read using the FFmpeg @ref{concat} demuxer.
1285 A list file with the suffix @code{".ffcat"} or @code{".ffconcat"} will
1286 auto-select this format.
1289 Generate an extended M3U8 file, version 3, compliant with
1290 @url{http://tools.ietf.org/id/draft-pantos-http-live-streaming}.
1292 A list file with the suffix @code{".m3u8"} will auto-select this format.
1295 If not specified the type is guessed from the list file name suffix.
1297 @item segment_time @var{time}
1298 Set segment duration to @var{time}, the value must be a duration
1299 specification. Default value is "2". See also the
1300 @option{segment_times} option.
1302 Note that splitting may not be accurate, unless you force the
1303 reference stream key-frames at the given time. See the introductory
1304 notice and the examples below.
1306 @item segment_atclocktime @var{1|0}
1307 If set to "1" split at regular clock time intervals starting from 00:00
1308 o'clock. The @var{time} value specified in @option{segment_time} is
1309 used for setting the length of the splitting interval.
1311 For example with @option{segment_time} set to "900" this makes it possible
1312 to create files at 12:00 o'clock, 12:15, 12:30, etc.
1314 Default value is "0".
1316 @item segment_clocktime_offset @var{duration}
1317 Delay the segment splitting times with the specified duration when using
1318 @option{segment_atclocktime}.
1320 For example with @option{segment_time} set to "900" and
1321 @option{segment_clocktime_offset} set to "300" this makes it possible to
1322 create files at 12:05, 12:20, 12:35, etc.
1324 Default value is "0".
1326 @item segment_clocktime_wrap_duration @var{duration}
1327 Force the segmenter to only start a new segment if a packet reaches the muxer
1328 within the specified duration after the segmenting clock time. This way you
1329 can make the segmenter more resilient to backward local time jumps, such as
1330 leap seconds or transition to standard time from daylight savings time.
1332 Assuming that the delay between the packets of your source is less than 0.5
1333 second you can detect a leap second by specifying 0.5 as the duration.
1335 Default is the maximum possible duration which means starting a new segment
1336 regardless of the elapsed time since the last clock time.
1338 @item segment_time_delta @var{delta}
1339 Specify the accuracy time when selecting the start time for a
1340 segment, expressed as a duration specification. Default value is "0".
1342 When delta is specified a key-frame will start a new segment if its
1343 PTS satisfies the relation:
1345 PTS >= start_time - time_delta
1348 This option is useful when splitting video content, which is always
1349 split at GOP boundaries, in case a key frame is found just before the
1350 specified split time.
1352 In particular may be used in combination with the @file{ffmpeg} option
1353 @var{force_key_frames}. The key frame times specified by
1354 @var{force_key_frames} may not be set accurately because of rounding
1355 issues, with the consequence that a key frame time may result set just
1356 before the specified time. For constant frame rate videos a value of
1357 1/(2*@var{frame_rate}) should address the worst case mismatch between
1358 the specified time and the time set by @var{force_key_frames}.
1360 @item segment_times @var{times}
1361 Specify a list of split points. @var{times} contains a list of comma
1362 separated duration specifications, in increasing order. See also
1363 the @option{segment_time} option.
1365 @item segment_frames @var{frames}
1366 Specify a list of split video frame numbers. @var{frames} contains a
1367 list of comma separated integer numbers, in increasing order.
1369 This option specifies to start a new segment whenever a reference
1370 stream key frame is found and the sequential number (starting from 0)
1371 of the frame is greater or equal to the next value in the list.
1373 @item segment_wrap @var{limit}
1374 Wrap around segment index once it reaches @var{limit}.
1376 @item segment_start_number @var{number}
1377 Set the sequence number of the first segment. Defaults to @code{0}.
1379 @item strftime @var{1|0}
1380 Use the @code{strftime} function to define the name of the new
1381 segments to write. If this is selected, the output segment name must
1382 contain a @code{strftime} function template. Default value is
1385 @item break_non_keyframes @var{1|0}
1386 If enabled, allow segments to start on frames other than keyframes. This
1387 improves behavior on some players when the time between keyframes is
1388 inconsistent, but may make things worse on others, and can cause some oddities
1389 during seeking. Defaults to @code{0}.
1391 @item reset_timestamps @var{1|0}
1392 Reset timestamps at the begin of each segment, so that each segment
1393 will start with near-zero timestamps. It is meant to ease the playback
1394 of the generated segments. May not work with some combinations of
1395 muxers/codecs. It is set to @code{0} by default.
1397 @item initial_offset @var{offset}
1398 Specify timestamp offset to apply to the output packet timestamps. The
1399 argument must be a time duration specification, and defaults to 0.
1401 @item write_empty_segments @var{1|0}
1402 If enabled, write an empty segment if there are no packets during the period a
1403 segment would usually span. Otherwise, the segment will be filled with the next
1404 packet written. Defaults to @code{0}.
1407 @subsection Examples
1411 Remux the content of file @file{in.mkv} to a list of segments
1412 @file{out-000.nut}, @file{out-001.nut}, etc., and write the list of
1413 generated segments to @file{out.list}:
1415 ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.list out%03d.nut
1419 Segment input and set output format options for the output segments:
1421 ffmpeg -i in.mkv -f segment -segment_time 10 -segment_format_options movflags=+faststart out%03d.mp4
1425 Segment the input file according to the split points specified by the
1426 @var{segment_times} option:
1428 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
1432 Use the @command{ffmpeg} @option{force_key_frames}
1433 option to force key frames in the input at the specified location, together
1434 with the segment option @option{segment_time_delta} to account for
1435 possible roundings operated when setting key frame times.
1437 ffmpeg -i in.mkv -force_key_frames 1,2,3,5,8,13,21 -codec:v mpeg4 -codec:a pcm_s16le -map 0 \
1438 -f segment -segment_list out.csv -segment_times 1,2,3,5,8,13,21 -segment_time_delta 0.05 out%03d.nut
1440 In order to force key frames on the input file, transcoding is
1444 Segment the input file by splitting the input file according to the
1445 frame numbers sequence specified with the @option{segment_frames} option:
1447 ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.csv -segment_frames 100,200,300,500,800 out%03d.nut
1451 Convert the @file{in.mkv} to TS segments using the @code{libx264}
1452 and @code{aac} encoders:
1454 ffmpeg -i in.mkv -map 0 -codec:v libx264 -codec:a aac -f ssegment -segment_list out.list out%03d.ts
1458 Segment the input file, and create an M3U8 live playlist (can be used
1459 as live HLS source):
1461 ffmpeg -re -i in.mkv -codec copy -map 0 -f segment -segment_list playlist.m3u8 \
1462 -segment_list_flags +live -segment_time 10 out%03d.mkv
1466 @section smoothstreaming
1468 Smooth Streaming muxer generates a set of files (Manifest, chunks) suitable for serving with conventional web server.
1472 Specify the number of fragments kept in the manifest. Default 0 (keep all).
1474 @item extra_window_size
1475 Specify the number of fragments kept outside of the manifest before removing from disk. Default 5.
1477 @item lookahead_count
1478 Specify the number of lookahead fragments. Default 2.
1480 @item min_frag_duration
1481 Specify the minimum fragment duration (in microseconds). Default 5000000.
1483 @item remove_at_exit
1484 Specify whether to remove all fragments when finished. Default 0 (do not remove).
1490 The fifo pseudo-muxer allows the separation of encoding and muxing by using
1491 first-in-first-out queue and running the actual muxer in a separate thread. This
1492 is especially useful in combination with the @ref{tee} muxer and can be used to
1493 send data to several destinations with different reliability/writing speed/latency.
1495 API users should be aware that callback functions (interrupt_callback,
1496 io_open and io_close) used within its AVFormatContext must be thread-safe.
1498 The behavior of the fifo muxer if the queue fills up or if the output fails is
1504 output can be transparently restarted with configurable delay between retries
1505 based on real time or time of the processed stream.
1508 encoding can be blocked during temporary failure, or continue transparently
1509 dropping packets in case fifo queue fills up.
1516 Specify the format name. Useful if it cannot be guessed from the
1520 Specify size of the queue (number of packets). Default value is 60.
1523 Specify format options for the underlying muxer. Muxer options can be specified
1524 as a list of @var{key}=@var{value} pairs separated by ':'.
1526 @item drop_pkts_on_overflow @var{bool}
1527 If set to 1 (true), in case the fifo queue fills up, packets will be dropped
1528 rather than blocking the encoder. This makes it possible to continue streaming without
1529 delaying the input, at the cost of omitting part of the stream. By default
1530 this option is set to 0 (false), so in such cases the encoder will be blocked
1531 until the muxer processes some of the packets and none of them is lost.
1533 @item attempt_recovery @var{bool}
1534 If failure occurs, attempt to recover the output. This is especially useful
1535 when used with network output, since it makes it possible to restart streaming transparently.
1536 By default this option is set to 0 (false).
1538 @item max_recovery_attempts
1539 Sets maximum number of successive unsuccessful recovery attempts after which
1540 the output fails permanently. By default this option is set to 0 (unlimited).
1542 @item recovery_wait_time @var{duration}
1543 Waiting time before the next recovery attempt after previous unsuccessful
1544 recovery attempt. Default value is 5 seconds.
1546 @item recovery_wait_streamtime @var{bool}
1547 If set to 0 (false), the real time is used when waiting for the recovery
1548 attempt (i.e. the recovery will be attempted after at least
1549 recovery_wait_time seconds).
1550 If set to 1 (true), the time of the processed stream is taken into account
1551 instead (i.e. the recovery will be attempted after at least @var{recovery_wait_time}
1552 seconds of the stream is omitted).
1553 By default, this option is set to 0 (false).
1555 @item recover_any_error @var{bool}
1556 If set to 1 (true), recovery will be attempted regardless of type of the error
1557 causing the failure. By default this option is set to 0 (false) and in case of
1558 certain (usually permanent) errors the recovery is not attempted even when
1559 @var{attempt_recovery} is set to 1.
1561 @item restart_with_keyframe @var{bool}
1562 Specify whether to wait for the keyframe after recovering from
1563 queue overflow or failure. This option is set to 0 (false) by default.
1567 @subsection Examples
1572 Stream something to rtmp server, continue processing the stream at real-time
1573 rate even in case of temporary failure (network outage) and attempt to recover
1574 streaming every second indefinitely.
1576 ffmpeg -re -i ... -c:v libx264 -c:a aac -f fifo -fifo_format flv -map 0:v -map 0:a
1577 -drop_pkts_on_overflow 1 -attempt_recovery 1 -recovery_wait_time 1 rtmp://example.com/live/stream_name
1585 The tee muxer can be used to write the same data to several files or any
1586 other kind of muxer. It can be used, for example, to both stream a video to
1587 the network and save it to disk at the same time.
1589 It is different from specifying several outputs to the @command{ffmpeg}
1590 command-line tool because the audio and video data will be encoded only once
1591 with the tee muxer; encoding can be a very expensive process. It is not
1592 useful when using the libavformat API directly because it is then possible
1593 to feed the same packets to several muxers directly.
1595 The slave outputs are specified in the file name given to the muxer,
1596 separated by '|'. If any of the slave name contains the '|' separator,
1597 leading or trailing spaces or any special character, it must be
1598 escaped (see @ref{quoting_and_escaping,,the "Quoting and escaping"
1599 section in the ffmpeg-utils(1) manual,ffmpeg-utils}).
1601 Muxer options can be specified for each slave by prepending them as a list of
1602 @var{key}=@var{value} pairs separated by ':', between square brackets. If
1603 the options values contain a special character or the ':' separator, they
1604 must be escaped; note that this is a second level escaping.
1606 The following special options are also recognized:
1609 Specify the format name. Useful if it cannot be guessed from the
1612 @item bsfs[/@var{spec}]
1613 Specify a list of bitstream filters to apply to the specified
1616 It is possible to specify to which streams a given bitstream filter
1617 applies, by appending a stream specifier to the option separated by
1618 @code{/}. @var{spec} must be a stream specifier (see @ref{Format
1619 stream specifiers}). If the stream specifier is not specified, the
1620 bitstream filters will be applied to all streams in the output.
1622 Several bitstream filters can be specified, separated by ",".
1625 Select the streams that should be mapped to the slave output,
1626 specified by a stream specifier. If not specified, this defaults to
1627 all the input streams. You may use multiple stream specifiers
1628 separated by commas (@code{,}) e.g.: @code{a:0,v}
1631 Specify behaviour on output failure. This can be set to either @code{abort} (which is
1632 default) or @code{ignore}. @code{abort} will cause whole process to fail in case of failure
1633 on this slave output. @code{ignore} will ignore failure on this output, so other outputs
1634 will continue without being affected.
1637 @subsection Examples
1641 Encode something and both archive it in a WebM file and stream it
1642 as MPEG-TS over UDP (the streams need to be explicitly mapped):
1644 ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a
1645 "archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/"
1649 As above, but continue streaming even if output to local file fails
1650 (for example local drive fills up):
1652 ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a
1653 "[onfail=ignore]archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/"
1657 Use @command{ffmpeg} to encode the input, and send the output
1658 to three different destinations. The @code{dump_extra} bitstream
1659 filter is used to add extradata information to all the output video
1660 keyframes packets, as requested by the MPEG-TS format. The select
1661 option is applied to @file{out.aac} in order to make it contain only
1664 ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac
1665 -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=a]out.aac"
1669 As below, but select only stream @code{a:1} for the audio output. Note
1670 that a second level escaping must be performed, as ":" is a special
1671 character used to separate options.
1673 ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac
1674 -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=\'a:1\']out.aac"
1678 Note: some codecs may need different options depending on the output format;
1679 the auto-detection of this can not work with the tee muxer. The main example
1680 is the @option{global_header} flag.
1682 @section webm_dash_manifest
1684 WebM DASH Manifest muxer.
1686 This muxer implements the WebM DASH Manifest specification to generate the DASH
1687 manifest XML. It also supports manifest generation for DASH live streams.
1689 For more information see:
1693 WebM DASH Specification: @url{https://sites.google.com/a/webmproject.org/wiki/adaptive-streaming/webm-dash-specification}
1695 ISO DASH Specification: @url{http://standards.iso.org/ittf/PubliclyAvailableStandards/c065274_ISO_IEC_23009-1_2014.zip}
1700 This muxer supports the following options:
1703 @item adaptation_sets
1704 This option has the following syntax: "id=x,streams=a,b,c id=y,streams=d,e" where x and y are the
1705 unique identifiers of the adaptation sets and a,b,c,d and e are the indices of the corresponding
1706 audio and video streams. Any number of adaptation sets can be added using this option.
1709 Set this to 1 to create a live stream DASH Manifest. Default: 0.
1711 @item chunk_start_index
1712 Start index of the first chunk. This will go in the @samp{startNumber} attribute
1713 of the @samp{SegmentTemplate} element in the manifest. Default: 0.
1715 @item chunk_duration_ms
1716 Duration of each chunk in milliseconds. This will go in the @samp{duration}
1717 attribute of the @samp{SegmentTemplate} element in the manifest. Default: 1000.
1719 @item utc_timing_url
1720 URL of the page that will return the UTC timestamp in ISO format. This will go
1721 in the @samp{value} attribute of the @samp{UTCTiming} element in the manifest.
1724 @item time_shift_buffer_depth
1725 Smallest time (in seconds) shifting buffer for which any Representation is
1726 guaranteed to be available. This will go in the @samp{timeShiftBufferDepth}
1727 attribute of the @samp{MPD} element. Default: 60.
1729 @item minimum_update_period
1730 Minimum update period (in seconds) of the manifest. This will go in the
1731 @samp{minimumUpdatePeriod} attribute of the @samp{MPD} element. Default: 0.
1737 ffmpeg -f webm_dash_manifest -i video1.webm \
1738 -f webm_dash_manifest -i video2.webm \
1739 -f webm_dash_manifest -i audio1.webm \
1740 -f webm_dash_manifest -i audio2.webm \
1741 -map 0 -map 1 -map 2 -map 3 \
1743 -f webm_dash_manifest \
1744 -adaptation_sets "id=0,streams=0,1 id=1,streams=2,3" \
1750 WebM Live Chunk Muxer.
1752 This muxer writes out WebM headers and chunks as separate files which can be
1753 consumed by clients that support WebM Live streams via DASH.
1757 This muxer supports the following options:
1760 @item chunk_start_index
1761 Index of the first chunk (defaults to 0).
1764 Filename of the header where the initialization data will be written.
1766 @item audio_chunk_duration
1767 Duration of each audio chunk in milliseconds (defaults to 5000).
1772 ffmpeg -f v4l2 -i /dev/video0 \
1776 -s 640x360 -keyint_min 30 -g 30 \
1778 -header webm_live_video_360.hdr \
1779 -chunk_start_index 1 \
1780 webm_live_video_360_%d.chk \
1785 -header webm_live_audio_128.hdr \
1786 -chunk_start_index 1 \
1787 -audio_chunk_duration 1000 \
1788 webm_live_audio_128_%d.chk