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 add_keyframe_index
155 Used to facilitate seeking; particularly for HTTP pseudo streaming.
162 Per-packet CRC (Cyclic Redundancy Check) testing format.
164 This muxer computes and prints the Adler-32 CRC for each audio
165 and video packet. By default audio frames are converted to signed
166 16-bit raw audio and video frames to raw video before computing the
169 The output of the muxer consists of a line for each audio and video
172 @var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, 0x@var{CRC}
175 @var{CRC} is a hexadecimal number 0-padded to 8 digits containing the
180 For example to compute the CRC of the audio and video frames in
181 @file{INPUT}, converted to raw audio and video packets, and store it
182 in the file @file{out.crc}:
184 ffmpeg -i INPUT -f framecrc out.crc
187 To print the information to stdout, use the command:
189 ffmpeg -i INPUT -f framecrc -
192 With @command{ffmpeg}, you can select the output format to which the
193 audio and video frames are encoded before computing the CRC for each
194 packet by specifying the audio and video codec. For example, to
195 compute the CRC of each decoded input audio frame converted to PCM
196 unsigned 8-bit and of each decoded input video frame converted to
197 MPEG-2 video, use the command:
199 ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f framecrc -
202 See also the @ref{crc} muxer.
207 Per-packet hash testing format.
209 This muxer computes and prints a cryptographic hash for each audio
210 and video packet. This can be used for packet-by-packet equality
211 checks without having to individually do a binary comparison on each.
213 By default audio frames are converted to signed 16-bit raw audio and
214 video frames to raw video before computing the hash, but the output
215 of explicit conversions to other codecs can also be used. It uses the
216 SHA-256 cryptographic hash function by default, but supports several
219 The output of the muxer consists of a line for each audio and video
222 @var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, @var{hash}
225 @var{hash} is a hexadecimal number representing the computed hash
229 @item hash @var{algorithm}
230 Use the cryptographic hash function specified by the string @var{algorithm}.
231 Supported values include @code{MD5}, @code{murmur3}, @code{RIPEMD128},
232 @code{RIPEMD160}, @code{RIPEMD256}, @code{RIPEMD320}, @code{SHA160},
233 @code{SHA224}, @code{SHA256} (default), @code{SHA512/224}, @code{SHA512/256},
234 @code{SHA384}, @code{SHA512}, @code{CRC32} and @code{adler32}.
240 To compute the SHA-256 hash of the audio and video frames in @file{INPUT},
241 converted to raw audio and video packets, and store it in the file
244 ffmpeg -i INPUT -f framehash out.sha256
247 To print the information to stdout, using the MD5 hash function, use
250 ffmpeg -i INPUT -f framehash -hash md5 -
253 See also the @ref{hash} muxer.
258 Per-packet MD5 testing format.
260 This is a variant of the @ref{framehash} muxer. Unlike that muxer,
261 it defaults to using the MD5 hash function.
265 To compute the MD5 hash of the audio and video frames in @file{INPUT},
266 converted to raw audio and video packets, and store it in the file
269 ffmpeg -i INPUT -f framemd5 out.md5
272 To print the information to stdout, use the command:
274 ffmpeg -i INPUT -f framemd5 -
277 See also the @ref{framehash} and @ref{md5} muxers.
284 It accepts the following options:
288 Set the number of times to loop the output. Use @code{-1} for no loop, @code{0}
289 for looping indefinitely (default).
292 Force the delay (expressed in centiseconds) after the last frame. Each frame
293 ends with a delay until the next frame. The default is @code{-1}, which is a
294 special value to tell the muxer to re-use the previous delay. In case of a
295 loop, you might want to customize this value to mark a pause for instance.
298 For example, to encode a gif looping 10 times, with a 5 seconds delay between
301 ffmpeg -i INPUT -loop 10 -final_delay 500 out.gif
304 Note 1: if you wish to extract the frames into separate GIF files, you need to
305 force the @ref{image2} muxer:
307 ffmpeg -i INPUT -c:v gif -f image2 "out%d.gif"
310 Note 2: the GIF format has a very large time base: the delay between two frames
311 can therefore not be smaller than one centi second.
318 This muxer computes and prints a cryptographic hash of all the input
319 audio and video frames. This can be used for equality checks without
320 having to do a complete binary comparison.
322 By default audio frames are converted to signed 16-bit raw audio and
323 video frames to raw video before computing the hash, but the output
324 of explicit conversions to other codecs can also be used. Timestamps
325 are ignored. It uses the SHA-256 cryptographic hash function by default,
326 but supports several other algorithms.
328 The output of the muxer consists of a single line of the form:
329 @var{algo}=@var{hash}, where @var{algo} is a short string representing
330 the hash function used, and @var{hash} is a hexadecimal number
331 representing the computed hash.
334 @item hash @var{algorithm}
335 Use the cryptographic hash function specified by the string @var{algorithm}.
336 Supported values include @code{MD5}, @code{murmur3}, @code{RIPEMD128},
337 @code{RIPEMD160}, @code{RIPEMD256}, @code{RIPEMD320}, @code{SHA160},
338 @code{SHA224}, @code{SHA256} (default), @code{SHA512/224}, @code{SHA512/256},
339 @code{SHA384}, @code{SHA512}, @code{CRC32} and @code{adler32}.
345 To compute the SHA-256 hash of the input converted to raw audio and
346 video, and store it in the file @file{out.sha256}:
348 ffmpeg -i INPUT -f hash out.sha256
351 To print an MD5 hash to stdout use the command:
353 ffmpeg -i INPUT -f hash -hash md5 -
356 See also the @ref{framehash} muxer.
361 Apple HTTP Live Streaming muxer that segments MPEG-TS according to
362 the HTTP Live Streaming (HLS) specification.
364 It creates a playlist file, and one or more segment files. The output filename
365 specifies the playlist filename.
367 By default, the muxer creates a file for each segment produced. These files
368 have the same name as the playlist, followed by a sequential number and a
371 For example, to convert an input file with @command{ffmpeg}:
373 ffmpeg -i in.nut out.m3u8
375 This example will produce the playlist, @file{out.m3u8}, and segment files:
376 @file{out0.ts}, @file{out1.ts}, @file{out2.ts}, etc.
378 See also the @ref{segment} muxer, which provides a more generic and
379 flexible implementation of a segmenter, and can be used to perform HLS
384 This muxer supports the following options:
387 @item hls_init_time @var{seconds}
388 Set the initial target segment length in seconds. Default value is @var{0}.
389 Segment will be cut on the next key frame after this time has passed on the first m3u8 list.
390 After the initial playlist is filled @command{ffmpeg} will cut segments
391 at duration equal to @code{hls_time}
393 @item hls_time @var{seconds}
394 Set the target segment length in seconds. Default value is 2.
395 Segment will be cut on the next key frame after this time has passed.
397 @item hls_list_size @var{size}
398 Set the maximum number of playlist entries. If set to 0 the list file
399 will contain all the segments. Default value is 5.
401 @item hls_ts_options @var{options_list}
402 Set output format options using a :-separated list of key=value
403 parameters. Values containing @code{:} special characters must be
406 @item hls_wrap @var{wrap}
407 Set the number after which the segment filename number (the number
408 specified in each segment file) wraps. If set to 0 the number will be
409 never wrapped. Default value is 0.
411 This option is useful to avoid to fill the disk with many segment
412 files, and limits the maximum number of segment files written to disk
415 @item start_number @var{number}
416 Start the playlist sequence number from @var{number}. Default value is
419 @item hls_allow_cache @var{allowcache}
420 Explicitly set whether the client MAY (1) or MUST NOT (0) cache media segments.
422 @item hls_base_url @var{baseurl}
423 Append @var{baseurl} to every entry in the playlist.
424 Useful to generate playlists with absolute paths.
426 Note that the playlist sequence number must be unique for each segment
427 and it is not to be confused with the segment filename sequence number
428 which can be cyclic, for example if the @option{wrap} option is
431 @item hls_segment_filename @var{filename}
432 Set the segment filename. Unless @code{hls_flags single_file} is set,
433 @var{filename} is used as a string format with the segment number:
435 ffmpeg -i in.nut -hls_segment_filename 'file%03d.ts' out.m3u8
437 This example will produce the playlist, @file{out.m3u8}, and segment files:
438 @file{file000.ts}, @file{file001.ts}, @file{file002.ts}, etc.
441 Use strftime on @var{filename} to expand the segment filename with localtime.
442 The segment number (%d) is not available in this mode.
444 ffmpeg -i in.nut -use_localtime 1 -hls_segment_filename 'file-%Y%m%d-%s.ts' out.m3u8
446 This example will produce the playlist, @file{out.m3u8}, and segment files:
447 @file{file-20160215-1455569023.ts}, @file{file-20160215-1455569024.ts}, etc.
449 @item use_localtime_mkdir
450 Used together with -use_localtime, it will create up to one subdirectory which
451 is expanded in @var{filename}.
453 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
455 This example will create a directory 201560215 (if it does not exist), and then
456 produce the playlist, @file{out.m3u8}, and segment files:
457 @file{201560215/file-20160215-1455569023.ts}, @file{201560215/file-20160215-1455569024.ts}, etc.
460 @item hls_key_info_file @var{key_info_file}
461 Use the information in @var{key_info_file} for segment encryption. The first
462 line of @var{key_info_file} specifies the key URI written to the playlist. The
463 key URL is used to access the encryption key during playback. The second line
464 specifies the path to the key file used to obtain the key during the encryption
465 process. The key file is read as a single packed array of 16 octets in binary
466 format. The optional third line specifies the initialization vector (IV) as a
467 hexadecimal string to be used instead of the segment sequence number (default)
468 for encryption. Changes to @var{key_info_file} will result in segment
469 encryption with the new key/IV and an entry in the playlist for the new key
472 Key info file format:
481 http://server/file.key
486 Example key file paths:
494 0123456789ABCDEF0123456789ABCDEF
497 Key info file example:
499 http://server/file.key
501 0123456789ABCDEF0123456789ABCDEF
504 Example shell script:
508 openssl rand 16 > file.key
509 echo $BASE_URL/file.key > file.keyinfo
510 echo file.key >> file.keyinfo
511 echo $(openssl rand -hex 16) >> file.keyinfo
512 ffmpeg -f lavfi -re -i testsrc -c:v h264 -hls_flags delete_segments \
513 -hls_key_info_file file.keyinfo out.m3u8
516 @item hls_flags single_file
517 If this flag is set, the muxer will store all segments in a single MPEG-TS
518 file, and will use byte ranges in the playlist. HLS playlists generated with
519 this way will have the version number 4.
522 ffmpeg -i in.nut -hls_flags single_file out.m3u8
524 Will produce the playlist, @file{out.m3u8}, and a single segment file,
527 @item hls_flags delete_segments
528 Segment files removed from the playlist are deleted after a period of time
529 equal to the duration of the segment plus the duration of the playlist.
531 @item hls_flags append_list
532 Append new segments into the end of old segment list,
533 and remove the @code{#EXT-X-ENDLIST} from the old segment list.
535 @item hls_flags round_durations
536 Round the duration info in the playlist file segment info to integer
537 values, instead of using floating point.
539 @item hls_flags discont_starts
540 Add the @code{#EXT-X-DISCONTINUITY} tag to the playlist, before the
541 first segment's information.
543 @item hls_flags omit_endlist
544 Do not append the @code{EXT-X-ENDLIST} tag at the end of the playlist.
546 @item hls_flags split_by_time
547 Allow segments to start on frames other than keyframes. This improves
548 behavior on some players when the time between keyframes is inconsistent,
549 but may make things worse on others, and can cause some oddities during
550 seeking. This flag should be used with the @code{hls_time} option.
552 @item hls_flags program_date_time
553 Generate @code{EXT-X-PROGRAM-DATE-TIME} tags.
555 @item hls_playlist_type event
556 Emit @code{#EXT-X-PLAYLIST-TYPE:EVENT} in the m3u8 header. Forces
557 @option{hls_list_size} to 0; the playlist can only be appended to.
559 @item hls_playlist_type vod
560 Emit @code{#EXT-X-PLAYLIST-TYPE:VOD} in the m3u8 header. Forces
561 @option{hls_list_size} to 0; the playlist must not change.
564 Use the given HTTP method to create the hls files.
566 ffmpeg -re -i in.ts -f hls -method PUT http://example.com/live/out.m3u8
568 This example will upload all the mpegts segment files to the HTTP
569 server using the HTTP PUT method, and update the m3u8 files every
570 @code{refresh} times using the same method.
571 Note that the HTTP server must support the given method for uploading
580 Microsoft's icon file format (ICO) has some strict limitations that should be noted:
584 Size cannot exceed 256 pixels in any dimension
587 Only BMP and PNG images can be stored
590 If a BMP image is used, it must be one of the following pixel formats:
592 BMP Bit Depth FFmpeg Pixel Format
602 If a BMP image is used, it must use the BITMAPINFOHEADER DIB header
605 If a PNG image is used, it must use the rgba pixel format
613 The image file muxer writes video frames to image files.
615 The output filenames are specified by a pattern, which can be used to
616 produce sequentially numbered series of files.
617 The pattern may contain the string "%d" or "%0@var{N}d", this string
618 specifies the position of the characters representing a numbering in
619 the filenames. If the form "%0@var{N}d" is used, the string
620 representing the number in each filename is 0-padded to @var{N}
621 digits. The literal character '%' can be specified in the pattern with
624 If the pattern contains "%d" or "%0@var{N}d", the first filename of
625 the file list specified will contain the number 1, all the following
626 numbers will be sequential.
628 The pattern may contain a suffix which is used to automatically
629 determine the format of the image files to write.
631 For example the pattern "img-%03d.bmp" will specify a sequence of
632 filenames of the form @file{img-001.bmp}, @file{img-002.bmp}, ...,
633 @file{img-010.bmp}, etc.
634 The pattern "img%%-%d.jpg" will specify a sequence of filenames of the
635 form @file{img%-1.jpg}, @file{img%-2.jpg}, ..., @file{img%-10.jpg},
640 The following example shows how to use @command{ffmpeg} for creating a
641 sequence of files @file{img-001.jpeg}, @file{img-002.jpeg}, ...,
642 taking one image every second from the input video:
644 ffmpeg -i in.avi -vsync cfr -r 1 -f image2 'img-%03d.jpeg'
647 Note that with @command{ffmpeg}, if the format is not specified with the
648 @code{-f} option and the output filename specifies an image file
649 format, the image2 muxer is automatically selected, so the previous
650 command can be written as:
652 ffmpeg -i in.avi -vsync cfr -r 1 'img-%03d.jpeg'
655 Note also that the pattern must not necessarily contain "%d" or
656 "%0@var{N}d", for example to create a single image file
657 @file{img.jpeg} from the start of the input video you can employ the command:
659 ffmpeg -i in.avi -f image2 -frames:v 1 img.jpeg
662 The @option{strftime} option allows you to expand the filename with
663 date and time information. Check the documentation of
664 the @code{strftime()} function for the syntax.
666 For example to generate image files from the @code{strftime()}
667 "%Y-%m-%d_%H-%M-%S" pattern, the following @command{ffmpeg} command
670 ffmpeg -f v4l2 -r 1 -i /dev/video0 -f image2 -strftime 1 "%Y-%m-%d_%H-%M-%S.jpg"
677 Start the sequence from the specified number. Default value is 0.
680 If set to 1, the filename will always be interpreted as just a
681 filename, not a pattern, and the corresponding file will be continuously
682 overwritten with new images. Default value is 0.
685 If set to 1, expand the filename with date and time information from
686 @code{strftime()}. Default value is 0.
689 The image muxer supports the .Y.U.V image file format. This format is
690 special in that that each image frame consists of three files, for
691 each of the YUV420P components. To read or write this image file format,
692 specify the name of the '.Y' file. The muxer will automatically open the
693 '.U' and '.V' files as required.
697 Matroska container muxer.
699 This muxer implements the matroska and webm container specs.
703 The recognized metadata settings in this muxer are:
707 Set title name provided to a single track.
710 Specify the language of the track in the Matroska languages form.
712 The language can be either the 3 letters bibliographic ISO-639-2 (ISO
713 639-2/B) form (like "fre" for French), or a language code mixed with a
714 country code for specialities in languages (like "fre-ca" for Canadian
718 Set stereo 3D video layout of two views in a single video track.
720 The following values are recognized:
725 Both views are arranged side by side, Left-eye view is on the left
727 Both views are arranged in top-bottom orientation, Left-eye view is at bottom
729 Both views are arranged in top-bottom orientation, Left-eye view is on top
730 @item checkerboard_rl
731 Each view is arranged in a checkerboard interleaved pattern, Left-eye view being first
732 @item checkerboard_lr
733 Each view is arranged in a checkerboard interleaved pattern, Right-eye view being first
734 @item row_interleaved_rl
735 Each view is constituted by a row based interleaving, Right-eye view is first row
736 @item row_interleaved_lr
737 Each view is constituted by a row based interleaving, Left-eye view is first row
738 @item col_interleaved_rl
739 Both views are arranged in a column based interleaving manner, Right-eye view is first column
740 @item col_interleaved_lr
741 Both views are arranged in a column based interleaving manner, Left-eye view is first column
742 @item anaglyph_cyan_red
743 All frames are in anaglyph format viewable through red-cyan filters
745 Both views are arranged side by side, Right-eye view is on the left
746 @item anaglyph_green_magenta
747 All frames are in anaglyph format viewable through green-magenta filters
749 Both eyes laced in one Block, Left-eye view is first
751 Both eyes laced in one Block, Right-eye view is first
755 For example a 3D WebM clip can be created using the following command line:
757 ffmpeg -i sample_left_right_clip.mpg -an -c:v libvpx -metadata stereo_mode=left_right -y stereo_clip.webm
762 This muxer supports the following options:
765 @item reserve_index_space
766 By default, this muxer writes the index for seeking (called cues in Matroska
767 terms) at the end of the file, because it cannot know in advance how much space
768 to leave for the index at the beginning of the file. However for some use cases
769 -- e.g. streaming where seeking is possible but slow -- it is useful to put the
770 index at the beginning of the file.
772 If this option is set to a non-zero value, the muxer will reserve a given amount
773 of space in the file header and then try to write the cues there when the muxing
774 finishes. If the available space does not suffice, muxing will fail. A safe size
775 for most use cases should be about 50kB per hour of video.
777 Note that cues are only written if the output is seekable and this option will
778 have no effect if it is not.
786 This is a variant of the @ref{hash} muxer. Unlike that muxer, it
787 defaults to using the MD5 hash function.
791 To compute the MD5 hash of the input converted to raw
792 audio and video, and store it in the file @file{out.md5}:
794 ffmpeg -i INPUT -f md5 out.md5
797 You can print the MD5 to stdout with the command:
799 ffmpeg -i INPUT -f md5 -
802 See also the @ref{hash} and @ref{framemd5} muxers.
804 @section mov, mp4, ismv
806 MOV/MP4/ISMV (Smooth Streaming) muxer.
808 The mov/mp4/ismv muxer supports fragmentation. Normally, a MOV/MP4
809 file has all the metadata about all packets stored in one location
810 (written at the end of the file, it can be moved to the start for
811 better playback by adding @var{faststart} to the @var{movflags}, or
812 using the @command{qt-faststart} tool). A fragmented
813 file consists of a number of fragments, where packets and metadata
814 about these packets are stored together. Writing a fragmented
815 file has the advantage that the file is decodable even if the
816 writing is interrupted (while a normal MOV/MP4 is undecodable if
817 it is not properly finished), and it requires less memory when writing
818 very long files (since writing normal MOV/MP4 files stores info about
819 every single packet in memory until the file is closed). The downside
820 is that it is less compatible with other applications.
824 Fragmentation is enabled by setting one of the AVOptions that define
825 how to cut the file into fragments:
828 @item -moov_size @var{bytes}
829 Reserves space for the moov atom at the beginning of the file instead of placing the
830 moov atom at the end. If the space reserved is insufficient, muxing will fail.
831 @item -movflags frag_keyframe
832 Start a new fragment at each video keyframe.
833 @item -frag_duration @var{duration}
834 Create fragments that are @var{duration} microseconds long.
835 @item -frag_size @var{size}
836 Create fragments that contain up to @var{size} bytes of payload data.
837 @item -movflags frag_custom
838 Allow the caller to manually choose when to cut fragments, by
839 calling @code{av_write_frame(ctx, NULL)} to write a fragment with
840 the packets written so far. (This is only useful with other
841 applications integrating libavformat, not from @command{ffmpeg}.)
842 @item -min_frag_duration @var{duration}
843 Don't create fragments that are shorter than @var{duration} microseconds long.
846 If more than one condition is specified, fragments are cut when
847 one of the specified conditions is fulfilled. The exception to this is
848 @code{-min_frag_duration}, which has to be fulfilled for any of the other
851 Additionally, the way the output file is written can be adjusted
852 through a few other options:
855 @item -movflags empty_moov
856 Write an initial moov atom directly at the start of the file, without
857 describing any samples in it. Generally, an mdat/moov pair is written
858 at the start of the file, as a normal MOV/MP4 file, containing only
859 a short portion of the file. With this option set, there is no initial
860 mdat atom, and the moov atom only describes the tracks but has
863 This option is implicitly set when writing ismv (Smooth Streaming) files.
864 @item -movflags separate_moof
865 Write a separate moof (movie fragment) atom for each track. Normally,
866 packets for all tracks are written in a moof atom (which is slightly
867 more efficient), but with this option set, the muxer writes one moof/mdat
868 pair for each track, making it easier to separate tracks.
870 This option is implicitly set when writing ismv (Smooth Streaming) files.
871 @item -movflags faststart
872 Run a second pass moving the index (moov atom) to the beginning of the file.
873 This operation can take a while, and will not work in various situations such
874 as fragmented output, thus it is not enabled by default.
875 @item -movflags rtphint
876 Add RTP hinting tracks to the output file.
877 @item -movflags disable_chpl
878 Disable Nero chapter markers (chpl atom). Normally, both Nero chapters
879 and a QuickTime chapter track are written to the file. With this option
880 set, only the QuickTime chapter track will be written. Nero chapters can
881 cause failures when the file is reprocessed with certain tagging programs, like
882 mp3Tag 2.61a and iTunes 11.3, most likely other versions are affected as well.
883 @item -movflags omit_tfhd_offset
884 Do not write any absolute base_data_offset in tfhd atoms. This avoids
885 tying fragments to absolute byte positions in the file/streams.
886 @item -movflags default_base_moof
887 Similarly to the omit_tfhd_offset, this flag avoids writing the
888 absolute base_data_offset field in tfhd atoms, but does so by using
889 the new default-base-is-moof flag instead. This flag is new from
890 14496-12:2012. This may make the fragments easier to parse in certain
891 circumstances (avoiding basing track fragment location calculations
892 on the implicit end of the previous track fragment).
894 Specify @code{on} to force writing a timecode track, @code{off} to disable it
895 and @code{auto} to write a timecode track only for mov and mp4 output (default).
900 Smooth Streaming content can be pushed in real time to a publishing
901 point on IIS with this muxer. Example:
903 ffmpeg -re @var{<normal input/transcoding options>} -movflags isml+frag_keyframe -f ismv http://server/publishingpoint.isml/Streams(Encoder1)
906 @subsection Audible AAX
908 Audible AAX files are encrypted M4B files, and they can be decrypted by specifying a 4 byte activation secret.
910 ffmpeg -activation_bytes 1CEB00DA -i test.aax -vn -c:a copy output.mp4
915 The MP3 muxer writes a raw MP3 stream with the following optional features:
918 An ID3v2 metadata header at the beginning (enabled by default). Versions 2.3 and
919 2.4 are supported, the @code{id3v2_version} private option controls which one is
920 used (3 or 4). Setting @code{id3v2_version} to 0 disables the ID3v2 header
923 The muxer supports writing attached pictures (APIC frames) to the ID3v2 header.
924 The pictures are supplied to the muxer in form of a video stream with a single
925 packet. There can be any number of those streams, each will correspond to a
926 single APIC frame. The stream metadata tags @var{title} and @var{comment} map
927 to APIC @var{description} and @var{picture type} respectively. See
928 @url{http://id3.org/id3v2.4.0-frames} for allowed picture types.
930 Note that the APIC frames must be written at the beginning, so the muxer will
931 buffer the audio frames until it gets all the pictures. It is therefore advised
932 to provide the pictures as soon as possible to avoid excessive buffering.
935 A Xing/LAME frame right after the ID3v2 header (if present). It is enabled by
936 default, but will be written only if the output is seekable. The
937 @code{write_xing} private option can be used to disable it. The frame contains
938 various information that may be useful to the decoder, like the audio duration
942 A legacy ID3v1 tag at the end of the file (disabled by default). It may be
943 enabled with the @code{write_id3v1} private option, but as its capabilities are
944 very limited, its usage is not recommended.
949 Write an mp3 with an ID3v2.3 header and an ID3v1 footer:
951 ffmpeg -i INPUT -id3v2_version 3 -write_id3v1 1 out.mp3
954 To attach a picture to an mp3 file select both the audio and the picture stream
957 ffmpeg -i input.mp3 -i cover.png -c copy -map 0 -map 1
958 -metadata:s:v title="Album cover" -metadata:s:v comment="Cover (Front)" out.mp3
961 Write a "clean" MP3 without any extra features:
963 ffmpeg -i input.wav -write_xing 0 -id3v2_version 0 out.mp3
968 MPEG transport stream muxer.
970 This muxer implements ISO 13818-1 and part of ETSI EN 300 468.
972 The recognized metadata settings in mpegts muxer are @code{service_provider}
973 and @code{service_name}. If they are not set the default for
974 @code{service_provider} is "FFmpeg" and the default for
975 @code{service_name} is "Service01".
979 The muxer options are:
982 @item mpegts_original_network_id @var{number}
983 Set the original_network_id (default 0x0001). This is unique identifier
984 of a network in DVB. Its main use is in the unique identification of a
985 service through the path Original_Network_ID, Transport_Stream_ID.
986 @item mpegts_transport_stream_id @var{number}
987 Set the transport_stream_id (default 0x0001). This identifies a
989 @item mpegts_service_id @var{number}
990 Set the service_id (default 0x0001) also known as program in DVB.
991 @item mpegts_service_type @var{number}
992 Set the program service_type (default @var{digital_tv}), see below
993 a list of pre defined values.
994 @item mpegts_pmt_start_pid @var{number}
995 Set the first PID for PMT (default 0x1000, max 0x1f00).
996 @item mpegts_start_pid @var{number}
997 Set the first PID for data packets (default 0x0100, max 0x0f00).
998 @item mpegts_m2ts_mode @var{number}
999 Enable m2ts mode if set to 1. Default value is -1 which disables m2ts mode.
1000 @item muxrate @var{number}
1001 Set a constant muxrate (default VBR).
1002 @item pcr_period @var{numer}
1003 Override the default PCR retransmission time (default 20ms), ignored
1004 if variable muxrate is selected.
1005 @item pat_period @var{number}
1006 Maximal time in seconds between PAT/PMT tables.
1007 @item sdt_period @var{number}
1008 Maximal time in seconds between SDT tables.
1009 @item pes_payload_size @var{number}
1010 Set minimum PES packet payload in bytes.
1011 @item mpegts_flags @var{flags}
1012 Set flags (see below).
1013 @item mpegts_copyts @var{number}
1014 Preserve original timestamps, if value is set to 1. Default value is -1, which
1015 results in shifting timestamps so that they start from 0.
1016 @item tables_version @var{number}
1017 Set PAT, PMT and SDT version (default 0, valid values are from 0 to 31, inclusively).
1018 This option allows updating stream structure so that standard consumer may
1019 detect the change. To do so, reopen output AVFormatContext (in case of API
1020 usage) or restart ffmpeg instance, cyclically changing tables_version value:
1022 ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
1023 ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
1025 ffmpeg -i source3.ts -codec copy -f mpegts -tables_version 31 udp://1.1.1.1:1111
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
1032 Option @option{mpegts_service_type} accepts the following values:
1036 Any hexdecimal value between 0x01 to 0xff as defined in ETSI 300 468.
1040 Digital Radio service.
1043 @item advanced_codec_digital_radio
1044 Advanced Codec Digital Radio service.
1045 @item mpeg2_digital_hdtv
1046 MPEG2 Digital HDTV service.
1047 @item advanced_codec_digital_sdtv
1048 Advanced Codec Digital SDTV service.
1049 @item advanced_codec_digital_hdtv
1050 Advanced Codec Digital HDTV service.
1053 Option @option{mpegts_flags} may take a set of such flags:
1056 @item resend_headers
1057 Reemit PAT/PMT before writing the next packet.
1059 Use LATM packetization for AAC.
1060 @item pat_pmt_at_frames
1061 Reemit PAT and PMT at each video frame.
1063 Conform to System B (DVB) instead of System A (ATSC).
1064 @item initial_discontinuity
1065 Mark the initial packet of each stream as discontinuity.
1071 ffmpeg -i file.mpg -c copy \
1072 -mpegts_original_network_id 0x1122 \
1073 -mpegts_transport_stream_id 0x3344 \
1074 -mpegts_service_id 0x5566 \
1075 -mpegts_pmt_start_pid 0x1500 \
1076 -mpegts_start_pid 0x150 \
1077 -metadata service_provider="Some provider" \
1078 -metadata service_name="Some Channel" \
1082 @section mxf, mxf_d10
1088 The muxer options are:
1091 @item store_user_comments @var{bool}
1092 Set if user comments should be stored if available or never.
1093 IRT D-10 does not allow user comments. The default is thus to write them for
1094 mxf but not for mxf_d10
1101 This muxer does not generate any output file, it is mainly useful for
1102 testing or benchmarking purposes.
1104 For example to benchmark decoding with @command{ffmpeg} you can use the
1107 ffmpeg -benchmark -i INPUT -f null out.null
1110 Note that the above command does not read or write the @file{out.null}
1111 file, but specifying the output file is required by the @command{ffmpeg}
1114 Alternatively you can write the command as:
1116 ffmpeg -benchmark -i INPUT -f null -
1122 @item -syncpoints @var{flags}
1123 Change the syncpoint usage in nut:
1125 @item @var{default} use the normal low-overhead seeking aids.
1126 @item @var{none} do not use the syncpoints at all, reducing the overhead but making the stream non-seekable;
1127 Use of this option is not recommended, as the resulting files are very damage
1128 sensitive and seeking is not possible. Also in general the overhead from
1129 syncpoints is negligible. Note, -@code{write_index} 0 can be used to disable
1130 all growing data tables, allowing to mux endless streams with limited memory
1131 and without these disadvantages.
1132 @item @var{timestamped} extend the syncpoint with a wallclock field.
1134 The @var{none} and @var{timestamped} flags are experimental.
1135 @item -write_index @var{bool}
1136 Write index at the end, the default is to write an index.
1140 ffmpeg -i INPUT -f_strict experimental -syncpoints none - | processor
1145 Ogg container muxer.
1148 @item -page_duration @var{duration}
1149 Preferred page duration, in microseconds. The muxer will attempt to create
1150 pages that are approximately @var{duration} microseconds long. This allows the
1151 user to compromise between seek granularity and container overhead. The default
1152 is 1 second. A value of 0 will fill all segments, making pages as large as
1153 possible. A value of 1 will effectively use 1 packet-per-page in most
1154 situations, giving a small seek granularity at the cost of additional container
1156 @item -serial_offset @var{value}
1157 Serial value from which to set the streams serial number.
1158 Setting it to different and sufficiently large values ensures that the produced
1159 ogg files can be safely chained.
1164 @section segment, stream_segment, ssegment
1166 Basic stream segmenter.
1168 This muxer outputs streams to a number of separate files of nearly
1169 fixed duration. Output filename pattern can be set in a fashion
1170 similar to @ref{image2}, or by using a @code{strftime} template if
1171 the @option{strftime} option is enabled.
1173 @code{stream_segment} is a variant of the muxer used to write to
1174 streaming output formats, i.e. which do not require global headers,
1175 and is recommended for outputting e.g. to MPEG transport stream segments.
1176 @code{ssegment} is a shorter alias for @code{stream_segment}.
1178 Every segment starts with a keyframe of the selected reference stream,
1179 which is set through the @option{reference_stream} option.
1181 Note that if you want accurate splitting for a video file, you need to
1182 make the input key frames correspond to the exact splitting times
1183 expected by the segmenter, or the segment muxer will start the new
1184 segment with the key frame found next after the specified start
1187 The segment muxer works best with a single constant frame rate video.
1189 Optionally it can generate a list of the created segments, by setting
1190 the option @var{segment_list}. The list type is specified by the
1191 @var{segment_list_type} option. The entry filenames in the segment
1192 list are set by default to the basename of the corresponding segment
1195 See also the @ref{hls} muxer, which provides a more specific
1196 implementation for HLS segmentation.
1200 The segment muxer supports the following options:
1203 @item increment_tc @var{1|0}
1204 if set to @code{1}, increment timecode between each segment
1205 If this is selected, the input need to have
1206 a timecode in the first video stream. Default value is
1209 @item reference_stream @var{specifier}
1210 Set the reference stream, as specified by the string @var{specifier}.
1211 If @var{specifier} is set to @code{auto}, the reference is chosen
1212 automatically. Otherwise it must be a stream specifier (see the ``Stream
1213 specifiers'' chapter in the ffmpeg manual) which specifies the
1214 reference stream. The default value is @code{auto}.
1216 @item segment_format @var{format}
1217 Override the inner container format, by default it is guessed by the filename
1220 @item segment_format_options @var{options_list}
1221 Set output format options using a :-separated list of key=value
1222 parameters. Values containing the @code{:} special character must be
1225 @item segment_list @var{name}
1226 Generate also a listfile named @var{name}. If not specified no
1227 listfile is generated.
1229 @item segment_list_flags @var{flags}
1230 Set flags affecting the segment list generation.
1232 It currently supports the following flags:
1235 Allow caching (only affects M3U8 list files).
1238 Allow live-friendly file generation.
1241 @item segment_list_size @var{size}
1242 Update the list file so that it contains at most @var{size}
1243 segments. If 0 the list file will contain all the segments. Default
1246 @item segment_list_entry_prefix @var{prefix}
1247 Prepend @var{prefix} to each entry. Useful to generate absolute paths.
1248 By default no prefix is applied.
1250 @item segment_list_type @var{type}
1251 Select the listing format.
1253 The following values are recognized:
1256 Generate a flat list for the created segments, one segment per line.
1259 Generate a list for the created segments, one segment per line,
1260 each line matching the format (comma-separated values):
1262 @var{segment_filename},@var{segment_start_time},@var{segment_end_time}
1265 @var{segment_filename} is the name of the output file generated by the
1266 muxer according to the provided pattern. CSV escaping (according to
1267 RFC4180) is applied if required.
1269 @var{segment_start_time} and @var{segment_end_time} specify
1270 the segment start and end time expressed in seconds.
1272 A list file with the suffix @code{".csv"} or @code{".ext"} will
1273 auto-select this format.
1275 @samp{ext} is deprecated in favor or @samp{csv}.
1278 Generate an ffconcat file for the created segments. The resulting file
1279 can be read using the FFmpeg @ref{concat} demuxer.
1281 A list file with the suffix @code{".ffcat"} or @code{".ffconcat"} will
1282 auto-select this format.
1285 Generate an extended M3U8 file, version 3, compliant with
1286 @url{http://tools.ietf.org/id/draft-pantos-http-live-streaming}.
1288 A list file with the suffix @code{".m3u8"} will auto-select this format.
1291 If not specified the type is guessed from the list file name suffix.
1293 @item segment_time @var{time}
1294 Set segment duration to @var{time}, the value must be a duration
1295 specification. Default value is "2". See also the
1296 @option{segment_times} option.
1298 Note that splitting may not be accurate, unless you force the
1299 reference stream key-frames at the given time. See the introductory
1300 notice and the examples below.
1302 @item segment_atclocktime @var{1|0}
1303 If set to "1" split at regular clock time intervals starting from 00:00
1304 o'clock. The @var{time} value specified in @option{segment_time} is
1305 used for setting the length of the splitting interval.
1307 For example with @option{segment_time} set to "900" this makes it possible
1308 to create files at 12:00 o'clock, 12:15, 12:30, etc.
1310 Default value is "0".
1312 @item segment_clocktime_offset @var{duration}
1313 Delay the segment splitting times with the specified duration when using
1314 @option{segment_atclocktime}.
1316 For example with @option{segment_time} set to "900" and
1317 @option{segment_clocktime_offset} set to "300" this makes it possible to
1318 create files at 12:05, 12:20, 12:35, etc.
1320 Default value is "0".
1322 @item segment_clocktime_wrap_duration @var{duration}
1323 Force the segmenter to only start a new segment if a packet reaches the muxer
1324 within the specified duration after the segmenting clock time. This way you
1325 can make the segmenter more resilient to backward local time jumps, such as
1326 leap seconds or transition to standard time from daylight savings time.
1328 Assuming that the delay between the packets of your source is less than 0.5
1329 second you can detect a leap second by specifying 0.5 as the duration.
1331 Default is the maximum possible duration which means starting a new segment
1332 regardless of the elapsed time since the last clock time.
1334 @item segment_time_delta @var{delta}
1335 Specify the accuracy time when selecting the start time for a
1336 segment, expressed as a duration specification. Default value is "0".
1338 When delta is specified a key-frame will start a new segment if its
1339 PTS satisfies the relation:
1341 PTS >= start_time - time_delta
1344 This option is useful when splitting video content, which is always
1345 split at GOP boundaries, in case a key frame is found just before the
1346 specified split time.
1348 In particular may be used in combination with the @file{ffmpeg} option
1349 @var{force_key_frames}. The key frame times specified by
1350 @var{force_key_frames} may not be set accurately because of rounding
1351 issues, with the consequence that a key frame time may result set just
1352 before the specified time. For constant frame rate videos a value of
1353 1/(2*@var{frame_rate}) should address the worst case mismatch between
1354 the specified time and the time set by @var{force_key_frames}.
1356 @item segment_times @var{times}
1357 Specify a list of split points. @var{times} contains a list of comma
1358 separated duration specifications, in increasing order. See also
1359 the @option{segment_time} option.
1361 @item segment_frames @var{frames}
1362 Specify a list of split video frame numbers. @var{frames} contains a
1363 list of comma separated integer numbers, in increasing order.
1365 This option specifies to start a new segment whenever a reference
1366 stream key frame is found and the sequential number (starting from 0)
1367 of the frame is greater or equal to the next value in the list.
1369 @item segment_wrap @var{limit}
1370 Wrap around segment index once it reaches @var{limit}.
1372 @item segment_start_number @var{number}
1373 Set the sequence number of the first segment. Defaults to @code{0}.
1375 @item strftime @var{1|0}
1376 Use the @code{strftime} function to define the name of the new
1377 segments to write. If this is selected, the output segment name must
1378 contain a @code{strftime} function template. Default value is
1381 @item break_non_keyframes @var{1|0}
1382 If enabled, allow segments to start on frames other than keyframes. This
1383 improves behavior on some players when the time between keyframes is
1384 inconsistent, but may make things worse on others, and can cause some oddities
1385 during seeking. Defaults to @code{0}.
1387 @item reset_timestamps @var{1|0}
1388 Reset timestamps at the begin of each segment, so that each segment
1389 will start with near-zero timestamps. It is meant to ease the playback
1390 of the generated segments. May not work with some combinations of
1391 muxers/codecs. It is set to @code{0} by default.
1393 @item initial_offset @var{offset}
1394 Specify timestamp offset to apply to the output packet timestamps. The
1395 argument must be a time duration specification, and defaults to 0.
1397 @item write_empty_segments @var{1|0}
1398 If enabled, write an empty segment if there are no packets during the period a
1399 segment would usually span. Otherwise, the segment will be filled with the next
1400 packet written. Defaults to @code{0}.
1403 @subsection Examples
1407 Remux the content of file @file{in.mkv} to a list of segments
1408 @file{out-000.nut}, @file{out-001.nut}, etc., and write the list of
1409 generated segments to @file{out.list}:
1411 ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.list out%03d.nut
1415 Segment input and set output format options for the output segments:
1417 ffmpeg -i in.mkv -f segment -segment_time 10 -segment_format_options movflags=+faststart out%03d.mp4
1421 Segment the input file according to the split points specified by the
1422 @var{segment_times} option:
1424 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
1428 Use the @command{ffmpeg} @option{force_key_frames}
1429 option to force key frames in the input at the specified location, together
1430 with the segment option @option{segment_time_delta} to account for
1431 possible roundings operated when setting key frame times.
1433 ffmpeg -i in.mkv -force_key_frames 1,2,3,5,8,13,21 -codec:v mpeg4 -codec:a pcm_s16le -map 0 \
1434 -f segment -segment_list out.csv -segment_times 1,2,3,5,8,13,21 -segment_time_delta 0.05 out%03d.nut
1436 In order to force key frames on the input file, transcoding is
1440 Segment the input file by splitting the input file according to the
1441 frame numbers sequence specified with the @option{segment_frames} option:
1443 ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.csv -segment_frames 100,200,300,500,800 out%03d.nut
1447 Convert the @file{in.mkv} to TS segments using the @code{libx264}
1448 and @code{aac} encoders:
1450 ffmpeg -i in.mkv -map 0 -codec:v libx264 -codec:a aac -f ssegment -segment_list out.list out%03d.ts
1454 Segment the input file, and create an M3U8 live playlist (can be used
1455 as live HLS source):
1457 ffmpeg -re -i in.mkv -codec copy -map 0 -f segment -segment_list playlist.m3u8 \
1458 -segment_list_flags +live -segment_time 10 out%03d.mkv
1462 @section smoothstreaming
1464 Smooth Streaming muxer generates a set of files (Manifest, chunks) suitable for serving with conventional web server.
1468 Specify the number of fragments kept in the manifest. Default 0 (keep all).
1470 @item extra_window_size
1471 Specify the number of fragments kept outside of the manifest before removing from disk. Default 5.
1473 @item lookahead_count
1474 Specify the number of lookahead fragments. Default 2.
1476 @item min_frag_duration
1477 Specify the minimum fragment duration (in microseconds). Default 5000000.
1479 @item remove_at_exit
1480 Specify whether to remove all fragments when finished. Default 0 (do not remove).
1486 The fifo pseudo-muxer allows the separation of encoding and muxing by using
1487 first-in-first-out queue and running the actual muxer in a separate thread. This
1488 is especially useful in combination with the @ref{tee} muxer and can be used to
1489 send data to several destinations with different reliability/writing speed/latency.
1491 API users should be aware that callback functions (interrupt_callback,
1492 io_open and io_close) used within its AVFormatContext must be thread-safe.
1494 The behavior of the fifo muxer if the queue fills up or if the output fails is
1500 output can be transparently restarted with configurable delay between retries
1501 based on real time or time of the processed stream.
1504 encoding can be blocked during temporary failure, or continue transparently
1505 dropping packets in case fifo queue fills up.
1512 Specify the format name. Useful if it cannot be guessed from the
1516 Specify size of the queue (number of packets). Default value is 60.
1519 Specify format options for the underlying muxer. Muxer options can be specified
1520 as a list of @var{key}=@var{value} pairs separated by ':'.
1522 @item drop_pkts_on_overflow @var{bool}
1523 If set to 1 (true), in case the fifo queue fills up, packets will be dropped
1524 rather than blocking the encoder. This makes it possible to continue streaming without
1525 delaying the input, at the cost of omitting part of the stream. By default
1526 this option is set to 0 (false), so in such cases the encoder will be blocked
1527 until the muxer processes some of the packets and none of them is lost.
1529 @item attempt_recovery @var{bool}
1530 If failure occurs, attempt to recover the output. This is especially useful
1531 when used with network output, since it makes it possible to restart streaming transparently.
1532 By default this option is set to 0 (false).
1534 @item max_recovery_attempts
1535 Sets maximum number of successive unsuccessful recovery attempts after which
1536 the output fails permanently. By default this option is set to 0 (unlimited).
1538 @item recovery_wait_time @var{duration}
1539 Waiting time before the next recovery attempt after previous unsuccessful
1540 recovery attempt. Default value is 5 seconds.
1542 @item recovery_wait_streamtime @var{bool}
1543 If set to 0 (false), the real time is used when waiting for the recovery
1544 attempt (i.e. the recovery will be attempted after at least
1545 recovery_wait_time seconds).
1546 If set to 1 (true), the time of the processed stream is taken into account
1547 instead (i.e. the recovery will be attempted after at least @var{recovery_wait_time}
1548 seconds of the stream is omitted).
1549 By default, this option is set to 0 (false).
1551 @item recover_any_error @var{bool}
1552 If set to 1 (true), recovery will be attempted regardless of type of the error
1553 causing the failure. By default this option is set to 0 (false) and in case of
1554 certain (usually permanent) errors the recovery is not attempted even when
1555 @var{attempt_recovery} is set to 1.
1557 @item restart_with_keyframe @var{bool}
1558 Specify whether to wait for the keyframe after recovering from
1559 queue overflow or failure. This option is set to 0 (false) by default.
1563 @subsection Examples
1568 Stream something to rtmp server, continue processing the stream at real-time
1569 rate even in case of temporary failure (network outage) and attempt to recover
1570 streaming every second indefinitely.
1572 ffmpeg -re -i ... -c:v libx264 -c:a aac -f fifo -fifo_format flv -map 0:v -map 0:a
1573 -drop_pkts_on_overflow 1 -attempt_recovery 1 -recovery_wait_time 1 rtmp://example.com/live/stream_name
1581 The tee muxer can be used to write the same data to several files or any
1582 other kind of muxer. It can be used, for example, to both stream a video to
1583 the network and save it to disk at the same time.
1585 It is different from specifying several outputs to the @command{ffmpeg}
1586 command-line tool because the audio and video data will be encoded only once
1587 with the tee muxer; encoding can be a very expensive process. It is not
1588 useful when using the libavformat API directly because it is then possible
1589 to feed the same packets to several muxers directly.
1591 The slave outputs are specified in the file name given to the muxer,
1592 separated by '|'. If any of the slave name contains the '|' separator,
1593 leading or trailing spaces or any special character, it must be
1594 escaped (see @ref{quoting_and_escaping,,the "Quoting and escaping"
1595 section in the ffmpeg-utils(1) manual,ffmpeg-utils}).
1597 Muxer options can be specified for each slave by prepending them as a list of
1598 @var{key}=@var{value} pairs separated by ':', between square brackets. If
1599 the options values contain a special character or the ':' separator, they
1600 must be escaped; note that this is a second level escaping.
1602 The following special options are also recognized:
1605 Specify the format name. Useful if it cannot be guessed from the
1608 @item bsfs[/@var{spec}]
1609 Specify a list of bitstream filters to apply to the specified
1612 It is possible to specify to which streams a given bitstream filter
1613 applies, by appending a stream specifier to the option separated by
1614 @code{/}. @var{spec} must be a stream specifier (see @ref{Format
1615 stream specifiers}). If the stream specifier is not specified, the
1616 bitstream filters will be applied to all streams in the output.
1618 Several bitstream filters can be specified, separated by ",".
1621 Select the streams that should be mapped to the slave output,
1622 specified by a stream specifier. If not specified, this defaults to
1623 all the input streams. You may use multiple stream specifiers
1624 separated by commas (@code{,}) e.g.: @code{a:0,v}
1627 Specify behaviour on output failure. This can be set to either @code{abort} (which is
1628 default) or @code{ignore}. @code{abort} will cause whole process to fail in case of failure
1629 on this slave output. @code{ignore} will ignore failure on this output, so other outputs
1630 will continue without being affected.
1633 @subsection Examples
1637 Encode something and both archive it in a WebM file and stream it
1638 as MPEG-TS over UDP (the streams need to be explicitly mapped):
1640 ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a
1641 "archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/"
1645 As above, but continue streaming even if output to local file fails
1646 (for example local drive fills up):
1648 ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a
1649 "[onfail=ignore]archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/"
1653 Use @command{ffmpeg} to encode the input, and send the output
1654 to three different destinations. The @code{dump_extra} bitstream
1655 filter is used to add extradata information to all the output video
1656 keyframes packets, as requested by the MPEG-TS format. The select
1657 option is applied to @file{out.aac} in order to make it contain only
1660 ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac -strict experimental
1661 -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=a]out.aac"
1665 As below, but select only stream @code{a:1} for the audio output. Note
1666 that a second level escaping must be performed, as ":" is a special
1667 character used to separate options.
1669 ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac -strict experimental
1670 -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=\'a:1\']out.aac"
1674 Note: some codecs may need different options depending on the output format;
1675 the auto-detection of this can not work with the tee muxer. The main example
1676 is the @option{global_header} flag.
1678 @section webm_dash_manifest
1680 WebM DASH Manifest muxer.
1682 This muxer implements the WebM DASH Manifest specification to generate the DASH
1683 manifest XML. It also supports manifest generation for DASH live streams.
1685 For more information see:
1689 WebM DASH Specification: @url{https://sites.google.com/a/webmproject.org/wiki/adaptive-streaming/webm-dash-specification}
1691 ISO DASH Specification: @url{http://standards.iso.org/ittf/PubliclyAvailableStandards/c065274_ISO_IEC_23009-1_2014.zip}
1696 This muxer supports the following options:
1699 @item adaptation_sets
1700 This option has the following syntax: "id=x,streams=a,b,c id=y,streams=d,e" where x and y are the
1701 unique identifiers of the adaptation sets and a,b,c,d and e are the indices of the corresponding
1702 audio and video streams. Any number of adaptation sets can be added using this option.
1705 Set this to 1 to create a live stream DASH Manifest. Default: 0.
1707 @item chunk_start_index
1708 Start index of the first chunk. This will go in the @samp{startNumber} attribute
1709 of the @samp{SegmentTemplate} element in the manifest. Default: 0.
1711 @item chunk_duration_ms
1712 Duration of each chunk in milliseconds. This will go in the @samp{duration}
1713 attribute of the @samp{SegmentTemplate} element in the manifest. Default: 1000.
1715 @item utc_timing_url
1716 URL of the page that will return the UTC timestamp in ISO format. This will go
1717 in the @samp{value} attribute of the @samp{UTCTiming} element in the manifest.
1720 @item time_shift_buffer_depth
1721 Smallest time (in seconds) shifting buffer for which any Representation is
1722 guaranteed to be available. This will go in the @samp{timeShiftBufferDepth}
1723 attribute of the @samp{MPD} element. Default: 60.
1725 @item minimum_update_period
1726 Minimum update period (in seconds) of the manifest. This will go in the
1727 @samp{minimumUpdatePeriod} attribute of the @samp{MPD} element. Default: 0.
1733 ffmpeg -f webm_dash_manifest -i video1.webm \
1734 -f webm_dash_manifest -i video2.webm \
1735 -f webm_dash_manifest -i audio1.webm \
1736 -f webm_dash_manifest -i audio2.webm \
1737 -map 0 -map 1 -map 2 -map 3 \
1739 -f webm_dash_manifest \
1740 -adaptation_sets "id=0,streams=0,1 id=1,streams=2,3" \
1746 WebM Live Chunk Muxer.
1748 This muxer writes out WebM headers and chunks as separate files which can be
1749 consumed by clients that support WebM Live streams via DASH.
1753 This muxer supports the following options:
1756 @item chunk_start_index
1757 Index of the first chunk (defaults to 0).
1760 Filename of the header where the initialization data will be written.
1762 @item audio_chunk_duration
1763 Duration of each audio chunk in milliseconds (defaults to 5000).
1768 ffmpeg -f v4l2 -i /dev/video0 \
1772 -s 640x360 -keyint_min 30 -g 30 \
1774 -header webm_live_video_360.hdr \
1775 -chunk_start_index 1 \
1776 webm_live_video_360_%d.chk \
1781 -header webm_live_audio_128.hdr \
1782 -chunk_start_index 1 \
1783 -audio_chunk_duration 1000 \
1784 webm_live_audio_128_%d.chk