Commit | Line | Data |
---|---|---|
2ba45a60 DM |
1 | @chapter Muxers |
2 | @c man begin MUXERS | |
3 | ||
4 | Muxers are configured elements in FFmpeg which allow writing | |
5 | multimedia streams to a particular type of file. | |
6 | ||
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}. | |
10 | ||
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}}. | |
15 | ||
16 | The option @code{-formats} of the ff* tools will display the list of | |
17 | enabled muxers. | |
18 | ||
19 | A description of some of the currently available muxers follows. | |
20 | ||
21 | @anchor{aiff} | |
22 | @section aiff | |
23 | ||
24 | Audio Interchange File Format muxer. | |
25 | ||
26 | @subsection Options | |
27 | ||
28 | It accepts the following options: | |
29 | ||
30 | @table @option | |
31 | @item write_id3v2 | |
32 | Enable ID3v2 tags writing when set to 1. Default is 0 (disabled). | |
33 | ||
34 | @item id3v2_version | |
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. | |
37 | ||
38 | @end table | |
39 | ||
40 | @anchor{crc} | |
41 | @section crc | |
42 | ||
43 | CRC (Cyclic Redundancy Check) testing format. | |
44 | ||
45 | This muxer computes and prints the Adler-32 CRC of all the input audio | |
46 | and video frames. By default audio frames are converted to signed | |
47 | 16-bit raw audio and video frames to raw video before computing the | |
48 | CRC. | |
49 | ||
50 | The output of the muxer consists of a single line of the form: | |
51 | CRC=0x@var{CRC}, where @var{CRC} is a hexadecimal number 0-padded to | |
52 | 8 digits containing the CRC for all the decoded input frames. | |
53 | ||
54 | See also the @ref{framecrc} muxer. | |
55 | ||
56 | @subsection Examples | |
57 | ||
58 | For example to compute the CRC of the input, and store it in the file | |
59 | @file{out.crc}: | |
60 | @example | |
61 | ffmpeg -i INPUT -f crc out.crc | |
62 | @end example | |
63 | ||
64 | You can print the CRC to stdout with the command: | |
65 | @example | |
66 | ffmpeg -i INPUT -f crc - | |
67 | @end example | |
68 | ||
69 | You can select the output format of each frame with @command{ffmpeg} by | |
70 | specifying the audio and video codec and format. For example to | |
71 | compute the CRC of the input audio converted to PCM unsigned 8-bit | |
72 | and the input video converted to MPEG-2 video, use the command: | |
73 | @example | |
74 | ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f crc - | |
75 | @end example | |
76 | ||
77 | @anchor{framecrc} | |
78 | @section framecrc | |
79 | ||
80 | Per-packet CRC (Cyclic Redundancy Check) testing format. | |
81 | ||
82 | This muxer computes and prints the Adler-32 CRC for each audio | |
83 | and video packet. By default audio frames are converted to signed | |
84 | 16-bit raw audio and video frames to raw video before computing the | |
85 | CRC. | |
86 | ||
87 | The output of the muxer consists of a line for each audio and video | |
88 | packet of the form: | |
89 | @example | |
90 | @var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, 0x@var{CRC} | |
91 | @end example | |
92 | ||
93 | @var{CRC} is a hexadecimal number 0-padded to 8 digits containing the | |
94 | CRC of the packet. | |
95 | ||
96 | @subsection Examples | |
97 | ||
98 | For example to compute the CRC of the audio and video frames in | |
99 | @file{INPUT}, converted to raw audio and video packets, and store it | |
100 | in the file @file{out.crc}: | |
101 | @example | |
102 | ffmpeg -i INPUT -f framecrc out.crc | |
103 | @end example | |
104 | ||
105 | To print the information to stdout, use the command: | |
106 | @example | |
107 | ffmpeg -i INPUT -f framecrc - | |
108 | @end example | |
109 | ||
110 | With @command{ffmpeg}, you can select the output format to which the | |
111 | audio and video frames are encoded before computing the CRC for each | |
112 | packet by specifying the audio and video codec. For example, to | |
113 | compute the CRC of each decoded input audio frame converted to PCM | |
114 | unsigned 8-bit and of each decoded input video frame converted to | |
115 | MPEG-2 video, use the command: | |
116 | @example | |
117 | ffmpeg -i INPUT -c:a pcm_u8 -c:v mpeg2video -f framecrc - | |
118 | @end example | |
119 | ||
120 | See also the @ref{crc} muxer. | |
121 | ||
122 | @anchor{framemd5} | |
123 | @section framemd5 | |
124 | ||
125 | Per-packet MD5 testing format. | |
126 | ||
127 | This muxer computes and prints the MD5 hash for each audio | |
128 | and video packet. By default audio frames are converted to signed | |
129 | 16-bit raw audio and video frames to raw video before computing the | |
130 | hash. | |
131 | ||
132 | The output of the muxer consists of a line for each audio and video | |
133 | packet of the form: | |
134 | @example | |
135 | @var{stream_index}, @var{packet_dts}, @var{packet_pts}, @var{packet_duration}, @var{packet_size}, @var{MD5} | |
136 | @end example | |
137 | ||
138 | @var{MD5} is a hexadecimal number representing the computed MD5 hash | |
139 | for the packet. | |
140 | ||
141 | @subsection Examples | |
142 | ||
143 | For example to compute the MD5 of the audio and video frames in | |
144 | @file{INPUT}, converted to raw audio and video packets, and store it | |
145 | in the file @file{out.md5}: | |
146 | @example | |
147 | ffmpeg -i INPUT -f framemd5 out.md5 | |
148 | @end example | |
149 | ||
150 | To print the information to stdout, use the command: | |
151 | @example | |
152 | ffmpeg -i INPUT -f framemd5 - | |
153 | @end example | |
154 | ||
155 | See also the @ref{md5} muxer. | |
156 | ||
157 | @anchor{gif} | |
158 | @section gif | |
159 | ||
160 | Animated GIF muxer. | |
161 | ||
162 | It accepts the following options: | |
163 | ||
164 | @table @option | |
165 | @item loop | |
166 | Set the number of times to loop the output. Use @code{-1} for no loop, @code{0} | |
167 | for looping indefinitely (default). | |
168 | ||
169 | @item final_delay | |
170 | Force the delay (expressed in centiseconds) after the last frame. Each frame | |
171 | ends with a delay until the next frame. The default is @code{-1}, which is a | |
172 | special value to tell the muxer to re-use the previous delay. In case of a | |
173 | loop, you might want to customize this value to mark a pause for instance. | |
174 | @end table | |
175 | ||
176 | For example, to encode a gif looping 10 times, with a 5 seconds delay between | |
177 | the loops: | |
178 | @example | |
179 | ffmpeg -i INPUT -loop 10 -final_delay 500 out.gif | |
180 | @end example | |
181 | ||
182 | Note 1: if you wish to extract the frames in separate GIF files, you need to | |
183 | force the @ref{image2} muxer: | |
184 | @example | |
185 | ffmpeg -i INPUT -c:v gif -f image2 "out%d.gif" | |
186 | @end example | |
187 | ||
188 | Note 2: the GIF format has a very small time base: the delay between two frames | |
189 | can not be smaller than one centi second. | |
190 | ||
191 | @anchor{hls} | |
192 | @section hls | |
193 | ||
194 | Apple HTTP Live Streaming muxer that segments MPEG-TS according to | |
195 | the HTTP Live Streaming (HLS) specification. | |
196 | ||
197 | It creates a playlist file and numbered segment files. The output | |
198 | filename specifies the playlist filename; the segment filenames | |
199 | receive the same basename as the playlist, a sequential number and | |
200 | a .ts extension. | |
201 | ||
202 | For example, to convert an input file with @command{ffmpeg}: | |
203 | @example | |
204 | ffmpeg -i in.nut out.m3u8 | |
205 | @end example | |
206 | ||
207 | See also the @ref{segment} muxer, which provides a more generic and | |
208 | flexible implementation of a segmenter, and can be used to perform HLS | |
209 | segmentation. | |
210 | ||
211 | @subsection Options | |
212 | ||
213 | This muxer supports the following options: | |
214 | ||
215 | @table @option | |
216 | @item hls_time @var{seconds} | |
217 | Set the segment length in seconds. Default value is 2. | |
218 | ||
219 | @item hls_list_size @var{size} | |
220 | Set the maximum number of playlist entries. If set to 0 the list file | |
221 | will contain all the segments. Default value is 5. | |
222 | ||
223 | @item hls_wrap @var{wrap} | |
224 | Set the number after which the segment filename number (the number | |
225 | specified in each segment file) wraps. If set to 0 the number will be | |
226 | never wrapped. Default value is 0. | |
227 | ||
228 | This option is useful to avoid to fill the disk with many segment | |
229 | files, and limits the maximum number of segment files written to disk | |
230 | to @var{wrap}. | |
231 | ||
232 | @item start_number @var{number} | |
233 | Start the playlist sequence number from @var{number}. Default value is | |
234 | 0. | |
235 | ||
236 | @item hls_base_url @var{baseurl} | |
237 | Append @var{baseurl} to every entry in the playlist. | |
238 | Useful to generate playlists with absolute paths. | |
239 | ||
240 | Note that the playlist sequence number must be unique for each segment | |
241 | and it is not to be confused with the segment filename sequence number | |
242 | which can be cyclic, for example if the @option{wrap} option is | |
243 | specified. | |
244 | @end table | |
245 | ||
246 | @anchor{ico} | |
247 | @section ico | |
248 | ||
249 | ICO file muxer. | |
250 | ||
251 | Microsoft's icon file format (ICO) has some strict limitations that should be noted: | |
252 | ||
253 | @itemize | |
254 | @item | |
255 | Size cannot exceed 256 pixels in any dimension | |
256 | ||
257 | @item | |
258 | Only BMP and PNG images can be stored | |
259 | ||
260 | @item | |
261 | If a BMP image is used, it must be one of the following pixel formats: | |
262 | @example | |
263 | BMP Bit Depth FFmpeg Pixel Format | |
264 | 1bit pal8 | |
265 | 4bit pal8 | |
266 | 8bit pal8 | |
267 | 16bit rgb555le | |
268 | 24bit bgr24 | |
269 | 32bit bgra | |
270 | @end example | |
271 | ||
272 | @item | |
273 | If a BMP image is used, it must use the BITMAPINFOHEADER DIB header | |
274 | ||
275 | @item | |
276 | If a PNG image is used, it must use the rgba pixel format | |
277 | @end itemize | |
278 | ||
279 | @anchor{image2} | |
280 | @section image2 | |
281 | ||
282 | Image file muxer. | |
283 | ||
284 | The image file muxer writes video frames to image files. | |
285 | ||
286 | The output filenames are specified by a pattern, which can be used to | |
287 | produce sequentially numbered series of files. | |
288 | The pattern may contain the string "%d" or "%0@var{N}d", this string | |
289 | specifies the position of the characters representing a numbering in | |
290 | the filenames. If the form "%0@var{N}d" is used, the string | |
291 | representing the number in each filename is 0-padded to @var{N} | |
292 | digits. The literal character '%' can be specified in the pattern with | |
293 | the string "%%". | |
294 | ||
295 | If the pattern contains "%d" or "%0@var{N}d", the first filename of | |
296 | the file list specified will contain the number 1, all the following | |
297 | numbers will be sequential. | |
298 | ||
299 | The pattern may contain a suffix which is used to automatically | |
300 | determine the format of the image files to write. | |
301 | ||
302 | For example the pattern "img-%03d.bmp" will specify a sequence of | |
303 | filenames of the form @file{img-001.bmp}, @file{img-002.bmp}, ..., | |
304 | @file{img-010.bmp}, etc. | |
305 | The pattern "img%%-%d.jpg" will specify a sequence of filenames of the | |
306 | form @file{img%-1.jpg}, @file{img%-2.jpg}, ..., @file{img%-10.jpg}, | |
307 | etc. | |
308 | ||
309 | @subsection Examples | |
310 | ||
311 | The following example shows how to use @command{ffmpeg} for creating a | |
312 | sequence of files @file{img-001.jpeg}, @file{img-002.jpeg}, ..., | |
313 | taking one image every second from the input video: | |
314 | @example | |
315 | ffmpeg -i in.avi -vsync 1 -r 1 -f image2 'img-%03d.jpeg' | |
316 | @end example | |
317 | ||
318 | Note that with @command{ffmpeg}, if the format is not specified with the | |
319 | @code{-f} option and the output filename specifies an image file | |
320 | format, the image2 muxer is automatically selected, so the previous | |
321 | command can be written as: | |
322 | @example | |
323 | ffmpeg -i in.avi -vsync 1 -r 1 'img-%03d.jpeg' | |
324 | @end example | |
325 | ||
326 | Note also that the pattern must not necessarily contain "%d" or | |
327 | "%0@var{N}d", for example to create a single image file | |
328 | @file{img.jpeg} from the input video you can employ the command: | |
329 | @example | |
330 | ffmpeg -i in.avi -f image2 -frames:v 1 img.jpeg | |
331 | @end example | |
332 | ||
333 | The @option{strftime} option allows you to expand the filename with | |
334 | date and time information. Check the documentation of | |
335 | the @code{strftime()} function for the syntax. | |
336 | ||
337 | For example to generate image files from the @code{strftime()} | |
338 | "%Y-%m-%d_%H-%M-%S" pattern, the following @command{ffmpeg} command | |
339 | can be used: | |
340 | @example | |
341 | ffmpeg -f v4l2 -r 1 -i /dev/video0 -f image2 -strftime 1 "%Y-%m-%d_%H-%M-%S.jpg" | |
342 | @end example | |
343 | ||
344 | @subsection Options | |
345 | ||
346 | @table @option | |
347 | @item start_number | |
348 | Start the sequence from the specified number. Default value is 1. Must | |
349 | be a non-negative number. | |
350 | ||
351 | @item update | |
352 | If set to 1, the filename will always be interpreted as just a | |
353 | filename, not a pattern, and the corresponding file will be continuously | |
354 | overwritten with new images. Default value is 0. | |
355 | ||
356 | @item strftime | |
357 | If set to 1, expand the filename with date and time information from | |
358 | @code{strftime()}. Default value is 0. | |
359 | @end table | |
360 | ||
361 | The image muxer supports the .Y.U.V image file format. This format is | |
362 | special in that that each image frame consists of three files, for | |
363 | each of the YUV420P components. To read or write this image file format, | |
364 | specify the name of the '.Y' file. The muxer will automatically open the | |
365 | '.U' and '.V' files as required. | |
366 | ||
367 | @section matroska | |
368 | ||
369 | Matroska container muxer. | |
370 | ||
371 | This muxer implements the matroska and webm container specs. | |
372 | ||
373 | @subsection Metadata | |
374 | ||
375 | The recognized metadata settings in this muxer are: | |
376 | ||
377 | @table @option | |
378 | @item title | |
379 | Set title name provided to a single track. | |
380 | ||
381 | @item language | |
382 | Specify the language of the track in the Matroska languages form. | |
383 | ||
384 | The language can be either the 3 letters bibliographic ISO-639-2 (ISO | |
385 | 639-2/B) form (like "fre" for French), or a language code mixed with a | |
386 | country code for specialities in languages (like "fre-ca" for Canadian | |
387 | French). | |
388 | ||
389 | @item stereo_mode | |
390 | Set stereo 3D video layout of two views in a single video track. | |
391 | ||
392 | The following values are recognized: | |
393 | @table @samp | |
394 | @item mono | |
395 | video is not stereo | |
396 | @item left_right | |
397 | Both views are arranged side by side, Left-eye view is on the left | |
398 | @item bottom_top | |
399 | Both views are arranged in top-bottom orientation, Left-eye view is at bottom | |
400 | @item top_bottom | |
401 | Both views are arranged in top-bottom orientation, Left-eye view is on top | |
402 | @item checkerboard_rl | |
403 | Each view is arranged in a checkerboard interleaved pattern, Left-eye view being first | |
404 | @item checkerboard_lr | |
405 | Each view is arranged in a checkerboard interleaved pattern, Right-eye view being first | |
406 | @item row_interleaved_rl | |
407 | Each view is constituted by a row based interleaving, Right-eye view is first row | |
408 | @item row_interleaved_lr | |
409 | Each view is constituted by a row based interleaving, Left-eye view is first row | |
410 | @item col_interleaved_rl | |
411 | Both views are arranged in a column based interleaving manner, Right-eye view is first column | |
412 | @item col_interleaved_lr | |
413 | Both views are arranged in a column based interleaving manner, Left-eye view is first column | |
414 | @item anaglyph_cyan_red | |
415 | All frames are in anaglyph format viewable through red-cyan filters | |
416 | @item right_left | |
417 | Both views are arranged side by side, Right-eye view is on the left | |
418 | @item anaglyph_green_magenta | |
419 | All frames are in anaglyph format viewable through green-magenta filters | |
420 | @item block_lr | |
421 | Both eyes laced in one Block, Left-eye view is first | |
422 | @item block_rl | |
423 | Both eyes laced in one Block, Right-eye view is first | |
424 | @end table | |
425 | @end table | |
426 | ||
427 | For example a 3D WebM clip can be created using the following command line: | |
428 | @example | |
429 | ffmpeg -i sample_left_right_clip.mpg -an -c:v libvpx -metadata stereo_mode=left_right -y stereo_clip.webm | |
430 | @end example | |
431 | ||
432 | @subsection Options | |
433 | ||
434 | This muxer supports the following options: | |
435 | ||
436 | @table @option | |
437 | @item reserve_index_space | |
438 | By default, this muxer writes the index for seeking (called cues in Matroska | |
439 | terms) at the end of the file, because it cannot know in advance how much space | |
440 | to leave for the index at the beginning of the file. However for some use cases | |
441 | -- e.g. streaming where seeking is possible but slow -- it is useful to put the | |
442 | index at the beginning of the file. | |
443 | ||
444 | If this option is set to a non-zero value, the muxer will reserve a given amount | |
445 | of space in the file header and then try to write the cues there when the muxing | |
446 | finishes. If the available space does not suffice, muxing will fail. A safe size | |
447 | for most use cases should be about 50kB per hour of video. | |
448 | ||
449 | Note that cues are only written if the output is seekable and this option will | |
450 | have no effect if it is not. | |
451 | @end table | |
452 | ||
453 | @anchor{md5} | |
454 | @section md5 | |
455 | ||
456 | MD5 testing format. | |
457 | ||
458 | This muxer computes and prints the MD5 hash of all the input audio | |
459 | and video frames. By default audio frames are converted to signed | |
460 | 16-bit raw audio and video frames to raw video before computing the | |
461 | hash. | |
462 | ||
463 | The output of the muxer consists of a single line of the form: | |
464 | MD5=@var{MD5}, where @var{MD5} is a hexadecimal number representing | |
465 | the computed MD5 hash. | |
466 | ||
467 | For example to compute the MD5 hash of the input converted to raw | |
468 | audio and video, and store it in the file @file{out.md5}: | |
469 | @example | |
470 | ffmpeg -i INPUT -f md5 out.md5 | |
471 | @end example | |
472 | ||
473 | You can print the MD5 to stdout with the command: | |
474 | @example | |
475 | ffmpeg -i INPUT -f md5 - | |
476 | @end example | |
477 | ||
478 | See also the @ref{framemd5} muxer. | |
479 | ||
480 | @section mov, mp4, ismv | |
481 | ||
482 | MOV/MP4/ISMV (Smooth Streaming) muxer. | |
483 | ||
484 | The mov/mp4/ismv muxer supports fragmentation. Normally, a MOV/MP4 | |
485 | file has all the metadata about all packets stored in one location | |
486 | (written at the end of the file, it can be moved to the start for | |
487 | better playback by adding @var{faststart} to the @var{movflags}, or | |
488 | using the @command{qt-faststart} tool). A fragmented | |
489 | file consists of a number of fragments, where packets and metadata | |
490 | about these packets are stored together. Writing a fragmented | |
491 | file has the advantage that the file is decodable even if the | |
492 | writing is interrupted (while a normal MOV/MP4 is undecodable if | |
493 | it is not properly finished), and it requires less memory when writing | |
494 | very long files (since writing normal MOV/MP4 files stores info about | |
495 | every single packet in memory until the file is closed). The downside | |
496 | is that it is less compatible with other applications. | |
497 | ||
498 | @subsection Options | |
499 | ||
500 | Fragmentation is enabled by setting one of the AVOptions that define | |
501 | how to cut the file into fragments: | |
502 | ||
503 | @table @option | |
504 | @item -moov_size @var{bytes} | |
505 | Reserves space for the moov atom at the beginning of the file instead of placing the | |
506 | moov atom at the end. If the space reserved is insufficient, muxing will fail. | |
507 | @item -movflags frag_keyframe | |
508 | Start a new fragment at each video keyframe. | |
509 | @item -frag_duration @var{duration} | |
510 | Create fragments that are @var{duration} microseconds long. | |
511 | @item -frag_size @var{size} | |
512 | Create fragments that contain up to @var{size} bytes of payload data. | |
513 | @item -movflags frag_custom | |
514 | Allow the caller to manually choose when to cut fragments, by | |
515 | calling @code{av_write_frame(ctx, NULL)} to write a fragment with | |
516 | the packets written so far. (This is only useful with other | |
517 | applications integrating libavformat, not from @command{ffmpeg}.) | |
518 | @item -min_frag_duration @var{duration} | |
519 | Don't create fragments that are shorter than @var{duration} microseconds long. | |
520 | @end table | |
521 | ||
522 | If more than one condition is specified, fragments are cut when | |
523 | one of the specified conditions is fulfilled. The exception to this is | |
524 | @code{-min_frag_duration}, which has to be fulfilled for any of the other | |
525 | conditions to apply. | |
526 | ||
527 | Additionally, the way the output file is written can be adjusted | |
528 | through a few other options: | |
529 | ||
530 | @table @option | |
531 | @item -movflags empty_moov | |
532 | Write an initial moov atom directly at the start of the file, without | |
533 | describing any samples in it. Generally, an mdat/moov pair is written | |
534 | at the start of the file, as a normal MOV/MP4 file, containing only | |
535 | a short portion of the file. With this option set, there is no initial | |
536 | mdat atom, and the moov atom only describes the tracks but has | |
537 | a zero duration. | |
538 | ||
539 | Files written with this option set do not work in QuickTime. | |
540 | This option is implicitly set when writing ismv (Smooth Streaming) files. | |
541 | @item -movflags separate_moof | |
542 | Write a separate moof (movie fragment) atom for each track. Normally, | |
543 | packets for all tracks are written in a moof atom (which is slightly | |
544 | more efficient), but with this option set, the muxer writes one moof/mdat | |
545 | pair for each track, making it easier to separate tracks. | |
546 | ||
547 | This option is implicitly set when writing ismv (Smooth Streaming) files. | |
548 | @item -movflags faststart | |
549 | Run a second pass moving the index (moov atom) to the beginning of the file. | |
550 | This operation can take a while, and will not work in various situations such | |
551 | as fragmented output, thus it is not enabled by default. | |
552 | @item -movflags rtphint | |
553 | Add RTP hinting tracks to the output file. | |
554 | @item -movflags disable_chpl | |
555 | Disable Nero chapter markers (chpl atom). Normally, both Nero chapters | |
556 | and a QuickTime chapter track are written to the file. With this option | |
557 | set, only the QuickTime chapter track will be written. Nero chapters can | |
558 | cause failures when the file is reprocessed with certain tagging programs, like | |
559 | mp3Tag 2.61a and iTunes 11.3, most likely other versions are affected as well. | |
560 | @end table | |
561 | ||
562 | @subsection Example | |
563 | ||
564 | Smooth Streaming content can be pushed in real time to a publishing | |
565 | point on IIS with this muxer. Example: | |
566 | @example | |
567 | ffmpeg -re @var{<normal input/transcoding options>} -movflags isml+frag_keyframe -f ismv http://server/publishingpoint.isml/Streams(Encoder1) | |
568 | @end example | |
569 | ||
570 | @section mp3 | |
571 | ||
572 | The MP3 muxer writes a raw MP3 stream with an ID3v2 header at the beginning and | |
573 | optionally an ID3v1 tag at the end. ID3v2.3 and ID3v2.4 are supported, the | |
574 | @code{id3v2_version} option controls which one is used. Setting | |
575 | @code{id3v2_version} to 0 will disable the ID3v2 header completely. The legacy | |
576 | ID3v1 tag is not written by default, but may be enabled with the | |
577 | @code{write_id3v1} option. | |
578 | ||
579 | The muxer may also write a Xing frame at the beginning, which contains the | |
580 | number of frames in the file. It is useful for computing duration of VBR files. | |
581 | The Xing frame is written if the output stream is seekable and if the | |
582 | @code{write_xing} option is set to 1 (the default). | |
583 | ||
584 | The muxer supports writing ID3v2 attached pictures (APIC frames). The pictures | |
585 | are supplied to the muxer in form of a video stream with a single packet. There | |
586 | can be any number of those streams, each will correspond to a single APIC frame. | |
587 | The stream metadata tags @var{title} and @var{comment} map to APIC | |
588 | @var{description} and @var{picture type} respectively. See | |
589 | @url{http://id3.org/id3v2.4.0-frames} for allowed picture types. | |
590 | ||
591 | Note that the APIC frames must be written at the beginning, so the muxer will | |
592 | buffer the audio frames until it gets all the pictures. It is therefore advised | |
593 | to provide the pictures as soon as possible to avoid excessive buffering. | |
594 | ||
595 | Examples: | |
596 | ||
597 | Write an mp3 with an ID3v2.3 header and an ID3v1 footer: | |
598 | @example | |
599 | ffmpeg -i INPUT -id3v2_version 3 -write_id3v1 1 out.mp3 | |
600 | @end example | |
601 | ||
602 | To attach a picture to an mp3 file select both the audio and the picture stream | |
603 | with @code{map}: | |
604 | @example | |
605 | ffmpeg -i input.mp3 -i cover.png -c copy -map 0 -map 1 | |
606 | -metadata:s:v title="Album cover" -metadata:s:v comment="Cover (Front)" out.mp3 | |
607 | @end example | |
608 | ||
609 | Write a "clean" MP3 without any extra features: | |
610 | @example | |
611 | ffmpeg -i input.wav -write_xing 0 -id3v2_version 0 out.mp3 | |
612 | @end example | |
613 | ||
614 | @section mpegts | |
615 | ||
616 | MPEG transport stream muxer. | |
617 | ||
618 | This muxer implements ISO 13818-1 and part of ETSI EN 300 468. | |
619 | ||
620 | The recognized metadata settings in mpegts muxer are @code{service_provider} | |
621 | and @code{service_name}. If they are not set the default for | |
622 | @code{service_provider} is "FFmpeg" and the default for | |
623 | @code{service_name} is "Service01". | |
624 | ||
625 | @subsection Options | |
626 | ||
627 | The muxer options are: | |
628 | ||
629 | @table @option | |
630 | @item -mpegts_original_network_id @var{number} | |
631 | Set the original_network_id (default 0x0001). This is unique identifier | |
632 | of a network in DVB. Its main use is in the unique identification of a | |
633 | service through the path Original_Network_ID, Transport_Stream_ID. | |
634 | @item -mpegts_transport_stream_id @var{number} | |
635 | Set the transport_stream_id (default 0x0001). This identifies a | |
636 | transponder in DVB. | |
637 | @item -mpegts_service_id @var{number} | |
638 | Set the service_id (default 0x0001) also known as program in DVB. | |
639 | @item -mpegts_pmt_start_pid @var{number} | |
640 | Set the first PID for PMT (default 0x1000, max 0x1f00). | |
641 | @item -mpegts_start_pid @var{number} | |
642 | Set the first PID for data packets (default 0x0100, max 0x0f00). | |
643 | @item -mpegts_m2ts_mode @var{number} | |
644 | Enable m2ts mode if set to 1. Default value is -1 which disables m2ts mode. | |
645 | @item -muxrate @var{number} | |
646 | Set a constant muxrate (default VBR). | |
647 | @item -pcr_period @var{numer} | |
648 | Override the default PCR retransmission time (default 20ms), ignored | |
649 | if variable muxrate is selected. | |
650 | @item -pes_payload_size @var{number} | |
651 | Set minimum PES packet payload in bytes. | |
652 | @item -mpegts_flags @var{flags} | |
653 | Set flags (see below). | |
654 | @item -mpegts_copyts @var{number} | |
655 | Preserve original timestamps, if value is set to 1. Default value is -1, which | |
656 | results in shifting timestamps so that they start from 0. | |
657 | @item -tables_version @var{number} | |
658 | Set PAT, PMT and SDT version (default 0, valid values are from 0 to 31, inclusively). | |
659 | This option allows updating stream structure so that standard consumer may | |
660 | detect the change. To do so, reopen output AVFormatContext (in case of API | |
661 | usage) or restart ffmpeg instance, cyclically changing tables_version value: | |
662 | @example | |
663 | ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111 | |
664 | ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111 | |
665 | ... | |
666 | ffmpeg -i source3.ts -codec copy -f mpegts -tables_version 31 udp://1.1.1.1:1111 | |
667 | ffmpeg -i source1.ts -codec copy -f mpegts -tables_version 0 udp://1.1.1.1:1111 | |
668 | ffmpeg -i source2.ts -codec copy -f mpegts -tables_version 1 udp://1.1.1.1:1111 | |
669 | ... | |
670 | @end example | |
671 | @end table | |
672 | ||
673 | Option mpegts_flags may take a set of such flags: | |
674 | ||
675 | @table @option | |
676 | @item resend_headers | |
677 | Reemit PAT/PMT before writing the next packet. | |
678 | @item latm | |
679 | Use LATM packetization for AAC. | |
680 | @end table | |
681 | ||
682 | @subsection Example | |
683 | ||
684 | @example | |
685 | ffmpeg -i file.mpg -c copy \ | |
686 | -mpegts_original_network_id 0x1122 \ | |
687 | -mpegts_transport_stream_id 0x3344 \ | |
688 | -mpegts_service_id 0x5566 \ | |
689 | -mpegts_pmt_start_pid 0x1500 \ | |
690 | -mpegts_start_pid 0x150 \ | |
691 | -metadata service_provider="Some provider" \ | |
692 | -metadata service_name="Some Channel" \ | |
693 | -y out.ts | |
694 | @end example | |
695 | ||
696 | @section null | |
697 | ||
698 | Null muxer. | |
699 | ||
700 | This muxer does not generate any output file, it is mainly useful for | |
701 | testing or benchmarking purposes. | |
702 | ||
703 | For example to benchmark decoding with @command{ffmpeg} you can use the | |
704 | command: | |
705 | @example | |
706 | ffmpeg -benchmark -i INPUT -f null out.null | |
707 | @end example | |
708 | ||
709 | Note that the above command does not read or write the @file{out.null} | |
710 | file, but specifying the output file is required by the @command{ffmpeg} | |
711 | syntax. | |
712 | ||
713 | Alternatively you can write the command as: | |
714 | @example | |
715 | ffmpeg -benchmark -i INPUT -f null - | |
716 | @end example | |
717 | ||
718 | @section nut | |
719 | ||
720 | @table @option | |
721 | @item -syncpoints @var{flags} | |
722 | Change the syncpoint usage in nut: | |
723 | @table @option | |
724 | @item @var{default} use the normal low-overhead seeking aids. | |
725 | @item @var{none} do not use the syncpoints at all, reducing the overhead but making the stream non-seekable; | |
726 | Use of this option is not recommended, as the resulting files are very damage | |
727 | sensitive and seeking is not possible. Also in general the overhead from | |
728 | syncpoints is negligible. Note, -@code{write_index} 0 can be used to disable | |
729 | all growing data tables, allowing to mux endless streams with limited memory | |
730 | and wihout these disadvantages. | |
731 | @item @var{timestamped} extend the syncpoint with a wallclock field. | |
732 | @end table | |
733 | The @var{none} and @var{timestamped} flags are experimental. | |
734 | @item -write_index @var{bool} | |
735 | Write index at the end, the default is to write an index. | |
736 | @end table | |
737 | ||
738 | @example | |
739 | ffmpeg -i INPUT -f_strict experimental -syncpoints none - | processor | |
740 | @end example | |
741 | ||
742 | @section ogg | |
743 | ||
744 | Ogg container muxer. | |
745 | ||
746 | @table @option | |
747 | @item -page_duration @var{duration} | |
748 | Preferred page duration, in microseconds. The muxer will attempt to create | |
749 | pages that are approximately @var{duration} microseconds long. This allows the | |
750 | user to compromise between seek granularity and container overhead. The default | |
751 | is 1 second. A value of 0 will fill all segments, making pages as large as | |
752 | possible. A value of 1 will effectively use 1 packet-per-page in most | |
753 | situations, giving a small seek granularity at the cost of additional container | |
754 | overhead. | |
755 | @end table | |
756 | ||
757 | @anchor{segment} | |
758 | @section segment, stream_segment, ssegment | |
759 | ||
760 | Basic stream segmenter. | |
761 | ||
762 | This muxer outputs streams to a number of separate files of nearly | |
763 | fixed duration. Output filename pattern can be set in a fashion similar to | |
764 | @ref{image2}. | |
765 | ||
766 | @code{stream_segment} is a variant of the muxer used to write to | |
767 | streaming output formats, i.e. which do not require global headers, | |
768 | and is recommended for outputting e.g. to MPEG transport stream segments. | |
769 | @code{ssegment} is a shorter alias for @code{stream_segment}. | |
770 | ||
771 | Every segment starts with a keyframe of the selected reference stream, | |
772 | which is set through the @option{reference_stream} option. | |
773 | ||
774 | Note that if you want accurate splitting for a video file, you need to | |
775 | make the input key frames correspond to the exact splitting times | |
776 | expected by the segmenter, or the segment muxer will start the new | |
777 | segment with the key frame found next after the specified start | |
778 | time. | |
779 | ||
780 | The segment muxer works best with a single constant frame rate video. | |
781 | ||
782 | Optionally it can generate a list of the created segments, by setting | |
783 | the option @var{segment_list}. The list type is specified by the | |
784 | @var{segment_list_type} option. The entry filenames in the segment | |
785 | list are set by default to the basename of the corresponding segment | |
786 | files. | |
787 | ||
788 | See also the @ref{hls} muxer, which provides a more specific | |
789 | implementation for HLS segmentation. | |
790 | ||
791 | @subsection Options | |
792 | ||
793 | The segment muxer supports the following options: | |
794 | ||
795 | @table @option | |
796 | @item reference_stream @var{specifier} | |
797 | Set the reference stream, as specified by the string @var{specifier}. | |
798 | If @var{specifier} is set to @code{auto}, the reference is chosen | |
799 | automatically. Otherwise it must be a stream specifier (see the ``Stream | |
800 | specifiers'' chapter in the ffmpeg manual) which specifies the | |
801 | reference stream. The default value is @code{auto}. | |
802 | ||
803 | @item segment_format @var{format} | |
804 | Override the inner container format, by default it is guessed by the filename | |
805 | extension. | |
806 | ||
807 | @item segment_format_options @var{options_list} | |
808 | Set output format options using a :-separated list of key=value | |
809 | parameters. Values containing the @code{:} special character must be | |
810 | escaped. | |
811 | ||
812 | @item segment_list @var{name} | |
813 | Generate also a listfile named @var{name}. If not specified no | |
814 | listfile is generated. | |
815 | ||
816 | @item segment_list_flags @var{flags} | |
817 | Set flags affecting the segment list generation. | |
818 | ||
819 | It currently supports the following flags: | |
820 | @table @samp | |
821 | @item cache | |
822 | Allow caching (only affects M3U8 list files). | |
823 | ||
824 | @item live | |
825 | Allow live-friendly file generation. | |
826 | @end table | |
827 | ||
828 | @item segment_list_type @var{type} | |
829 | Select the listing format. | |
830 | @table @option | |
831 | @item @var{flat} use a simple flat list of entries. | |
832 | @item @var{hls} use a m3u8-like structure. | |
833 | @end table | |
834 | ||
835 | @item segment_list_size @var{size} | |
836 | Update the list file so that it contains at most @var{size} | |
837 | segments. If 0 the list file will contain all the segments. Default | |
838 | value is 0. | |
839 | ||
840 | @item segment_list_entry_prefix @var{prefix} | |
841 | Prepend @var{prefix} to each entry. Useful to generate absolute paths. | |
842 | By default no prefix is applied. | |
843 | ||
844 | The following values are recognized: | |
845 | @table @samp | |
846 | @item flat | |
847 | Generate a flat list for the created segments, one segment per line. | |
848 | ||
849 | @item csv, ext | |
850 | Generate a list for the created segments, one segment per line, | |
851 | each line matching the format (comma-separated values): | |
852 | @example | |
853 | @var{segment_filename},@var{segment_start_time},@var{segment_end_time} | |
854 | @end example | |
855 | ||
856 | @var{segment_filename} is the name of the output file generated by the | |
857 | muxer according to the provided pattern. CSV escaping (according to | |
858 | RFC4180) is applied if required. | |
859 | ||
860 | @var{segment_start_time} and @var{segment_end_time} specify | |
861 | the segment start and end time expressed in seconds. | |
862 | ||
863 | A list file with the suffix @code{".csv"} or @code{".ext"} will | |
864 | auto-select this format. | |
865 | ||
866 | @samp{ext} is deprecated in favor or @samp{csv}. | |
867 | ||
868 | @item ffconcat | |
869 | Generate an ffconcat file for the created segments. The resulting file | |
870 | can be read using the FFmpeg @ref{concat} demuxer. | |
871 | ||
872 | A list file with the suffix @code{".ffcat"} or @code{".ffconcat"} will | |
873 | auto-select this format. | |
874 | ||
875 | @item m3u8 | |
876 | Generate an extended M3U8 file, version 3, compliant with | |
877 | @url{http://tools.ietf.org/id/draft-pantos-http-live-streaming}. | |
878 | ||
879 | A list file with the suffix @code{".m3u8"} will auto-select this format. | |
880 | @end table | |
881 | ||
882 | If not specified the type is guessed from the list file name suffix. | |
883 | ||
884 | @item segment_time @var{time} | |
885 | Set segment duration to @var{time}, the value must be a duration | |
886 | specification. Default value is "2". See also the | |
887 | @option{segment_times} option. | |
888 | ||
889 | Note that splitting may not be accurate, unless you force the | |
890 | reference stream key-frames at the given time. See the introductory | |
891 | notice and the examples below. | |
892 | ||
893 | @item segment_atclocktime @var{1|0} | |
894 | If set to "1" split at regular clock time intervals starting from 00:00 | |
895 | o'clock. The @var{time} value specified in @option{segment_time} is | |
896 | used for setting the length of the splitting interval. | |
897 | ||
898 | For example with @option{segment_time} set to "900" this makes it possible | |
899 | to create files at 12:00 o'clock, 12:15, 12:30, etc. | |
900 | ||
901 | Default value is "0". | |
902 | ||
903 | @item segment_time_delta @var{delta} | |
904 | Specify the accuracy time when selecting the start time for a | |
905 | segment, expressed as a duration specification. Default value is "0". | |
906 | ||
907 | When delta is specified a key-frame will start a new segment if its | |
908 | PTS satisfies the relation: | |
909 | @example | |
910 | PTS >= start_time - time_delta | |
911 | @end example | |
912 | ||
913 | This option is useful when splitting video content, which is always | |
914 | split at GOP boundaries, in case a key frame is found just before the | |
915 | specified split time. | |
916 | ||
917 | In particular may be used in combination with the @file{ffmpeg} option | |
918 | @var{force_key_frames}. The key frame times specified by | |
919 | @var{force_key_frames} may not be set accurately because of rounding | |
920 | issues, with the consequence that a key frame time may result set just | |
921 | before the specified time. For constant frame rate videos a value of | |
922 | 1/(2*@var{frame_rate}) should address the worst case mismatch between | |
923 | the specified time and the time set by @var{force_key_frames}. | |
924 | ||
925 | @item segment_times @var{times} | |
926 | Specify a list of split points. @var{times} contains a list of comma | |
927 | separated duration specifications, in increasing order. See also | |
928 | the @option{segment_time} option. | |
929 | ||
930 | @item segment_frames @var{frames} | |
931 | Specify a list of split video frame numbers. @var{frames} contains a | |
932 | list of comma separated integer numbers, in increasing order. | |
933 | ||
934 | This option specifies to start a new segment whenever a reference | |
935 | stream key frame is found and the sequential number (starting from 0) | |
936 | of the frame is greater or equal to the next value in the list. | |
937 | ||
938 | @item segment_wrap @var{limit} | |
939 | Wrap around segment index once it reaches @var{limit}. | |
940 | ||
941 | @item segment_start_number @var{number} | |
942 | Set the sequence number of the first segment. Defaults to @code{0}. | |
943 | ||
944 | @item reset_timestamps @var{1|0} | |
945 | Reset timestamps at the begin of each segment, so that each segment | |
946 | will start with near-zero timestamps. It is meant to ease the playback | |
947 | of the generated segments. May not work with some combinations of | |
948 | muxers/codecs. It is set to @code{0} by default. | |
949 | ||
950 | @item initial_offset @var{offset} | |
951 | Specify timestamp offset to apply to the output packet timestamps. The | |
952 | argument must be a time duration specification, and defaults to 0. | |
953 | @end table | |
954 | ||
955 | @subsection Examples | |
956 | ||
957 | @itemize | |
958 | @item | |
959 | Remux the content of file @file{in.mkv} to a list of segments | |
960 | @file{out-000.nut}, @file{out-001.nut}, etc., and write the list of | |
961 | generated segments to @file{out.list}: | |
962 | @example | |
963 | ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.list out%03d.nut | |
964 | @end example | |
965 | ||
966 | @item | |
967 | Segment input and set output format options for the output segments: | |
968 | @example | |
969 | ffmpeg -i in.mkv -f segment -segment_time 10 -segment_format_options movflags=+faststart out%03d.mp4 | |
970 | @end example | |
971 | ||
972 | @item | |
973 | Segment the input file according to the split points specified by the | |
974 | @var{segment_times} option: | |
975 | @example | |
976 | 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 | |
977 | @end example | |
978 | ||
979 | @item | |
980 | Use the @command{ffmpeg} @option{force_key_frames} | |
981 | option to force key frames in the input at the specified location, together | |
982 | with the segment option @option{segment_time_delta} to account for | |
983 | possible roundings operated when setting key frame times. | |
984 | @example | |
985 | ffmpeg -i in.mkv -force_key_frames 1,2,3,5,8,13,21 -codec:v mpeg4 -codec:a pcm_s16le -map 0 \ | |
986 | -f segment -segment_list out.csv -segment_times 1,2,3,5,8,13,21 -segment_time_delta 0.05 out%03d.nut | |
987 | @end example | |
988 | In order to force key frames on the input file, transcoding is | |
989 | required. | |
990 | ||
991 | @item | |
992 | Segment the input file by splitting the input file according to the | |
993 | frame numbers sequence specified with the @option{segment_frames} option: | |
994 | @example | |
995 | ffmpeg -i in.mkv -codec copy -map 0 -f segment -segment_list out.csv -segment_frames 100,200,300,500,800 out%03d.nut | |
996 | @end example | |
997 | ||
998 | @item | |
999 | Convert the @file{in.mkv} to TS segments using the @code{libx264} | |
1000 | and @code{libfaac} encoders: | |
1001 | @example | |
1002 | ffmpeg -i in.mkv -map 0 -codec:v libx264 -codec:a libfaac -f ssegment -segment_list out.list out%03d.ts | |
1003 | @end example | |
1004 | ||
1005 | @item | |
1006 | Segment the input file, and create an M3U8 live playlist (can be used | |
1007 | as live HLS source): | |
1008 | @example | |
1009 | ffmpeg -re -i in.mkv -codec copy -map 0 -f segment -segment_list playlist.m3u8 \ | |
1010 | -segment_list_flags +live -segment_time 10 out%03d.mkv | |
1011 | @end example | |
1012 | @end itemize | |
1013 | ||
1014 | @section smoothstreaming | |
1015 | ||
1016 | Smooth Streaming muxer generates a set of files (Manifest, chunks) suitable for serving with conventional web server. | |
1017 | ||
1018 | @table @option | |
1019 | @item window_size | |
1020 | Specify the number of fragments kept in the manifest. Default 0 (keep all). | |
1021 | ||
1022 | @item extra_window_size | |
1023 | Specify the number of fragments kept outside of the manifest before removing from disk. Default 5. | |
1024 | ||
1025 | @item lookahead_count | |
1026 | Specify the number of lookahead fragments. Default 2. | |
1027 | ||
1028 | @item min_frag_duration | |
1029 | Specify the minimum fragment duration (in microseconds). Default 5000000. | |
1030 | ||
1031 | @item remove_at_exit | |
1032 | Specify whether to remove all fragments when finished. Default 0 (do not remove). | |
1033 | ||
1034 | @end table | |
1035 | ||
1036 | @section tee | |
1037 | ||
1038 | The tee muxer can be used to write the same data to several files or any | |
1039 | other kind of muxer. It can be used, for example, to both stream a video to | |
1040 | the network and save it to disk at the same time. | |
1041 | ||
1042 | It is different from specifying several outputs to the @command{ffmpeg} | |
1043 | command-line tool because the audio and video data will be encoded only once | |
1044 | with the tee muxer; encoding can be a very expensive process. It is not | |
1045 | useful when using the libavformat API directly because it is then possible | |
1046 | to feed the same packets to several muxers directly. | |
1047 | ||
1048 | The slave outputs are specified in the file name given to the muxer, | |
1049 | separated by '|'. If any of the slave name contains the '|' separator, | |
1050 | leading or trailing spaces or any special character, it must be | |
1051 | escaped (see @ref{quoting_and_escaping,,the "Quoting and escaping" | |
1052 | section in the ffmpeg-utils(1) manual,ffmpeg-utils}). | |
1053 | ||
1054 | Muxer options can be specified for each slave by prepending them as a list of | |
1055 | @var{key}=@var{value} pairs separated by ':', between square brackets. If | |
1056 | the options values contain a special character or the ':' separator, they | |
1057 | must be escaped; note that this is a second level escaping. | |
1058 | ||
1059 | The following special options are also recognized: | |
1060 | @table @option | |
1061 | @item f | |
1062 | Specify the format name. Useful if it cannot be guessed from the | |
1063 | output name suffix. | |
1064 | ||
1065 | @item bsfs[/@var{spec}] | |
1066 | Specify a list of bitstream filters to apply to the specified | |
1067 | output. | |
1068 | ||
1069 | It is possible to specify to which streams a given bitstream filter | |
1070 | applies, by appending a stream specifier to the option separated by | |
1071 | @code{/}. @var{spec} must be a stream specifier (see @ref{Format | |
1072 | stream specifiers}). If the stream specifier is not specified, the | |
1073 | bitstream filters will be applied to all streams in the output. | |
1074 | ||
1075 | Several bitstream filters can be specified, separated by ",". | |
1076 | ||
1077 | @item select | |
1078 | Select the streams that should be mapped to the slave output, | |
1079 | specified by a stream specifier. If not specified, this defaults to | |
1080 | all the input streams. | |
1081 | @end table | |
1082 | ||
1083 | @subsection Examples | |
1084 | ||
1085 | @itemize | |
1086 | @item | |
1087 | Encode something and both archive it in a WebM file and stream it | |
1088 | as MPEG-TS over UDP (the streams need to be explicitly mapped): | |
1089 | @example | |
1090 | ffmpeg -i ... -c:v libx264 -c:a mp2 -f tee -map 0:v -map 0:a | |
1091 | "archive-20121107.mkv|[f=mpegts]udp://10.0.1.255:1234/" | |
1092 | @end example | |
1093 | ||
1094 | @item | |
1095 | Use @command{ffmpeg} to encode the input, and send the output | |
1096 | to three different destinations. The @code{dump_extra} bitstream | |
1097 | filter is used to add extradata information to all the output video | |
1098 | keyframes packets, as requested by the MPEG-TS format. The select | |
1099 | option is applied to @file{out.aac} in order to make it contain only | |
1100 | audio packets. | |
1101 | @example | |
1102 | ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac -strict experimental | |
1103 | -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=a]out.aac" | |
1104 | @end example | |
1105 | ||
1106 | @item | |
1107 | As below, but select only stream @code{a:1} for the audio output. Note | |
1108 | that a second level escaping must be performed, as ":" is a special | |
1109 | character used to separate options. | |
1110 | @example | |
1111 | ffmpeg -i ... -map 0 -flags +global_header -c:v libx264 -c:a aac -strict experimental | |
1112 | -f tee "[bsfs/v=dump_extra]out.ts|[movflags=+faststart]out.mp4|[select=\'a:1\']out.aac" | |
1113 | @end example | |
1114 | @end itemize | |
1115 | ||
1116 | Note: some codecs may need different options depending on the output format; | |
1117 | the auto-detection of this can not work with the tee muxer. The main example | |
1118 | is the @option{global_header} flag. | |
1119 | ||
1120 | @section webm_dash_manifest | |
1121 | ||
1122 | WebM DASH Manifest muxer. | |
1123 | ||
1124 | This muxer implements the WebM DASH Manifest specification to generate the DASH manifest XML. | |
1125 | ||
1126 | @subsection Options | |
1127 | ||
1128 | This muxer supports the following options: | |
1129 | ||
1130 | @table @option | |
1131 | @item adaptation_sets | |
1132 | This option has the following syntax: "id=x,streams=a,b,c id=y,streams=d,e" where x and y are the | |
1133 | unique identifiers of the adaptation sets and a,b,c,d and e are the indices of the corresponding | |
1134 | audio and video streams. Any number of adaptation sets can be added using this option. | |
1135 | @end table | |
1136 | ||
1137 | @subsection Example | |
1138 | @example | |
1139 | ffmpeg -f webm_dash_manifest -i video1.webm \ | |
1140 | -f webm_dash_manifest -i video2.webm \ | |
1141 | -f webm_dash_manifest -i audio1.webm \ | |
1142 | -f webm_dash_manifest -i audio2.webm \ | |
1143 | -map 0 -map 1 -map 2 -map 3 \ | |
1144 | -c copy \ | |
1145 | -f webm_dash_manifest \ | |
1146 | -adaptation_sets "id=0,streams=0,1 id=1,streams=2,3" \ | |
1147 | manifest.xml | |
1148 | @end example | |
1149 | ||
1150 | @c man end MUXERS |