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.

457 lines
17KB

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