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.

260 lines
10KB

  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 JPEGs to another format ?
  14. If the JPEGs are named img1.jpg, img2.jpg, img3.jpg,..., use:
  15. @example
  16. ffmpeg -i img%d.jpg /tmp/a.mpg
  17. @end example
  18. @samp{%d} is replaced by the image number.
  19. @file{img%03d.jpg} generates @file{img001.jpg}, @file{img002.jpg}, etc...
  20. The same system is used for the other image formats.
  21. @section FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it ?
  22. No. FFmpeg only supports open source codecs. Windows DLLs are not
  23. portable, bloated and often slow.
  24. @section Why do I see a slight quality degradation with multithreaded MPEG* encoding ?
  25. For multithreaded MPEG* encoding, the encoded slices must be independent,
  26. otherwise thread n would practically have to wait for n-1 to finish, so it's
  27. quite logical that there is a small reduction of quality. This is not a bug.
  28. @section How can I read from the standard input or write to the standard output ?
  29. Use @file{-} as filename.
  30. @section Why does ffmpeg not decode audio in VOB files ?
  31. The audio is AC3 (a.k.a. A/52). AC3 decoding is an optional component in ffmpeg
  32. as the component that handles AC3 decoding (liba52) is currently released under
  33. the GPL. If you have liba52 installed on your system, enable AC3 decoding
  34. with @code{./configure --enable-a52}. Take care: by
  35. enabling AC3, you automatically change the license of libavcodec from
  36. LGPL to GPL.
  37. @section Which codecs are supported by Windows ?
  38. Windows does not support standard formats like MPEG very well, unless you
  39. install some additional codecs
  40. The following list of video codecs should work on most Windows systems:
  41. @table @option
  42. @item msmpeg4v2
  43. .avi/.asf
  44. @item msmpeg4
  45. .asf only
  46. @item wmv1
  47. .asf only
  48. @item wmv2
  49. .asf only
  50. @item mpeg4
  51. only if you have some MPEG-4 codec installed like ffdshow or XviD
  52. @item mpeg1
  53. .mpg only
  54. @end table
  55. Note, ASF files often have .wmv or .wma extensions in Windows. It should also
  56. be mentioned that Microsoft claims a patent on the ASF format, and may sue
  57. or threaten users who create ASF files with non-Microsoft software. It is
  58. strongly advised to avoid ASF where possible.
  59. The following list of audio codecs should work on most Windows systems:
  60. @table @option
  61. @item adpcm_ima_wav
  62. @item adpcm_ms
  63. @item pcm
  64. @item mp3
  65. if some MP3 codec like LAME is installed
  66. @end table
  67. @section Why does the chrominance data seem to be sampled at a different time from the luminance data on bt8x8 captures on Linux?
  68. This is a well-known bug in the bt8x8 driver. For 2.4.26 there is a patch at
  69. (@url{http://mplayerhq.hu/~michael/bttv-420-2.4.26.patch}). This may also
  70. apply cleanly to other 2.4-series kernels.
  71. @section How do I avoid the ugly aliasing artifacts in bt8x8 captures on Linux?
  72. Pass 'combfilter=1 lumafilter=1' to the bttv driver. Note though that 'combfilter=1'
  73. will cause somewhat too strong filtering. A fix is to apply (@url{http://mplayerhq.hu/~michael/bttv-comb-2.4.26.patch})
  74. or (@url{http://mplayerhq.hu/~michael/bttv-comb-2.6.6.patch})
  75. and pass 'combfilter=2'.
  76. @section I have a problem with an old version of ffmpeg; where should I report it?
  77. Nowhere. Upgrade to the latest release or if there is no recent release upgrade
  78. to Subversion HEAD. You could also try to report it. Maybe you will get lucky and
  79. become the first person in history to get an answer different from "upgrade
  80. to Subversion HEAD".
  81. @section -f jpeg doesn't work.
  82. Try '-f image -img jpeg test%d.jpg'.
  83. @section Why can I not change the framerate?
  84. Some codecs, like MPEG-1/2, only allow a small number of fixed framerates.
  85. Choose a different codec with the -vcodec command line option.
  86. @section ffmpeg does not work; What is wrong?
  87. Try a 'make distclean' in the ffmpeg source directory. If this does not help see
  88. (@url{http://ffmpeg.org/bugreports.php}).
  89. @section How do I encode XviD or DivX video with ffmpeg?
  90. Both XviD and DivX (version 4+) are implementations of the ISO MPEG-4
  91. standard (note that there are many other coding formats that use this
  92. same standard). Thus, use '-vcodec mpeg4' to encode these formats. The
  93. default fourcc stored in an MPEG-4-coded file will be 'FMP4'. If you want
  94. a different fourcc, use the '-vtag' option. E.g., '-vtag xvid' will
  95. force the fourcc 'xvid' to be stored as the video fourcc rather than the
  96. default.
  97. @section How do I encode videos which play on the iPod?
  98. @table @option
  99. @item needed stuff
  100. -acodec aac -vcodec mpeg4 width<=320 height<=240
  101. @item working stuff
  102. 4mv, title
  103. @item non-working stuff
  104. B-frames
  105. @item example command line
  106. ffmpeg -i input -acodec aac -ab 128 -vcodec mpeg4 -b 1200 -mbd 2 -flags +4mv+trell -aic 2 -cmp 2 -subcmp 2 -s 320x180 -title X output.mp4
  107. @end table
  108. @section How do I encode videos which play on the PSP?
  109. @table @option
  110. @item needed stuff
  111. -acodec aac -vcodec mpeg4 width*height<=76800 width%16=0 height%16=0 -ar 24000 -r 30000/1001 or 15000/1001 -f psp
  112. @item working stuff
  113. 4mv, title
  114. @item non-working stuff
  115. B-frames
  116. @item example command line
  117. ffmpeg -i input -acodec aac -ab 128 -vcodec mpeg4 -b 1200 -ar 24000 -mbd 2 -flags +4mv+trell -aic 2 -cmp 2 -subcmp 2 -s 368x192 -r 30000/1001 -title X -f psp output.mp4
  118. @item needed stuff for H.264
  119. -acodec aac -vcodec h264 width*height<=76800 width%16=0? height%16=0? -ar 48000 -coder 1 -r 30000/1001 or 15000/1001 -f psp
  120. @item working stuff for H.264
  121. title, loop filter
  122. @item non-working stuff for H.264
  123. CAVLC
  124. @item example command line
  125. ffmpeg -i input -acodec aac -ab 128 -vcodec h264 -b 1200 -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
  126. @end table
  127. @chapter Development
  128. @section When will the next FFmpeg version be released? / Why are FFmpeg releases so few and far between?
  129. Like most open source projects FFmpeg suffers from a certain lack of
  130. manpower. For this reason the developers have to prioritize the work
  131. they do and putting out releases is not at the top of the list, fixing
  132. bugs and reviewing patches takes precedence. Please don't complain or
  133. request more timely and/or frequent releases unless you are willing to
  134. help out creating them.
  135. @section Why doesn't FFmpeg support feature [xyz]?
  136. Because no one has taken on that task yet. FFmpeg development is
  137. driven by the tasks that are important to the individual developers.
  138. If there is a feature that is important to you, the best way to get
  139. it implemented is to undertake the task yourself.
  140. @section Are there examples illustrating how to use the FFmpeg libraries, particularly libavcodec and libavformat ?
  141. Yes. Read the Developers Guide of the FFmpeg documentation. Alternatively,
  142. examine the source code for one of the many open source projects that
  143. already incorporate ffmpeg at (@url{projects.php}).
  144. @section Can you support my C compiler XXX ?
  145. No. Only GCC is supported. GCC is ported to most systems available and there
  146. is no need to pollute the source code with @code{#ifdef}s
  147. related to the compiler.
  148. @section Can I use FFmpeg or libavcodec under Windows ?
  149. Yes, but the MinGW tools @emph{must} be used to compile FFmpeg. You
  150. can link the resulting DLLs with any other Windows program. Read the
  151. @emph{Native Windows Compilation} and @emph{Visual C++ compatibility}
  152. sections in the FFmpeg documentation to find more information.
  153. @section Can you add automake, libtool or autoconf support ?
  154. No. These tools are too bloated and they complicate the build. Moreover,
  155. since only @samp{gcc} is supported they would add little advantages in
  156. terms of portability.
  157. @section Why not rewrite ffmpeg in object-oriented C++ ?
  158. ffmpeg is already organized in a highly modular manner and does not need to
  159. be rewritten in a formal object language. Further, many of the developers
  160. favor straight C; it works for them. For more arguments on this matter,
  161. read "Programming Religion" at (@url{http://lkml.org/faq/lkmlfaq-15.html}).
  162. @section Why are the ffmpeg programs devoid of debugging symbols ?
  163. The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug
  164. information. Those binaries are strip'd to create ffmpeg, ffplay, etc. If
  165. you need the debug information, used the *_g versions.
  166. @section I do not like the LGPL, can I contribute code under the GPL instead ?
  167. Yes, as long as the code is optional and can easily and cleanly be placed
  168. under #ifdef CONFIG_GPL without breaking anything. So for example a new codec
  169. or filter would be OK under GPL while a bugfix to LGPL code would not.
  170. @section I want to compile xyz.c alone but my compiler produced many errors.
  171. Common code is in its own files in libav* and is used by the individual
  172. codecs. They will not work without the common parts, you have to compile
  173. the whole libav*. If you wish, disable some parts with configure switches.
  174. You can also try to hack it and remove more, but if you had problems fixing
  175. the compilation failure then you are probably not qualified for this.
  176. @section Visual C++ produces many errors.
  177. Visual C++ is not compliant to the C standard and does not support
  178. the inline assembly used in FFmpeg.
  179. If you wish - for whatever weird reason - to use Visual C++ for your
  180. project then you can link the Visual C++ code with libav* as long as
  181. you compile the latter with a working C compiler. For more information, see
  182. the @emph{Visual C++ compatibility} section in the FFmpeg documentation.
  183. There have been efforts to make FFmpeg compatible with Visual C++ in the
  184. past. However, they have all been rejected as too intrusive, especially
  185. since MinGW does the job perfectly adequately. None of the core developers
  186. work with Visual C++ and thus this item is low priority. Should you find
  187. the silver bullet that solves this problem, feel free to shoot it at us.
  188. @section I have a file in memory / a API different from *open/*read/ libc how do i use it with libavformat ?
  189. You have to implement a URLProtocol, see libavformat/file.c in FFmpeg
  190. and libmpdemux/demux_lavf.c in MPlayer sources.
  191. @bye