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.

473 lines
18KB

  1. \input texinfo @c -*- texinfo -*-
  2. @settitle FFmpeg FAQ
  3. @titlepage
  4. @sp 7
  5. @center @titlefont{FFmpeg FAQ}
  6. @sp 3
  7. @end titlepage
  8. @chapter General Questions
  9. @section When will the next FFmpeg version be released? / Why are FFmpeg releases so few and far between?
  10. Like most open source projects FFmpeg suffers from a certain lack of
  11. manpower. For this reason the developers have to prioritize the work
  12. they do and putting out releases is not at the top of the list, fixing
  13. bugs and reviewing patches takes precedence. Please don't complain or
  14. request more timely and/or frequent releases unless you are willing to
  15. help out creating them.
  16. @section I have a problem with an old version of FFmpeg; where should I report it?
  17. Nowhere. Upgrade to the latest release or if there is no recent release upgrade
  18. to Subversion HEAD. You could also try to report it. Maybe you will get lucky and
  19. become the first person in history to get an answer different from "upgrade
  20. to Subversion HEAD".
  21. @section Why doesn't FFmpeg support feature [xyz]?
  22. Because no one has taken on that task yet. FFmpeg development is
  23. driven by the tasks that are important to the individual developers.
  24. If there is a feature that is important to you, the best way to get
  25. it implemented is to undertake the task yourself or sponsor a developer.
  26. @section FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it?
  27. No. Windows DLLs are not portable, bloated and often slow.
  28. Moreover FFmpeg strives to support all codecs natively.
  29. A DLL loader is not conducive to that goal.
  30. @section My bugreport/mail to ffmpeg-devel/user has not received any replies.
  31. Likely reasons
  32. @itemize
  33. @item We are busy and haven't had time yet to read your report or
  34. investigate the issue.
  35. @item You didn't follow bugreports.html.
  36. @item You didn't use Subversion HEAD.
  37. @item You reported a segmentation fault without gdb output.
  38. @item You describe a problem but not how to reproduce it.
  39. @item It's unclear if you use ffmpeg as command line tool or use
  40. libav* from another application.
  41. @item You speak about a video having problems on playback but
  42. not what you use to play it.
  43. @item We have no faint clue what you are talking about besides
  44. that it is related to FFmpeg.
  45. @end itemize
  46. @section Is there a forum for FFmpeg? I do not like mailing lists.
  47. Yes, (@url{http://dir.gmane.org/gmane.comp.video.ffmpeg.user}).
  48. @section I cannot read this file although this format seems to be supported by ffmpeg.
  49. Even if ffmpeg can read the container format, it may not support all its
  50. codecs. Please consult the supported codec list in the ffmpeg
  51. documentation.
  52. @section Which codecs are supported by Windows?
  53. Windows does not support standard formats like MPEG very well, unless you
  54. install some additional codecs
  55. The following list of video codecs should work on most Windows systems:
  56. @table @option
  57. @item msmpeg4v2
  58. .avi/.asf
  59. @item msmpeg4
  60. .asf only
  61. @item wmv1
  62. .asf only
  63. @item wmv2
  64. .asf only
  65. @item mpeg4
  66. only if you have some MPEG-4 codec installed like ffdshow or XviD
  67. @item mpeg1
  68. .mpg only
  69. @end table
  70. Note, ASF files often have .wmv or .wma extensions in Windows. It should also
  71. be mentioned that Microsoft claims a patent on the ASF format, and may sue
  72. or threaten users who create ASF files with non-Microsoft software. It is
  73. strongly advised to avoid ASF where possible.
  74. The following list of audio codecs should work on most Windows systems:
  75. @table @option
  76. @item adpcm_ima_wav
  77. @item adpcm_ms
  78. @item pcm
  79. @item mp3
  80. if some MP3 codec like LAME is installed
  81. @end table
  82. @chapter Usage
  83. @section ffmpeg does not work; What is wrong?
  84. Try a @code{make distclean} in the ffmpeg source directory before the build. If this does not help see
  85. (@url{http://ffmpeg.org/bugreports.html}).
  86. @section How do I encode single pictures to movies?
  87. First, rename your pictures to follow a numerical sequence.
  88. For example, img1.jpg, img2.jpg, img3.jpg,...
  89. Then you may run:
  90. @example
  91. ffmpeg -f image2 -i img%d.jpg /tmp/a.mpg
  92. @end example
  93. Notice that @samp{%d} is replaced by the image number.
  94. @file{img%03d.jpg} means the sequence @file{img001.jpg}, @file{img002.jpg}, etc...
  95. The same logic is used for any image format that ffmpeg reads.
  96. @section How do I encode movie to single pictures?
  97. Use:
  98. @example
  99. ffmpeg -i movie.mpg movie%d.jpg
  100. @end example
  101. The @file{movie.mpg} used as input will be converted to
  102. @file{movie1.jpg}, @file{movie2.jpg}, etc...
  103. Instead of relying on file format self-recognition, you may also use
  104. @table @option
  105. @item -vcodec ppm
  106. @item -vcodec png
  107. @item -vcodec mjpeg
  108. @end table
  109. to force the encoding.
  110. Applying that to the previous example:
  111. @example
  112. ffmpeg -i movie.mpg -f image2 -vcodec mjpeg menu%d.jpg
  113. @end example
  114. Beware that there is no "jpeg" codec. Use "mjpeg" instead.
  115. @section I get "Unsupported codec (id=86043) for input stream #0.1". What is the problem?
  116. This is the Qcelp codec, FFmpeg has no support for that codec currently. Try mencoder/mplayer it might work.
  117. @section Why do I see a slight quality degradation with multithreaded MPEG* encoding?
  118. For multithreaded MPEG* encoding, the encoded slices must be independent,
  119. otherwise thread n would practically have to wait for n-1 to finish, so it's
  120. quite logical that there is a small reduction of quality. This is not a bug.
  121. @section How can I read from the standard input or write to the standard output?
  122. Use @file{-} as filename.
  123. @section Why does FFmpeg not decode audio in VOB files?
  124. The audio is AC-3 (a.k.a. A/52). AC-3 decoding is an optional component in FFmpeg
  125. as the component that handles AC-3 decoding is currently released under the GPL.
  126. Enable AC-3 decoding with @code{./configure --enable-gpl}. Take care: By
  127. enabling AC-3, you automatically change the license of libavcodec from
  128. LGPL to GPL.
  129. @section Why does the chrominance data seem to be sampled at a different time from the luminance data on bt8x8 captures on Linux?
  130. This is a well-known bug in the bt8x8 driver. For 2.4.26 there is a patch at
  131. (@url{http://svn.mplayerhq.hu/michael/trunk/patches/bttv-420-2.4.26.patch?view=co}). This may also
  132. apply cleanly to other 2.4-series kernels.
  133. @section How do I avoid the ugly aliasing artifacts in bt8x8 captures on Linux?
  134. Pass 'combfilter=1 lumafilter=1' to the bttv driver. Note though that 'combfilter=1'
  135. will cause somewhat too strong filtering. A fix is to apply (@url{http://svn.mplayerhq.hu/michael/trunk/patches/bttv-comb-2.4.26.patch?view=co})
  136. or (@url{http://svn.mplayerhq.hu/michael/trunk/patches/bttv-comb-2.6.6.patch?view=co})
  137. and pass 'combfilter=2'.
  138. @section -f jpeg doesn't work.
  139. Try '-f image2 test%d.jpg'.
  140. @section Why can I not change the framerate?
  141. Some codecs, like MPEG-1/2, only allow a small number of fixed framerates.
  142. Choose a different codec with the -vcodec command line option.
  143. @section How do I encode XviD or DivX video with ffmpeg?
  144. Both XviD and DivX (version 4+) are implementations of the ISO MPEG-4
  145. standard (note that there are many other coding formats that use this
  146. same standard). Thus, use '-vcodec mpeg4' to encode these formats. The
  147. default fourcc stored in an MPEG-4-coded file will be 'FMP4'. If you want
  148. a different fourcc, use the '-vtag' option. E.g., '-vtag xvid' will
  149. force the fourcc 'xvid' to be stored as the video fourcc rather than the
  150. default.
  151. @section How do I encode videos which play on the iPod?
  152. @table @option
  153. @item needed stuff
  154. -acodec libfaac -vcodec mpeg4 width<=320 height<=240
  155. @item working stuff
  156. 4mv, title
  157. @item non-working stuff
  158. B-frames
  159. @item example command line
  160. ffmpeg -i input -acodec libfaac -ab 128kb -vcodec mpeg4 -b 1200kb -mbd 2 -flags +4mv+trell -aic 2 -cmp 2 -subcmp 2 -s 320x180 -title X output.mp4
  161. @end table
  162. @section How do I encode videos which play on the PSP?
  163. @table @option
  164. @item needed stuff
  165. -acodec libfaac -vcodec mpeg4 width*height<=76800 width%16=0 height%16=0 -ar 24000 -r 30000/1001 or 15000/1001 -f psp
  166. @item working stuff
  167. 4mv, title
  168. @item non-working stuff
  169. B-frames
  170. @item example command line
  171. ffmpeg -i input -acodec libfaac -ab 128kb -vcodec mpeg4 -b 1200kb -ar 24000 -mbd 2 -flags +4mv+trell -aic 2 -cmp 2 -subcmp 2 -s 368x192 -r 30000/1001 -title X -f psp output.mp4
  172. @item needed stuff for H.264
  173. -acodec libfaac -vcodec h264 width*height<=76800 width%16=0? height%16=0? -ar 48000 -coder 1 -r 30000/1001 or 15000/1001 -f psp
  174. @item working stuff for H.264
  175. title, loop filter
  176. @item non-working stuff for H.264
  177. CAVLC
  178. @item example command line
  179. ffmpeg -i input -acodec libfaac -ab 128kb -vcodec h264 -b 1200kb -ar 48000 -mbd 2 -coder 1 -cmp 2 -subcmp 2 -s 368x192 -r 30000/1001 -title X -f psp -flags loop -trellis 2 -partitions parti4x4+parti8x8+partp4x4+partp8x8+partb8x8 output.mp4
  180. @end table
  181. @section Which are good parameters for encoding high quality MPEG-4?
  182. '-mbd rd -flags +4mv+trell+aic -cmp 2 -subcmp 2 -g 300 -pass 1/2',
  183. things to try: '-bf 2', '-flags qprd', '-flags mv0', '-flags skiprd'.
  184. @section Which are good parameters for encoding high quality MPEG-1/MPEG-2?
  185. '-mbd rd -flags +trell -cmp 2 -subcmp 2 -g 100 -pass 1/2'
  186. but beware the '-g 100' might cause problems with some decoders.
  187. Things to try: '-bf 2', '-flags qprd', '-flags mv0', '-flags skiprd.
  188. @section Interlaced video looks very bad when encoded with ffmpeg, whats wrong?
  189. You should use '-flags +ilme+ildct' and maybe '-flags +alt' for interlaced
  190. material, and try '-top 0/1' if the result looks really messed-up.
  191. @section How can I read DirectShow files?
  192. If you have built FFmpeg with @code{./configure --enable-avisynth}
  193. (only possible on MinGW/Cygwin platforms),
  194. then you may use any file that DirectShow can read as input.
  195. (Be aware that this feature has been recently added,
  196. so you will need to help yourself in case of problems.)
  197. Just create an "input.avs" text file with this single line ...
  198. @example
  199. DirectShowSource("C:\path to your file\yourfile.asf")
  200. @end example
  201. ... and then feed that text file to FFmpeg:
  202. @example
  203. ffmpeg -i input.avs
  204. @end example
  205. For ANY other help on Avisynth, please visit @url{http://www.avisynth.org/}.
  206. @section How can I join video files?
  207. A few multimedia containers (MPEG-1, MPEG-2 PS, DV) allow to join video files by
  208. merely concatenating them.
  209. Hence you may concatenate your multimedia files by first transcoding them to
  210. these privileged formats, then using the humble @code{cat} command (or the
  211. equally humble @code{copy} under Windows), and finally transcoding back to your
  212. format of choice.
  213. @example
  214. ffmpeg -i input1.avi -sameq intermediate1.mpg
  215. ffmpeg -i input2.avi -sameq intermediate2.mpg
  216. cat intermediate1.mpg intermediate2.mpg > intermediate_all.mpg
  217. ffmpeg -i intermediate_all.mpg -sameq output.avi
  218. @end example
  219. Notice that you should either use @code{-sameq} or set a reasonably high
  220. bitrate for your intermediate and output files, if you want to preserve
  221. video quality.
  222. Also notice that you may avoid the huge intermediate files by taking advantage
  223. of named pipes, should your platform support it:
  224. @example
  225. mkfifo intermediate1.mpg
  226. mkfifo intermediate2.mpg
  227. ffmpeg -i input1.avi -sameq -y intermediate1.mpg < /dev/null &
  228. ffmpeg -i input2.avi -sameq -y intermediate2.mpg < /dev/null &
  229. cat intermediate1.mpg intermediate2.mpg |\
  230. ffmpeg -f mpeg -i - -sameq -vcodec mpeg4 -acodec libmp3lame output.avi
  231. @end example
  232. Similarly, the yuv4mpegpipe format, and the raw video, raw audio codecs also
  233. allow concatenation, and the transcoding step is almost lossless.
  234. For example, let's say we want to join two FLV files into an output.flv file:
  235. @example
  236. mkfifo temp1.a
  237. mkfifo temp1.v
  238. mkfifo temp2.a
  239. mkfifo temp2.v
  240. mkfifo all.a
  241. mkfifo all.v
  242. ffmpeg -i input1.flv -vn -f u16le -acodec pcm_s16le -ac 2 -ar 44100 - > temp1.a < /dev/null &
  243. ffmpeg -i input2.flv -vn -f u16le -acodec pcm_s16le -ac 2 -ar 44100 - > temp2.a < /dev/null &
  244. ffmpeg -i input1.flv -an -f yuv4mpegpipe - > temp1.v < /dev/null &
  245. ffmpeg -i input2.flv -an -f yuv4mpegpipe - > temp2.v < /dev/null &
  246. cat temp1.a temp2.a > all.a &
  247. cat temp1.v temp2.v > all.v &
  248. ffmpeg -f u16le -acodec pcm_s16le -ac 2 -ar 44100 -i all.a \
  249. -f yuv4mpegpipe -i all.v \
  250. -sameq -y output.flv
  251. rm temp[12].[av] all.[av]
  252. @end example
  253. @section FFmpeg does not adhere to the -maxrate setting, some frames are bigger than maxrate/fps.
  254. Read the MPEG spec about video buffer verifier.
  255. @section I want CBR, but no matter what I do frame sizes differ.
  256. You do not understand what CBR is, please read the MPEG spec.
  257. Read about video buffer verifier and constant bitrate.
  258. The one sentence summary is that there is a buffer and the input rate is
  259. constant, the output can vary as needed.
  260. @section How do I check if a stream is CBR?
  261. To quote the MPEG-2 spec:
  262. "There is no way to tell that a bitstream is constant bitrate without
  263. examining all of the vbv_delay values and making complicated computations."
  264. @chapter Development
  265. @section Are there examples illustrating how to use the FFmpeg libraries, particularly libavcodec and libavformat?
  266. Yes. Read the Developers Guide of the FFmpeg documentation. Alternatively,
  267. examine the source code for one of the many open source projects that
  268. already incorporate ffmpeg at (@url{projects.html}).
  269. @section Can you support my C compiler XXX?
  270. It depends. If your compiler is C99-compliant, then patches to support
  271. it are likely to be welcome if they do not pollute the source code
  272. with @code{#ifdef}s related to the compiler.
  273. @section Is Microsoft Visual C++ supported?
  274. No. Microsoft Visual C++ is not compliant to the C99 standard and does
  275. not - among other things - support the inline assembly used in FFmpeg.
  276. If you wish to use MSVC++ for your
  277. project then you can link the MSVC++ code with libav* as long as
  278. you compile the latter with a working C compiler. For more information, see
  279. the @emph{Microsoft Visual C++ compatibility} section in the FFmpeg
  280. documentation.
  281. There have been efforts to make FFmpeg compatible with MSVC++ in the
  282. past. However, they have all been rejected as too intrusive, especially
  283. since MinGW does the job adequately. None of the core developers
  284. work with MSVC++ and thus this item is low priority. Should you find
  285. the silver bullet that solves this problem, feel free to shoot it at us.
  286. We strongly recommend you to move over from MSVC++ to MinGW tools.
  287. @section Can I use FFmpeg or libavcodec under Windows?
  288. Yes, but the Cygwin or MinGW tools @emph{must} be used to compile FFmpeg.
  289. Read the @emph{Windows} section in the FFmpeg documentation to find more
  290. information.
  291. To get help and instructions for building FFmpeg under Windows, check out
  292. the FFmpeg Windows Help Forum at
  293. @url{http://arrozcru.no-ip.org/ffmpeg/}.
  294. @section Can you add automake, libtool or autoconf support?
  295. No. These tools are too bloated and they complicate the build.
  296. @section Why not rewrite ffmpeg in object-oriented C++?
  297. ffmpeg is already organized in a highly modular manner and does not need to
  298. be rewritten in a formal object language. Further, many of the developers
  299. favor straight C; it works for them. For more arguments on this matter,
  300. read "Programming Religion" at (@url{http://www.tux.org/lkml/#s15}).
  301. @section Why are the ffmpeg programs devoid of debugging symbols?
  302. The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug
  303. information. Those binaries are strip'd to create ffmpeg, ffplay, etc. If
  304. you need the debug information, used the *_g versions.
  305. @section I do not like the LGPL, can I contribute code under the GPL instead?
  306. Yes, as long as the code is optional and can easily and cleanly be placed
  307. under #ifdef CONFIG_GPL without breaking anything. So for example a new codec
  308. or filter would be OK under GPL while a bugfix to LGPL code would not.
  309. @section I want to compile xyz.c alone but my compiler produced many errors.
  310. Common code is in its own files in libav* and is used by the individual
  311. codecs. They will not work without the common parts, you have to compile
  312. the whole libav*. If you wish, disable some parts with configure switches.
  313. You can also try to hack it and remove more, but if you had problems fixing
  314. the compilation failure then you are probably not qualified for this.
  315. @section I'm using libavcodec from within my C++ application but the linker complains about missing symbols which seem to be available.
  316. FFmpeg is a pure C project, so to use the libraries within your C++ application
  317. you need to explicitly state that you are using a C library. You can do this by
  318. encompassing your FFmpeg includes using @code{extern "C"}.
  319. See @url{http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html#faq-32.3}
  320. @section I have a file in memory / a API different from *open/*read/ libc how do i use it with libavformat?
  321. You have to implement a URLProtocol, see libavformat/file.c in FFmpeg
  322. and libmpdemux/demux_lavf.c in MPlayer sources.
  323. @section I get "No compatible shell script interpreter found." in MSys.
  324. The standard MSys bash (2.04) is broken. You need to install 2.05 or later.
  325. @section I get "./configure: line <xxx>: pr: command not found" in MSys.
  326. The standard MSys install doesn't come with pr. You need to get it from the coreutils package.
  327. @section I tried to pass RTP packets into a decoder, but it doesn't work.
  328. RTP is a container format like any other, you must first depacketize the
  329. codec frames/samples stored in RTP and then feed to the decoder.
  330. @section Where can I find libav* headers for Pascal/Delphi?
  331. see @url{http://www.iversenit.dk/dev/ffmpeg-headers/}
  332. @section Where is the documentation about ffv1, msmpeg4, asv1, 4xm?
  333. see @url{http://svn.mplayerhq.hu/michael/trunk/docs/}
  334. @section How do I feed H.263-RTP (and other codecs in RTP) to libavcodec?
  335. Even if peculiar since it is network oriented, RTP is a container like any
  336. other. You have to @emph{demux} RTP before feeding the payload to libavcodec.
  337. In this specific case please look at RFC 4629 to see how it should be done.
  338. @section AVStream.r_frame_rate is wrong, it is much larger than the framerate.
  339. r_frame_rate is NOT the average framerate, it is the smallest framerate
  340. that can accurately represent all timestamps. So no, it is not
  341. wrong if it is larger than the average!
  342. For example, if you have mixed 25 and 30 fps content, then r_frame_rate
  343. will be 150.
  344. @bye