[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Currently, the grabbing stuff does not handle synchronisation correctly. You are free to correct it. It is planned to fix it ASAP.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
No. FFmpeg only supports open source codecs. Windows DLLs are not portable, bloated and often slow.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use `-' as filename.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AC3 decoding is optional as the codec is currently released under the
GPL. Enable it with ./configure --enable-a52
. Take care: by
enabling AC3, you automatically change the license of libavcodec from
LGPL to GPL.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Yes. Read the Developers Guide of the FFmpeg documentation.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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 #ifdef
s
related to the compiler.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Yes, but the MinGW tools must be used to compile FFmpeg. You can link the resulting DLLs with any other Windows program. Read the Native Windows Compilation section in the FFmpeg documentation to have more information.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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.
[Top] | [Contents] | [Index] | [ ? ] |
[Top] | [Contents] | [Index] | [ ? ] |
1. General Problems
2. Development
[Top] | [Contents] | [Index] | [ ? ] |
Button | Name | Go to | From 1.2.3 go to |
---|---|---|---|
[ < ] | Back | previous section in reading order | 1.2.2 |
[ > ] | Forward | next section in reading order | 1.2.4 |
[ << ] | FastBack | previous or up-and-previous section | 1.1 |
[ Up ] | Up | up section | 1.2 |
[ >> ] | FastForward | next or up-and-next section | 1.3 |
[Top] | Top | cover (top) of document | |
[Contents] | Contents | table of contents | |
[Index] | Index | concept index | |
[ ? ] | About | this page |