You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

558 lines
20KB

  1. @chapter Muxers
  2. @c man begin MUXERS
  3. Muxers are configured elements in Libav which allow writing
  4. multimedia streams to a particular type of file.
  5. When you configure your Libav build, all the supported muxers
  6. are enabled by default. You can list all available muxers using the
  7. configure option @code{--list-muxers}.
  8. You can disable all the muxers with the configure option
  9. @code{--disable-muxers} and selectively enable / disable single muxers
  10. with the options @code{--enable-muxer=@var{MUXER}} /
  11. @code{--disable-muxer=@var{MUXER}}.
  12. The option @code{-formats} of the av* tools will display the list of
  13. enabled muxers.
  14. A description of some of the currently available muxers follows.
  15. @anchor{crc}
  16. @section crc
  17. CRC (Cyclic Redundancy Check) testing format.
  18. This muxer computes and prints the Adler-32 CRC of all the input audio
  19. and video frames. By default audio frames are converted to signed
  20. 16-bit raw audio and video frames to raw video before computing the
  21. CRC.
  22. The output of the muxer consists of a single line of the form:
  23. CRC=0x@var{CRC}, where @var{CRC} is a hexadecimal number 0-padded to
  24. 8 digits containing the CRC for all the decoded input frames.
  25. For example to compute the CRC of the input, and store it in the file
  26. @file{out.crc}:
  27. @example
  28. avconv -i INPUT -f crc out.crc
  29. @end example
  30. You can print the CRC to stdout with the command:
  31. @example
  32. avconv -i INPUT -f crc -
  33. @end example
  34. You can select the output format of each frame with @command{avconv} by
  35. specifying the audio and video codec and format. For example to
  36. compute the CRC of the input audio converted to PCM unsigned 8-bit
  37. and the input video converted to MPEG-2 video, use the command:
  38. @example
  39. avconv -i INPUT -c:a pcm_u8 -c:v mpeg2video -f crc -
  40. @end example
  41. See also the @ref{framecrc} muxer.
  42. @anchor{framecrc}
  43. @section framecrc
  44. Per-frame CRC (Cyclic Redundancy Check) testing format.
  45. This muxer computes and prints the Adler-32 CRC for each decoded audio
  46. and video frame. 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. The output of the muxer consists of a line for each audio and video
  50. frame of the form: @var{stream_index}, @var{frame_dts},
  51. @var{frame_size}, 0x@var{CRC}, where @var{CRC} is a hexadecimal
  52. number 0-padded to 8 digits containing the CRC of the decoded frame.
  53. For example to compute the CRC of each decoded frame in the input, and
  54. store it in the file @file{out.crc}:
  55. @example
  56. avconv -i INPUT -f framecrc out.crc
  57. @end example
  58. You can print the CRC of each decoded frame to stdout with the command:
  59. @example
  60. avconv -i INPUT -f framecrc -
  61. @end example
  62. You can select the output format of each frame with @command{avconv} by
  63. specifying the audio and video codec and format. For example, to
  64. compute the CRC of each decoded input audio frame converted to PCM
  65. unsigned 8-bit and of each decoded input video frame converted to
  66. MPEG-2 video, use the command:
  67. @example
  68. avconv -i INPUT -c:a pcm_u8 -c:v mpeg2video -f framecrc -
  69. @end example
  70. See also the @ref{crc} muxer.
  71. @anchor{hls}
  72. @section hls
  73. Apple HTTP Live Streaming muxer that segments MPEG-TS according to
  74. the HTTP Live Streaming specification.
  75. It creates a playlist file and numbered segment files. The output
  76. filename specifies the playlist filename; the segment filenames
  77. receive the same basename as the playlist, a sequential number and
  78. a .ts extension.
  79. @example
  80. avconv -i in.nut out.m3u8
  81. @end example
  82. @table @option
  83. @item -hls_time @var{seconds}
  84. Set the segment length in seconds.
  85. @item -hls_list_size @var{size}
  86. Set the maximum number of playlist entries.
  87. @item -hls_wrap @var{wrap}
  88. Set the number after which index wraps.
  89. @item -start_number @var{number}
  90. Start the sequence from @var{number}.
  91. @item -hls_base_url @var{baseurl}
  92. Append @var{baseurl} to every entry in the playlist.
  93. Useful to generate playlists with absolute paths.
  94. @item -hls_allow_cache @var{allowcache}
  95. Explicitly set whether the client MAY (1) or MUST NOT (0) cache media segments
  96. @item -hls_version @var{version}
  97. Set the protocol version. Enables or disables version-specific features
  98. such as the integer (version 2) or decimal EXTINF values (version 3).
  99. @end table
  100. @anchor{image2}
  101. @section image2
  102. Image file muxer.
  103. The image file muxer writes video frames to image files.
  104. The output filenames are specified by a pattern, which can be used to
  105. produce sequentially numbered series of files.
  106. The pattern may contain the string "%d" or "%0@var{N}d", this string
  107. specifies the position of the characters representing a numbering in
  108. the filenames. If the form "%0@var{N}d" is used, the string
  109. representing the number in each filename is 0-padded to @var{N}
  110. digits. The literal character '%' can be specified in the pattern with
  111. the string "%%".
  112. If the pattern contains "%d" or "%0@var{N}d", the first filename of
  113. the file list specified will contain the number 1, all the following
  114. numbers will be sequential.
  115. The pattern may contain a suffix which is used to automatically
  116. determine the format of the image files to write.
  117. For example the pattern "img-%03d.bmp" will specify a sequence of
  118. filenames of the form @file{img-001.bmp}, @file{img-002.bmp}, ...,
  119. @file{img-010.bmp}, etc.
  120. The pattern "img%%-%d.jpg" will specify a sequence of filenames of the
  121. form @file{img%-1.jpg}, @file{img%-2.jpg}, ..., @file{img%-10.jpg},
  122. etc.
  123. The following example shows how to use @command{avconv} for creating a
  124. sequence of files @file{img-001.jpeg}, @file{img-002.jpeg}, ...,
  125. taking one image every second from the input video:
  126. @example
  127. avconv -i in.avi -vsync 1 -r 1 -f image2 'img-%03d.jpeg'
  128. @end example
  129. Note that with @command{avconv}, if the format is not specified with the
  130. @code{-f} option and the output filename specifies an image file
  131. format, the image2 muxer is automatically selected, so the previous
  132. command can be written as:
  133. @example
  134. avconv -i in.avi -vsync 1 -r 1 'img-%03d.jpeg'
  135. @end example
  136. Note also that the pattern must not necessarily contain "%d" or
  137. "%0@var{N}d", for example to create a single image file
  138. @file{img.jpeg} from the input video you can employ the command:
  139. @example
  140. avconv -i in.avi -f image2 -frames:v 1 img.jpeg
  141. @end example
  142. @table @option
  143. @item -start_number @var{number}
  144. Start the sequence from @var{number}.
  145. @item -update @var{number}
  146. If @var{number} is nonzero, the filename will always be interpreted as just a
  147. filename, not a pattern, and this file will be continuously overwritten with new
  148. images.
  149. @end table
  150. @section matroska
  151. Matroska container muxer.
  152. This muxer implements the matroska and webm container specs.
  153. The recognized metadata settings in this muxer are:
  154. @table @option
  155. @item title=@var{title name}
  156. Name provided to a single track
  157. @end table
  158. @table @option
  159. @item language=@var{language name}
  160. Specifies the language of the track in the Matroska languages form
  161. @end table
  162. @table @option
  163. @item STEREO_MODE=@var{mode}
  164. Stereo 3D video layout of two views in a single video track
  165. @table @option
  166. @item mono
  167. video is not stereo
  168. @item left_right
  169. Both views are arranged side by side, Left-eye view is on the left
  170. @item bottom_top
  171. Both views are arranged in top-bottom orientation, Left-eye view is at bottom
  172. @item top_bottom
  173. Both views are arranged in top-bottom orientation, Left-eye view is on top
  174. @item checkerboard_rl
  175. Each view is arranged in a checkerboard interleaved pattern, Left-eye view being first
  176. @item checkerboard_lr
  177. Each view is arranged in a checkerboard interleaved pattern, Right-eye view being first
  178. @item row_interleaved_rl
  179. Each view is constituted by a row based interleaving, Right-eye view is first row
  180. @item row_interleaved_lr
  181. Each view is constituted by a row based interleaving, Left-eye view is first row
  182. @item col_interleaved_rl
  183. Both views are arranged in a column based interleaving manner, Right-eye view is first column
  184. @item col_interleaved_lr
  185. Both views are arranged in a column based interleaving manner, Left-eye view is first column
  186. @item anaglyph_cyan_red
  187. All frames are in anaglyph format viewable through red-cyan filters
  188. @item right_left
  189. Both views are arranged side by side, Right-eye view is on the left
  190. @item anaglyph_green_magenta
  191. All frames are in anaglyph format viewable through green-magenta filters
  192. @item block_lr
  193. Both eyes laced in one Block, Left-eye view is first
  194. @item block_rl
  195. Both eyes laced in one Block, Right-eye view is first
  196. @end table
  197. @end table
  198. For example a 3D WebM clip can be created using the following command line:
  199. @example
  200. avconv -i sample_left_right_clip.mpg -an -c:v libvpx -metadata STEREO_MODE=left_right -y stereo_clip.webm
  201. @end example
  202. This muxer supports the following options:
  203. @table @option
  204. @item reserve_index_space
  205. By default, this muxer writes the index for seeking (called cues in Matroska
  206. terms) at the end of the file, because it cannot know in advance how much space
  207. to leave for the index at the beginning of the file. However for some use cases
  208. -- e.g. streaming where seeking is possible but slow -- it is useful to put the
  209. index at the beginning of the file.
  210. If this option is set to a non-zero value, the muxer will reserve a given amount
  211. of space in the file header and then try to write the cues there when the muxing
  212. finishes. If the available space does not suffice, muxing will fail. A safe size
  213. for most use cases should be about 50kB per hour of video.
  214. Note that cues are only written if the output is seekable and this option will
  215. have no effect if it is not.
  216. @end table
  217. @section mov, mp4, ismv
  218. The mov/mp4/ismv muxer supports fragmentation. Normally, a MOV/MP4
  219. file has all the metadata about all packets stored in one location
  220. (written at the end of the file, it can be moved to the start for
  221. better playback using the @command{qt-faststart} tool). A fragmented
  222. file consists of a number of fragments, where packets and metadata
  223. about these packets are stored together. Writing a fragmented
  224. file has the advantage that the file is decodable even if the
  225. writing is interrupted (while a normal MOV/MP4 is undecodable if
  226. it is not properly finished), and it requires less memory when writing
  227. very long files (since writing normal MOV/MP4 files stores info about
  228. every single packet in memory until the file is closed). The downside
  229. is that it is less compatible with other applications.
  230. Fragmentation is enabled by setting one of the AVOptions that define
  231. how to cut the file into fragments:
  232. @table @option
  233. @item -movflags frag_keyframe
  234. Start a new fragment at each video keyframe.
  235. @item -frag_duration @var{duration}
  236. Create fragments that are @var{duration} microseconds long.
  237. @item -frag_size @var{size}
  238. Create fragments that contain up to @var{size} bytes of payload data.
  239. @item -movflags frag_custom
  240. Allow the caller to manually choose when to cut fragments, by
  241. calling @code{av_write_frame(ctx, NULL)} to write a fragment with
  242. the packets written so far. (This is only useful with other
  243. applications integrating libavformat, not from @command{avconv}.)
  244. @item -min_frag_duration @var{duration}
  245. Don't create fragments that are shorter than @var{duration} microseconds long.
  246. @end table
  247. If more than one condition is specified, fragments are cut when
  248. one of the specified conditions is fulfilled. The exception to this is
  249. @code{-min_frag_duration}, which has to be fulfilled for any of the other
  250. conditions to apply.
  251. Additionally, the way the output file is written can be adjusted
  252. through a few other options:
  253. @table @option
  254. @item -movflags empty_moov
  255. Write an initial moov atom directly at the start of the file, without
  256. describing any samples in it. Generally, an mdat/moov pair is written
  257. at the start of the file, as a normal MOV/MP4 file, containing only
  258. a short portion of the file. With this option set, there is no initial
  259. mdat atom, and the moov atom only describes the tracks but has
  260. a zero duration.
  261. This option is implicitly set when writing ismv (Smooth Streaming) files.
  262. @item -movflags separate_moof
  263. Write a separate moof (movie fragment) atom for each track. Normally,
  264. packets for all tracks are written in a moof atom (which is slightly
  265. more efficient), but with this option set, the muxer writes one moof/mdat
  266. pair for each track, making it easier to separate tracks.
  267. This option is implicitly set when writing ismv (Smooth Streaming) files.
  268. @item -movflags faststart
  269. Run a second pass moving the index (moov atom) to the beginning of the file.
  270. This operation can take a while, and will not work in various situations such
  271. as fragmented output, thus it is not enabled by default.
  272. @item -movflags disable_chpl
  273. Disable Nero chapter markers (chpl atom). Normally, both Nero chapters
  274. and a QuickTime chapter track are written to the file. With this option
  275. set, only the QuickTime chapter track will be written. Nero chapters can
  276. cause failures when the file is reprocessed with certain tagging programs.
  277. @item -movflags omit_tfhd_offset
  278. Do not write any absolute base_data_offset in tfhd atoms. This avoids
  279. tying fragments to absolute byte positions in the file/streams.
  280. @item -movflags default_base_moof
  281. Similarly to the omit_tfhd_offset, this flag avoids writing the
  282. absolute base_data_offset field in tfhd atoms, but does so by using
  283. the new default-base-is-moof flag instead. This flag is new from
  284. 14496-12:2012. This may make the fragments easier to parse in certain
  285. circumstances (avoiding basing track fragment location calculations
  286. on the implicit end of the previous track fragment).
  287. @end table
  288. Smooth Streaming content can be pushed in real time to a publishing
  289. point on IIS with this muxer. Example:
  290. @example
  291. avconv -re @var{<normal input/transcoding options>} -movflags isml+frag_keyframe -f ismv http://server/publishingpoint.isml/Streams(Encoder1)
  292. @end example
  293. @section mp3
  294. The MP3 muxer writes a raw MP3 stream with the following optional features:
  295. @itemize @bullet
  296. @item
  297. An ID3v2 metadata header at the beginning (enabled by default). Versions 2.3 and
  298. 2.4 are supported, the @code{id3v2_version} private option controls which one is
  299. used (3 or 4). Setting @code{id3v2_version} to 0 disables the ID3v2 header
  300. completely.
  301. The muxer supports writing attached pictures (APIC frames) to the ID3v2 header.
  302. The pictures are supplied to the muxer in form of a video stream with a single
  303. packet. There can be any number of those streams, each will correspond to a
  304. single APIC frame. The stream metadata tags @var{title} and @var{comment} map
  305. to APIC @var{description} and @var{picture type} respectively. See
  306. @url{http://id3.org/id3v2.4.0-frames} for allowed picture types.
  307. Note that the APIC frames must be written at the beginning, so the muxer will
  308. buffer the audio frames until it gets all the pictures. It is therefore advised
  309. to provide the pictures as soon as possible to avoid excessive buffering.
  310. @item
  311. A Xing/LAME frame right after the ID3v2 header (if present). It is enabled by
  312. default, but will be written only if the output is seekable. The
  313. @code{write_xing} private option can be used to disable it. The frame contains
  314. various information that may be useful to the decoder, like the audio duration
  315. or encoder delay.
  316. @item
  317. A legacy ID3v1 tag at the end of the file (disabled by default). It may be
  318. enabled with the @code{write_id3v1} private option, but as its capabilities are
  319. very limited, its usage is not recommended.
  320. @end itemize
  321. Examples:
  322. Write an mp3 with an ID3v2.3 header and an ID3v1 footer:
  323. @example
  324. avconv -i INPUT -id3v2_version 3 -write_id3v1 1 out.mp3
  325. @end example
  326. Attach a picture to an mp3:
  327. @example
  328. avconv -i input.mp3 -i cover.png -c copy -metadata:s:v title="Album cover"
  329. -metadata:s:v comment="Cover (Front)" out.mp3
  330. @end example
  331. Write a "clean" MP3 without any extra features:
  332. @example
  333. avconv -i input.wav -write_xing 0 -id3v2_version 0 out.mp3
  334. @end example
  335. @section mpegts
  336. MPEG transport stream muxer.
  337. This muxer implements ISO 13818-1 and part of ETSI EN 300 468.
  338. The muxer options are:
  339. @table @option
  340. @item -mpegts_original_network_id @var{number}
  341. Set the original_network_id (default 0x0001). This is unique identifier
  342. of a network in DVB. Its main use is in the unique identification of a
  343. service through the path Original_Network_ID, Transport_Stream_ID.
  344. @item -mpegts_transport_stream_id @var{number}
  345. Set the transport_stream_id (default 0x0001). This identifies a
  346. transponder in DVB.
  347. @item -mpegts_service_id @var{number}
  348. Set the service_id (default 0x0001) also known as program in DVB.
  349. @item -mpegts_pmt_start_pid @var{number}
  350. Set the first PID for PMT (default 0x1000, max 0x1f00).
  351. @item -mpegts_start_pid @var{number}
  352. Set the first PID for data packets (default 0x0100, max 0x0f00).
  353. @item -muxrate @var{number}
  354. Set a constant muxrate (default VBR).
  355. @item -pcr_period @var{numer}
  356. Override the default PCR retransmission time (default 20ms), ignored
  357. if variable muxrate is selected.
  358. @end table
  359. The recognized metadata settings in mpegts muxer are @code{service_provider}
  360. and @code{service_name}. If they are not set the default for
  361. @code{service_provider} is "Libav" and the default for
  362. @code{service_name} is "Service01".
  363. @example
  364. avconv -i file.mpg -c copy \
  365. -mpegts_original_network_id 0x1122 \
  366. -mpegts_transport_stream_id 0x3344 \
  367. -mpegts_service_id 0x5566 \
  368. -mpegts_pmt_start_pid 0x1500 \
  369. -mpegts_start_pid 0x150 \
  370. -metadata service_provider="Some provider" \
  371. -metadata service_name="Some Channel" \
  372. -y out.ts
  373. @end example
  374. @section null
  375. Null muxer.
  376. This muxer does not generate any output file, it is mainly useful for
  377. testing or benchmarking purposes.
  378. For example to benchmark decoding with @command{avconv} you can use the
  379. command:
  380. @example
  381. avconv -benchmark -i INPUT -f null out.null
  382. @end example
  383. Note that the above command does not read or write the @file{out.null}
  384. file, but specifying the output file is required by the @command{avconv}
  385. syntax.
  386. Alternatively you can write the command as:
  387. @example
  388. avconv -benchmark -i INPUT -f null -
  389. @end example
  390. @section nut
  391. @table @option
  392. @item -syncpoints @var{flags}
  393. Change the syncpoint usage in nut:
  394. @table @option
  395. @item @var{default} use the normal low-overhead seeking aids.
  396. @item @var{none} do not use the syncpoints at all, reducing the overhead but making the stream non-seekable;
  397. @item @var{timestamped} extend the syncpoint with a wallclock field.
  398. @end table
  399. The @var{none} and @var{timestamped} flags are experimental.
  400. @end table
  401. @example
  402. avconv -i INPUT -f_strict experimental -syncpoints none - | processor
  403. @end example
  404. @section ogg
  405. Ogg container muxer.
  406. @table @option
  407. @item -page_duration @var{duration}
  408. Preferred page duration, in microseconds. The muxer will attempt to create
  409. pages that are approximately @var{duration} microseconds long. This allows the
  410. user to compromise between seek granularity and container overhead. The default
  411. is 1 second. A value of 0 will fill all segments, making pages as large as
  412. possible. A value of 1 will effectively use 1 packet-per-page in most
  413. situations, giving a small seek granularity at the cost of additional container
  414. overhead.
  415. @item -serial_offset @var{value}
  416. Serial value from which to set the streams serial number.
  417. Setting it to different and sufficiently large values ensures that the produced
  418. ogg files can be safely chained.
  419. @end table
  420. @section segment
  421. Basic stream segmenter.
  422. The segmenter muxer outputs streams to a number of separate files of nearly
  423. fixed duration. Output filename pattern can be set in a fashion similar to
  424. @ref{image2}.
  425. Every segment starts with a video keyframe, if a video stream is present.
  426. The segment muxer works best with a single constant frame rate video.
  427. Optionally it can generate a flat list of the created segments, one segment
  428. per line.
  429. @table @option
  430. @item segment_format @var{format}
  431. Override the inner container format, by default it is guessed by the filename
  432. extension.
  433. @item segment_time @var{t}
  434. Set segment duration to @var{t} seconds.
  435. @item segment_list @var{name}
  436. Generate also a listfile named @var{name}.
  437. @item segment_list_type @var{type}
  438. Select the listing format.
  439. @table @option
  440. @item @var{flat} use a simple flat list of entries.
  441. @item @var{hls} use a m3u8-like structure.
  442. @end table
  443. @item segment_list_size @var{size}
  444. Overwrite the listfile once it reaches @var{size} entries.
  445. @item segment_list_entry_prefix @var{prefix}
  446. Prepend @var{prefix} to each entry. Useful to generate absolute paths.
  447. @item segment_wrap @var{limit}
  448. Wrap around segment index once it reaches @var{limit}.
  449. @end table
  450. @example
  451. avconv -i in.mkv -c copy -map 0 -f segment -list out.list out%03d.nut
  452. @end example
  453. @c man end MUXERS