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.

74 lines
2.1KB

  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 ffserver doesn't not work.
  10. ffmpeg development is now concentrated on the codec and format
  11. handling. New developments broke ffserver, so don't expect it to work
  12. correctly. It is planned to fix it ASAP.
  13. @section I cannot read this file although this format seems to be suppored by ffmpeg.
  14. Even if ffmpeg can read the file format, it may not support all its
  15. codecs. Please consult the supported codec list in the ffmpeg
  16. documentation.
  17. @section I get audio/video synchro problems when grabbing.
  18. Currently, the grabbing stuff does not handle synchronisation
  19. correctly. You are free to correct it. It is planned to fix it ASAP.
  20. @section How do I encode jpegs to another format ?
  21. If the jpegs are named img1.jpg, img2.jpg, img3.jpg,..., use:
  22. @example
  23. ffmpeg -i img%d.jpg /tmp/a.mpg
  24. @end example
  25. @samp{%d} is replaced by the image number.
  26. @file{img%03d.jpg} generates @file{img001.jpg}, @file{img002.jpg}, etc...
  27. The same system is used for the other image formats.
  28. @section FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it ?
  29. No. FFmpeg only supports open source codecs. Windows DLLs are not
  30. portable, bloated and often slow.
  31. @section How can I read from the standard input or write to the standard output ?
  32. Use @file{-} as filename.
  33. @chapter Development
  34. @section Can you support my C compiler XXX ?
  35. No. Only GCC is supported. GCC is ported on most systems available and I
  36. don't see the need to pollute the source code with @code{#ifdef}s
  37. related to the compiler.
  38. @section I want to use ffmpeg or libavcodec under Windows. Can you support my proprietary C compiler XXX ?
  39. No. Use @code{mingw-gcc} available at @url{http://www.mingw.org/} to
  40. compile the code. It generates object files fully compatible with other
  41. windows compilers.
  42. @section Can you add automake, libtool or autoconf support ?
  43. No. These tools are too blowted and they complicate the build. Moreover,
  44. since only @samp{gcc} is supported they would add little advantages in
  45. terms of portability.
  46. @bye