From: Fabrice Bellard Date: Mon, 4 Nov 2002 18:50:04 +0000 (+0000) Subject: updated FAQ - converted it to texinfo X-Git-Tag: v0.5~17098 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7ff56c72b204e2b11ca90c7b2ef7575a63e5f6bc;p=platform%2Fupstream%2Flibav.git updated FAQ - converted it to texinfo Originally committed as revision 1158 to svn://svn.ffmpeg.org/ffmpeg/trunk --- diff --git a/doc/FAQ b/doc/FAQ deleted file mode 100644 index 4ee34ec..0000000 --- a/doc/FAQ +++ /dev/null @@ -1,41 +0,0 @@ - -1) ffserver doesn't not work. - -ffmpeg development is now concentrated on the codec and format -handling. New developments broke ffserver, so don't expect it to work -correctly. It is planned to fix it ASAP. - -2) I cannot read this AVI file. - -Even if ffmpeg can read the AVI format, it does not support all its -codecs. Please consult the supported codec list on the ffmpeg project -page. - -3) I cannot read this Real Audio/Video file. - -See (2). ffmpeg only supports Real Video 1.0 and AC3 as Real -codecs. It mean that you cannot view files encoded with real tools -after version 5.0. - -4) I get audio/video synchro problems when grabbing. - -Currently, the grabbing stuff does not handle synchronisation -correctly. You are free to correct it. It is planned to fix it ASAP. - -5) How do I encode jpegs to another format ? - -If the jpegs are named img1.jpg, img2.jpg, img3.jpg,..., use: - - ffmpeg -i img%d.jpg /tmp/a.mpg - -'%d' is replaced by the image number. - -'img%03d.jpg' generates img001.jpg, img002.jpg, etc... - -The same system is used for the other image formats. - -6) FFmpeg does not support codec XYZ. Can you include a Windows DLL - loader to support it ? - -No ! FFmpeg only supports open source codecs. Windows DLLs are not -portable, bloated and often slow. diff --git a/doc/faq.html b/doc/faq.html new file mode 100644 index 0000000..6af28f0 --- /dev/null +++ b/doc/faq.html @@ -0,0 +1,139 @@ + + + + +FFmpeg FAQ + + +

FFmpeg FAQ

+

+

+

Table of Contents

+ +

+ +

+FFmpeg FAQ + + + + +

1. General Problems

+ + + +

1.1 ffserver doesn't not work.

+ +

+ffmpeg development is now concentrated on the codec and format +handling. New developments broke ffserver, so don't expect it to work +correctly. It is planned to fix it ASAP. + + + + +

1.2 I cannot read this file although this format seems to be suppored by ffmpeg.

+ +

+Even if ffmpeg can read the file format, it may not support all its +codecs. Please consult the supported codec list in the ffmpeg +documentation. + + + + +

1.3 I get audio/video synchro problems when grabbing.

+ +

+Currently, the grabbing stuff does not handle synchronisation +correctly. You are free to correct it. It is planned to fix it ASAP. + + + + +

1.4 How do I encode jpegs to another format ?

+ +

+If the jpegs are named img1.jpg, img2.jpg, img3.jpg,..., use: + + + +

+  ffmpeg -i img%d.jpg /tmp/a.mpg
+
+ +

+`%d' is replaced by the image number. + + +

+`img%03d.jpg' generates `img001.jpg', `img002.jpg', etc... + + +

+The same system is used for the other image formats. + + + + +

1.5 FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it ?

+ +

+No. FFmpeg only supports open source codecs. Windows DLLs are not +portable, bloated and often slow. + + + + +

2. Development

+ + + +

2.1 Can you support my C compiler XXX ?

+ +

+No. Only GCC is supported. GCC is ported on most systems available and I +don't see the need to pollute the source code with #ifdefs +related to the compiler. + + + + +

2.2 I want to use ffmpeg or libavcodec under Windows. Can you support my proprietary C compiler XXX ?

+ +

+No. Use mingw-gcc available at http://www.mingw.org/ to +compile the code. It generates object files fully compatible with other +windows compilers. + + + + +

2.3 Can you add automake, libtool or autoconf support ?

+ +

+No. These tools are too blowted and they complicate the build. Moreover, +since only `gcc' is supported they would add little advantages in +terms of portability. + + +

+This document was generated on 4 November 2002 using +texi2html 1.56k. + + diff --git a/doc/faq.texi b/doc/faq.texi new file mode 100644 index 0000000..1adc434 --- /dev/null +++ b/doc/faq.texi @@ -0,0 +1,69 @@ +\input texinfo @c -*- texinfo -*- + +@settitle FFmpeg FAQ +@titlepage +@sp 7 +@center @titlefont{FFmpeg FAQ} +@sp 3 +@end titlepage + + +@chapter General Problems + +@section ffserver doesn't not work. + +ffmpeg development is now concentrated on the codec and format +handling. New developments broke ffserver, so don't expect it to work +correctly. It is planned to fix it ASAP. + +@section I cannot read this file although this format seems to be suppored by ffmpeg. + +Even if ffmpeg can read the file format, it may not support all its +codecs. Please consult the supported codec list in the ffmpeg +documentation. + +@section I get audio/video synchro problems when grabbing. + +Currently, the grabbing stuff does not handle synchronisation +correctly. You are free to correct it. It is planned to fix it ASAP. + +@section How do I encode jpegs to another format ? + +If the jpegs are named img1.jpg, img2.jpg, img3.jpg,..., use: + +@example + ffmpeg -i img%d.jpg /tmp/a.mpg +@end example + +@samp{%d} is replaced by the image number. + +@file{img%03d.jpg} generates @file{img001.jpg}, @file{img002.jpg}, etc... + +The same system is used for the other image formats. + +@section FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it ? + +No. FFmpeg only supports open source codecs. Windows DLLs are not +portable, bloated and often slow. + +@chapter Development + +@section Can you support my C compiler XXX ? + +No. Only GCC is supported. GCC is ported on most systems available and I +don't see the need to pollute the source code with @code{#ifdef}s +related to the compiler. + +@section I want to use ffmpeg or libavcodec under Windows. Can you support my proprietary C compiler XXX ? + +No. Use @code{mingw-gcc} available at @url{http://www.mingw.org/} to +compile the code. It generates object files fully compatible with other +windows compilers. + +@section Can you add automake, libtool or autoconf support ? + +No. These tools are too blowted and they complicate the build. Moreover, +since only @samp{gcc} is supported they would add little advantages in +terms of portability. + +@bye