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.
26 It accepts the following options:
30 Enable ID3v2 tags writing when set to 1. Default is 0 (disabled).
33 Select ID3v2 version to write. Currently only version 3 and 4 (aka.
34 ID3v2.3 and ID3v2.4) are supported. The default is version 4.
41 CRC (Cyclic Redundancy Check) testing format.
43 This muxer computes and prints the Adler-32 CRC of all the input audio
44 and video frames. By default audio frames are converted to signed
45 16-bit raw audio and video frames to raw video before computing the
48 The output of the muxer consists of a single line of the form:
49 CRC=0x@var{CRC}, where @var{CRC} is a hexadecimal number 0-padded to
50 8 digits containing the CRC for all the decoded input frames.
52 For example to compute the CRC of the input, and store it in the file
55 ffmpeg -i INPUT -f crc out.crc
58 You can print the CRC to stdout with the command:
60 ffmpeg -i INPUT -f crc -
63 You can select the output format of each frame with @command{ffmpeg} by
64 specifying the audio and video codec and format. For example to
65 compute the CRC of the input audio converted to PCM unsigned 8-bit
66 and the input video converted to MPEG-2 video, use the command:
68 ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f crc -
71 See also the @ref{framecrc} muxer.
76 Per-packet CRC (Cyclic Redundancy Check) testing format.
78 This muxer computes and prints the Adler-32 CRC for each audio
79 and video packet. By default audio frames are converted to signed
80 16-bit raw audio and video frames to raw video before computing the
83 The output of the muxer consists of a line for each audio and video
86 @var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, 0x@var{CRC}
89 @var{CRC} is a hexadecimal number 0-padded to 8 digits containing the
92 For example to compute the CRC of the audio and video frames in
93 @file{INPUT}, converted to raw audio and video packets, and store it
94 in the file @file{out.crc}:
96 ffmpeg -i INPUT -f framecrc out.crc
99 To print the information to stdout, use the command:
101 ffmpeg -i INPUT -f framecrc -
104 With @command{ffmpeg}, you can select the output format to which the
105 audio and video frames are encoded before computing the CRC for each
106 packet by specifying the audio and video codec. For example, to
107 compute the CRC of each decoded input audio frame converted to PCM
108 unsigned 8-bit and of each decoded input video frame converted to
109 MPEG-2 video, use the command:
111 ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f framecrc -
114 See also the @ref{crc} muxer.
119 Per-packet MD5 testing format.
121 This muxer computes and prints the MD5 hash for each audio
122 and video packet. By default audio frames are converted to signed
123 16-bit raw audio and video frames to raw video before computing the
126 The output of the muxer consists of a line for each audio and video
129 @var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, @var{MD5}
132 @var{MD5} is a hexadecimal number representing the computed MD5 hash
135 For example to compute the MD5 of the audio and video frames in
136 @file{INPUT}, converted to raw audio and video packets, and store it
137 in the file @file{out.md5}:
139 ffmpeg -i INPUT -f framemd5 out.md5
142 To print the information to stdout, use the command:
144 ffmpeg -i INPUT -f framemd5 -
147 See also the @ref{md5} muxer.
152 Apple HTTP Live Streaming muxer that segments MPEG-TS according to
153 the HTTP Live Streaming specification.
155 It creates a playlist file and numbered segment files. The output
156 filename specifies the playlist filename; the segment filenames
157 receive the same basename as the playlist, a sequential number and
161 ffmpeg -i in.nut out.m3u8
165 @item -hls_time @var{seconds}
166 Set the segment length in seconds.
167 @item -hls_list_size @var{size}
168 Set the maximum number of playlist entries.
169 @item -hls_wrap @var{wrap}
170 Set the number after which index wraps.
171 @item -start_number @var{number}
172 Start the sequence from @var{number}.
180 Microsoft's icon file format (ICO) has some strict limitations that should be noted:
184 Size cannot exceed 256 pixels in any dimension
187 Only BMP and PNG images can be stored
190 If a BMP image is used, it must be one of the following pixel formats:
192 BMP Bit Depth FFmpeg Pixel Format
202 If a BMP image is used, it must use the BITMAPINFOHEADER DIB header
205 If a PNG image is used, it must use the rgba pixel format
213 The image file muxer writes video frames to image files.
215 The output filenames are specified by a pattern, which can be used to
216 produce sequentially numbered series of files.
217 The pattern may contain the string "%d" or "%0@var{N}d", this string
218 specifies the position of the characters representing a numbering in
219 the filenames. If the form "%0@var{N}d" is used, the string
220 representing the number in each filename is 0-padded to @var{N}
221 digits. The literal character '%' can be specified in the pattern with
224 If the pattern contains "%d" or "%0@var{N}d", the first filename of
225 the file list specified will contain the number 1, all the following
226 numbers will be sequential.
228 The pattern may contain a suffix which is used to automatically
229 determine the format of the image files to write.
231 For example the pattern "img-%03d.bmp" will specify a sequence of
232 filenames of the form @file{img-001.bmp}, @file{img-002.bmp}, ...,
233 @file{img-010.bmp}, etc.
234 The pattern "img%%-%d.jpg" will specify a sequence of filenames of the
235 form @file{img%-1.jpg}, @file{img%-2.jpg}, ..., @file{img%-10.jpg},
238 The following example shows how to use @command{ffmpeg} for creating a
239 sequence of files @file{img-001.jpeg}, @file{img-002.jpeg}, ...,
240 taking one image every second from the input video:
242 ffmpeg -i in.avi -vsync 1 -r 1 -f image2 'img-%03d.jpeg'
245 Note that with @command{ffmpeg}, if the format is not specified with the
246 @code{-f} option and the output filename specifies an image file
247 format, the image2 muxer is automatically selected, so the previous
248 command can be written as:
250 ffmpeg -i in.avi -vsync 1 -r 1 'img-%03d.jpeg'
253 Note also that the pattern must not necessarily contain "%d" or
254 "%0@var{N}d", for example to create a single image file
255 @file{img.jpeg} from the input video you can employ the command:
257 ffmpeg -i in.avi -f image2 -frames:v 1 img.jpeg
261 @item start_number @var{number}
262 Start the sequence from @var{number}. Default value is 1. Must be a
265 @item -update @var{number}
266 If @var{number} is nonzero, the filename will always be interpreted as just a
267 filename, not a pattern, and this file will be continuously overwritten with new
272 The image muxer supports the .Y.U.V image file format. This format is
273 special in that that each image frame consists of three files, for
274 each of the YUV420P components. To read or write this image file format,
275 specify the name of the '.Y' file. The muxer will automatically open the
276 '.U' and '.V' files as required.
280 Matroska container muxer.
282 This muxer implements the matroska and webm container specs.
284 The recognized metadata settings in this muxer are:
288 @item title=@var{title name}
289 Name provided to a single track
294 @item language=@var{language name}
295 Specifies the language of the track in the Matroska languages form
300 @item stereo_mode=@var{mode}
301 Stereo 3D video layout of two views in a single video track
306 Both views are arranged side by side, Left-eye view is on the left
308 Both views are arranged in top-bottom orientation, Left-eye view is at bottom
310 Both views are arranged in top-bottom orientation, Left-eye view is on top
311 @item checkerboard_rl
312 Each view is arranged in a checkerboard interleaved pattern, Left-eye view being first
313 @item checkerboard_lr
314 Each view is arranged in a checkerboard interleaved pattern, Right-eye view being first
315 @item row_interleaved_rl
316 Each view is constituted by a row based interleaving, Right-eye view is first row
317 @item row_interleaved_lr
318 Each view is constituted by a row based interleaving, Left-eye view is first row
319 @item col_interleaved_rl
320 Both views are arranged in a column based interleaving manner, Right-eye view is first column
321 @item col_interleaved_lr
322 Both views are arranged in a column based interleaving manner, Left-eye view is first column
323 @item anaglyph_cyan_red
324 All frames are in anaglyph format viewable through red-cyan filters
326 Both views are arranged side by side, Right-eye view is on the left
327 @item anaglyph_green_magenta
328 All frames are in anaglyph format viewable through green-magenta filters
330 Both eyes laced in one Block, Left-eye view is first
332 Both eyes laced in one Block, Right-eye view is first
336 For example a 3D WebM clip can be created using the following command line:
338 ffmpeg -i sample_left_right_clip.mpg -an -c:v libvpx -metadata stereo_mode=left_right -y stereo_clip.webm
341 This muxer supports the following options:
345 @item reserve_index_space
346 By default, this muxer writes the index for seeking (called cues in Matroska
347 terms) at the end of the file, because it cannot know in advance how much space
348 to leave for the index at the beginning of the file. However for some use cases
349 -- e.g. streaming where seeking is possible but slow -- it is useful to put the
350 index at the beginning of the file.
352 If this option is set to a non-zero value, the muxer will reserve a given amount
353 of space in the file header and then try to write the cues there when the muxing
354 finishes. If the available space does not suffice, muxing will fail. A safe size
355 for most use cases should be about 50kB per hour of video.
357 Note that cues are only written if the output is seekable and this option will
358 have no effect if it is not.
367 This muxer computes and prints the MD5 hash of all the input audio
368 and video frames. By default audio frames are converted to signed
369 16-bit raw audio and video frames to raw video before computing the
372 The output of the muxer consists of a single line of the form:
373 MD5=@var{MD5}, where @var{MD5} is a hexadecimal number representing
374 the computed MD5 hash.
376 For example to compute the MD5 hash of the input converted to raw
377 audio and video, and store it in the file @file{out.md5}:
379 ffmpeg -i INPUT -f md5 out.md5
382 You can print the MD5 to stdout with the command:
384 ffmpeg -i INPUT -f md5 -
387 See also the @ref{framemd5} muxer.
389 @section mov/mp4/ismv
391 MOV/MP4/ISMV (Smooth Streaming) muxer.
393 The mov/mp4/ismv muxer supports fragmentation. Normally, a MOV/MP4
394 file has all the metadata about all packets stored in one location
395 (written at the end of the file, it can be moved to the start for
396 better playback by adding @var{faststart} to the @var{movflags}, or
397 using the @command{qt-faststart} tool). A fragmented
398 file consists of a number of fragments, where packets and metadata
399 about these packets are stored together. Writing a fragmented
400 file has the advantage that the file is decodable even if the
401 writing is interrupted (while a normal MOV/MP4 is undecodable if
402 it is not properly finished), and it requires less memory when writing
403 very long files (since writing normal MOV/MP4 files stores info about
404 every single packet in memory until the file is closed). The downside
405 is that it is less compatible with other applications.
407 Fragmentation is enabled by setting one of the AVOptions that define
408 how to cut the file into fragments:
411 @item -moov_size @var{bytes}
412 Reserves space for the moov atom at the beginning of the file instead of placing the
413 moov atom at the end. If the space reserved is insufficient, muxing will fail.
414 @item -movflags frag_keyframe
415 Start a new fragment at each video keyframe.
416 @item -frag_duration @var{duration}
417 Create fragments that are @var{duration} microseconds long.
418 @item -frag_size @var{size}
419 Create fragments that contain up to @var{size} bytes of payload data.
420 @item -movflags frag_custom
421 Allow the caller to manually choose when to cut fragments, by
422 calling @code{av_write_frame(ctx, NULL)} to write a fragment with
423 the packets written so far. (This is only useful with other
424 applications integrating libavformat, not from @command{ffmpeg}.)
425 @item -min_frag_duration @var{duration}
426 Don't create fragments that are shorter than @var{duration} microseconds long.
429 If more than one condition is specified, fragments are cut when
430 one of the specified conditions is fulfilled. The exception to this is
431 @code{-min_frag_duration}, which has to be fulfilled for any of the other
434 Additionally, the way the output file is written can be adjusted
435 through a few other options:
438 @item -movflags empty_moov
439 Write an initial moov atom directly at the start of the file, without
440 describing any samples in it. Generally, an mdat/moov pair is written
441 at the start of the file, as a normal MOV/MP4 file, containing only
442 a short portion of the file. With this option set, there is no initial
443 mdat atom, and the moov atom only describes the tracks but has
446 Files written with this option set do not work in QuickTime.
447 This option is implicitly set when writing ismv (Smooth Streaming) files.
448 @item -movflags separate_moof
449 Write a separate moof (movie fragment) atom for each track. Normally,
450 packets for all tracks are written in a moof atom (which is slightly
451 more efficient), but with this option set, the muxer writes one moof/mdat
452 pair for each track, making it easier to separate tracks.
454 This option is implicitly set when writing ismv (Smooth Streaming) files.
455 @item -movflags faststart
456 Run a second pass moving the index (moov atom) to the beginning of the file.
457 This operation can take a while, and will not work in various situations such
458 as fragmented output, thus it is not enabled by default.
459 @item -movflags rtphint
460 Add RTP hinting tracks to the output file.
463 Smooth Streaming content can be pushed in real time to a publishing
464 point on IIS with this muxer. Example:
466 ffmpeg -re @var{<normal input/transcoding options>} -movflags isml+frag_keyframe -f ismv http://server/publishingpoint.isml/Streams(Encoder1)
471 The MP3 muxer writes a raw MP3 stream with an ID3v2 header at the beginning and
472 optionally an ID3v1 tag at the end. ID3v2.3 and ID3v2.4 are supported, the
473 @code{id3v2_version} option controls which one is used. The legacy ID3v1 tag is
474 not written by default, but may be enabled with the @code{write_id3v1} option.
476 For seekable output the muxer also writes a Xing frame at the beginning, which
477 contains the number of frames in the file. It is useful for computing duration
480 The muxer supports writing ID3v2 attached pictures (APIC frames). The pictures
481 are supplied to the muxer in form of a video stream with a single packet. There
482 can be any number of those streams, each will correspond to a single APIC frame.
483 The stream metadata tags @var{title} and @var{comment} map to APIC
484 @var{description} and @var{picture type} respectively. See
485 @url{http://id3.org/id3v2.4.0-frames} for allowed picture types.
487 Note that the APIC frames must be written at the beginning, so the muxer will
488 buffer the audio frames until it gets all the pictures. It is therefore advised
489 to provide the pictures as soon as possible to avoid excessive buffering.
493 Write an mp3 with an ID3v2.3 header and an ID3v1 footer:
495 ffmpeg -i INPUT -id3v2_version 3 -write_id3v1 1 out.mp3
498 To attach a picture to an mp3 file select both the audio and the picture stream
501 ffmpeg -i input.mp3 -i cover.png -c copy -map 0 -map 1
502 -metadata:s:v title="Album cover" -metadata:s:v comment="Cover (Front)" out.mp3
507 MPEG transport stream muxer.
509 This muxer implements ISO 13818-1 and part of ETSI EN 300 468.
511 The muxer options are:
514 @item -mpegts_original_network_id @var{number}
515 Set the original_network_id (default 0x0001). This is unique identifier
516 of a network in DVB. Its main use is in the unique identification of a
517 service through the path Original_Network_ID, Transport_Stream_ID.
518 @item -mpegts_transport_stream_id @var{number}
519 Set the transport_stream_id (default 0x0001). This identifies a
521 @item -mpegts_service_id @var{number}
522 Set the service_id (default 0x0001) also known as program in DVB.
523 @item -mpegts_pmt_start_pid @var{number}
524 Set the first PID for PMT (default 0x1000, max 0x1f00).
525 @item -mpegts_start_pid @var{number}
526 Set the first PID for data packets (default 0x0100, max 0x0f00).
527 @item -mpegts_m2ts_mode @var{number}
528 Enable m2ts mode if set to 1. Default value is -1 which disables m2ts mode.
529 @item -muxrate @var{number}
531 @item -pes_payload_size @var{number}
532 Set minimum PES packet payload in bytes.
533 @item -mpegts_flags @var{flags}
534 Set flags (see below).
535 @item -mpegts_copyts @var{number}
536 Preserve original timestamps, if value is set to 1. Default value is -1, which
537 results in shifting timestamps so that they start from 0.
538 @item -tables_version @var{number}
539 Set PAT, PMT and SDT version (default 0, valid values are from 0 to 31, inclusively).
540 This option allows updating stream structure so that standard consumer may
541 detect the change. To do so, reopen output AVFormatContext (in case of API
542 usage) or restart ffmpeg instance, cyclically changing tables_version value:
544 ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
545 ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
547 ffmpeg -i source3.ts -codec copy -f mpegts -tables_version 31 udp://1.1.1.1:1111
548 ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111
549 ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111
554 Option mpegts_flags may take a set of such flags:
558 Reemit PAT/PMT before writing the next packet.
560 Use LATM packetization for AAC.
563 The recognized metadata settings in mpegts muxer are @code{service_provider}
564 and @code{service_name}. If they are not set the default for
565 @code{service_provider} is "FFmpeg" and the default for
566 @code{service_name} is "Service01".
569 ffmpeg -i file.mpg -c copy \
570 -mpegts_original_network_id 0x1122 \
571 -mpegts_transport_stream_id 0x3344 \
572 -mpegts_service_id 0x5566 \
573 -mpegts_pmt_start_pid 0x1500 \
574 -mpegts_start_pid 0x150 \
575 -metadata service_provider="Some provider" \
576 -metadata service_name="Some Channel" \
584 This muxer does not generate any output file, it is mainly useful for
585 testing or benchmarking purposes.
587 For example to benchmark decoding with @command{ffmpeg} you can use the
590 ffmpeg -benchmark -i INPUT -f null out.null
593 Note that the above command does not read or write the @file{out.null}
594 file, but specifying the output file is required by the @command{ffmpeg}
597 Alternatively you can write the command as:
599 ffmpeg -benchmark -i INPUT -f null -
607 @item -page_duration @var{duration}
608 Preferred page duration, in microseconds. The muxer will attempt to create
609 pages that are approximately @var{duration} microseconds long. This allows the
610 user to compromise between seek granularity and container overhead. The default
611 is 1 second. A value of 0 will fill all segments, making pages as large as
612 possible. A value of 1 will effectively use 1 packet-per-page in most
613 situations, giving a small seek granularity at the cost of additional container
617 @section segment, stream_segment, ssegment
619 Basic stream segmenter.
621 The segmenter muxer outputs streams to a number of separate files of nearly
622 fixed duration. Output filename pattern can be set in a fashion similar to
625 @code{stream_segment} is a variant of the muxer used to write to
626 streaming output formats, i.e. which do not require global headers,
627 and is recommended for outputting e.g. to MPEG transport stream segments.
628 @code{ssegment} is a shorter alias for @code{stream_segment}.
630 Every segment starts with a keyframe of the selected reference stream,
631 which is set through the @option{reference_stream} option.
633 Note that if you want accurate splitting for a video file, you need to
634 make the input key frames correspond to the exact splitting times
635 expected by the segmenter, or the segment muxer will start the new
636 segment with the key frame found next after the specified start
639 The segment muxer works best with a single constant frame rate video.
641 Optionally it can generate a list of the created segments, by setting
642 the option @var{segment_list}. The list type is specified by the
643 @var{segment_list_type} option.
645 The segment muxer supports the following options:
648 @item reference_stream @var{specifier}
649 Set the reference stream, as specified by the string @var{specifier}.
650 If @var{specifier} is set to @code{auto}, the reference is choosen
651 automatically. Otherwise it must be a stream specifier (see the ``Stream
652 specifiers'' chapter in the ffmpeg manual) which specifies the
653 reference stream. The default value is @code{auto}.
655 @item segment_format @var{format}
656 Override the inner container format, by default it is guessed by the filename
659 @item segment_list @var{name}
660 Generate also a listfile named @var{name}. If not specified no
661 listfile is generated.
663 @item segment_list_flags @var{flags}
664 Set flags affecting the segment list generation.
666 It currently supports the following flags:
669 Allow caching (only affects M3U8 list files).
672 Allow live-friendly file generation.
675 Default value is @code{samp}.
677 @item segment_list_size @var{size}
678 Update the list file so that it contains at most the last @var{size}
679 segments. If 0 the list file will contain all the segments. Default
682 @item segment_list_type @var{type}
683 Specify the format for the segment list file.
685 The following values are recognized:
688 Generate a flat list for the created segments, one segment per line.
691 Generate a list for the created segments, one segment per line,
692 each line matching the format (comma-separated values):
694 @var{segment_filename},@var{segment_start_time},@var{segment_end_time}
697 @var{segment_filename} is the name of the output file generated by the
698 muxer according to the provided pattern. CSV escaping (according to
699 RFC4180) is applied if required.
701 @var{segment_start_time} and @var{segment_end_time} specify
702 the segment start and end time expressed in seconds.
704 A list file with the suffix @code{".csv"} or @code{".ext"} will
705 auto-select this format.
707 @samp{ext} is deprecated in favor or @samp{csv}.
710 Generate an ffconcat file for the created segments. The resulting file
711 can be read using the FFmpeg @ref{concat} demuxer.
713 A list file with the suffix @code{".ffcat"} or @code{".ffconcat"} will
714 auto-select this format.
717 Generate an extended M3U8 file, version 3, compliant with
718 @url{http://tools.ietf.org/id/draft-pantos-http-live-streaming}.
720 A list file with the suffix @code{".m3u8"} will auto-select this format.
723 If not specified the type is guessed from the list file name suffix.
725 @item segment_time @var{time}
726 Set segment duration to @var{time}, the value must be a duration
727 specification. Default value is "2". See also the
728 @option{segment_times} option.
730 Note that splitting may not be accurate, unless you force the
731 reference stream key-frames at the given time. See the introductory
732 notice and the examples below.
734 @item segment_time_delta @var{delta}
735 Specify the accuracy time when selecting the start time for a
736 segment, expressed as a duration specification. Default value is "0".
738 When delta is specified a key-frame will start a new segment if its
739 PTS satisfies the relation:
741 PTS >= start_time - time_delta
744 This option is useful when splitting video content, which is always
745 split at GOP boundaries, in case a key frame is found just before the
746 specified split time.
748 In particular may be used in combination with the @file{ffmpeg} option
749 @var{force_key_frames}. The key frame times specified by
750 @var{force_key_frames} may not be set accurately because of rounding
751 issues, with the consequence that a key frame time may result set just
752 before the specified time. For constant frame rate videos a value of
753 1/2*@var{frame_rate} should address the worst case mismatch between
754 the specified time and the time set by @var{force_key_frames}.
756 @item segment_times @var{times}
757 Specify a list of split points. @var{times} contains a list of comma
758 separated duration specifications, in increasing order. See also
759 the @option{segment_time} option.
761 @item segment_frames @var{frames}
762 Specify a list of split video frame numbers. @var{frames} contains a
763 list of comma separated integer numbers, in increasing order.
765 This option specifies to start a new segment whenever a reference
766 stream key frame is found and the sequential number (starting from 0)
767 of the frame is greater or equal to the next value in the list.
769 @item segment_wrap @var{limit}
770 Wrap around segment index once it reaches @var{limit}.
772 @item segment_start_number @var{number}
773 Set the sequence number of the first segment. Defaults to @code{0}.
775 @item reset_timestamps @var{1|0}
776 Reset timestamps at the begin of each segment, so that each segment
777 will start with near-zero timestamps. It is meant to ease the playback
778 of the generated segments. May not work with some combinations of
779 muxers/codecs. It is set to @code{0} by default.
781 @item initial_offset @var{offset}
782 Specify timestamp offset to apply to the output packet timestamps. The
783 argument must be a time duration specification, and defaults to 0.
790 To remux the content of file @file{in.mkv} to a list of segments
791 @file{out-000.nut}, @file{out-001.nut}, etc., and write the list of
792 generated segments to @file{out.list}:
794 ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.list out%03d.nut
798 As the example above, but segment the input file according to the split
799 points specified by the @var{segment_times} option:
801 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
805 As the example above, but use the @command{ffmpeg} @option{force_key_frames}
806 option to force key frames in the input at the specified location, together
807 with the segment option @option{segment_time_delta} to account for
808 possible roundings operated when setting key frame times.
810 ffmpeg -i in.mkv -force_key_frames 1,2,3,5,8,13,21 -codec:v mpeg4 -codec:a pcm_s16le -map 0 \
811 -f segment -segment_list out.csv -segment_times 1,2,3,5,8,13,21 -segment_time_delta 0.05 out%03d.nut
813 In order to force key frames on the input file, transcoding is
817 Segment the input file by splitting the input file according to the
818 frame numbers sequence specified with the @option{segment_frames} option:
820 ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.csv -segment_frames 100,200,300,500,800 out%03d.nut
824 To convert the @file{in.mkv} to TS segments using the @code{libx264}
825 and @code{libfaac} encoders:
827 ffmpeg -i in.mkv -map 0 -codec:v libx264 -codec:a libfaac -f ssegment -segment_list out.list out%03d.ts
831 Segment the input file, and create an M3U8 live playlist (can be used
834 ffmpeg -re -i in.mkv -codec copy -map 0 -f segment -segment_list playlist.m3u8 \
835 -segment_list_flags +live -segment_time 10 out%03d.mkv
841 The tee muxer can be used to write the same data to several files or any
842 other kind of muxer. It can be used, for example, to both stream a video to
843 the network and save it to disk at the same time.
845 It is different from specifying several outputs to the @command{ffmpeg}
846 command-line tool because the audio and video data will be encoded only once
847 with the tee muxer; encoding can be a very expensive process. It is not
848 useful when using the libavformat API directly because it is then possible
849 to feed the same packets to several muxers directly.
851 The slave outputs are specified in the file name given to the muxer,
852 separated by '|'. If any of the slave name contains the '|' separator,
853 leading or trailing spaces or any special character, it must be
854 escaped (see the ``Quoting and escaping'' section in the ffmpeg-utils
857 Muxer options can be specified for each slave by prepending them as a list of
858 @var{key}=@var{value} pairs separated by ':', between square brackets. If
859 the options values contain a special character or the ':' separator, they
860 must be escaped; note that this is a second level escaping.
862 The following special options are also recognized:
865 Specify the format name. Useful if it cannot be guessed from the
868 @item bsfs[/@var{spec}]
869 Specify a list of bitstream filters to apply to the specified
870 output. It is possible to specify to which streams a given bitstream
871 filter applies, by appending a stream specifier to the option
872 separated by @code{/}. If the stream specifier is not specified, the
873 bistream filters will be applied to all streams in the output.
875 Several bitstream filters can be specified, separated by ",".
878 Select the streams that should be mapped to the slave output,
879 specified by a stream specifier. If not specified, this defaults to
880 all the input streams.
883 Some examples follow.
886 Encode something and both archive it in a WebM file and stream it
887 as MPEG-TS over UDP (the streams need to be explicitly mapped):
889 ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a
890 "archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/"
894 Use @command{ffmpeg} to encode the input, and send the output
895 to three different destinations. The @code{dump_extra} bitstream
896 filter is used to add extradata information to all the output video
897 keyframes packets, as requested by the MPEG-TS format. The select
898 option is applied to @file{out.aac} in order to make it contain only
901 ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac -strict experimental
902 -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=a]out.aac"
906 Note: some codecs may need different options depending on the output format;
907 the auto-detection of this can not work with the tee muxer. The main example
908 is the @option{global_header} flag.