[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ 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] | [ ? ] |
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] | [ ? ] |
For multithreaded MPEG* encoding, the encoded slices must be independent, otherwise thread n would practically have to wait for n-1 to finish, so it's quite logical that there is a small reduction of quality. This is not a bug.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use `-' as filename.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The audio is AC3 (a.k.a. A/52). AC3 decoding is an optional component in ffmpeg
as the component that handles AC3 decoding (liba52) is currently released under
the GPL. If you have liba52 installed on your system, enable AC3 decoding
with ./configure --enable-a52
. Take care: by
enabling AC3, you automatically change the license of libavcodec from
LGPL to GPL.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Windows does not support standard formats like MPEG very well, unless you install some additional codecs
The following list of video codecs should work on most Windows systems:
The following list of audio codecs should work on most Windows systems:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This is a well-known bug in the bt8x8 driver. For 2.4.26 there is a patch at (http://mplayerhq.hu/~michael/bttv-420-2.4.26.patch). This may also apply cleanly to other 2.4-series kernels.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Pass 'combfilter=1 lumafilter=1' to the bttv driver. Note though that 'combfilter=1' will cause somewhat too strong filtering. A fix is to apply (http://mplayerhq.hu/~michael/bttv-comb-2.4.26.patch) or (http://mplayerhq.hu/~michael/bttv-comb-2.6.6.patch) and pass 'combfilter=2'.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Try '-f image -img jpeg test%d.jpg'.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Some codecs, like MPEG-1/2, only allow a small number of fixed framerates. Choose a different codec with the -vcodec command line option.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Try a 'make distclean' in the ffmpeg source directory. If this does not help see (http://ffmpeg.org/bugreports.php).
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Both XviD and DivX (version 4+) are implementations of the ISO MPEG-4 standard (note that there are many other coding formats that use this same standard). Thus, use '-vcodec mpeg4' to encode these formats. The default fourcc stored in an MPEG-4-coded file will be 'FMP4'. If you want a different fourcc, use the '-vtag' option. E.g., '-vtag xvid' will force the fourcc 'xvid' to be stored as the video fourcc rather than the default.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Like most open source projects FFmpeg suffers from a certain lack of manpower. For this reason the developers have to prioritize the work they do and putting out releases is not at the top of the list, fixing bugs and reviewing patches takes precedence. Please don't complain or request more timely and/or frequent releases unless you are willing to help out creating them.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Because no one has taken on that task yet. FFmpeg development is driven by the tasks that are important to the individual developers. If there is a feature that is important to you, the best way to get it implemented is to undertake the task yourself.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Yes. Read the Developers Guide of the FFmpeg documentation. Alternatively, examine the source code for one of the many open source projects that already incorporate ffmpeg at (projects.php).
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
No. Only GCC is supported. GCC is ported to most systems available and there
is no 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 and Visual C++ compatibility sections in the FFmpeg documentation to find more information.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
No. These tools are too bloated and they complicate the build. Moreover, since only `gcc' is supported they would add little advantages in terms of portability.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ffmpeg is already organized in a highly modular manner and does not need to be rewritten in a formal object language. Further, many of the developers favor straight C; it works for them. For more arguments on this matter, read "Programming Religion" at (http://lkml.org/faq/lkmlfaq-15.html).
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug information. Those binaries are strip'd to create ffmpeg, ffplay, etc. If you need the debug information, used the *_g versions.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Yes, as long as the code is optional and can easily and cleanly be placed under #ifdef CONFIG_GPL without breaking anything. So for example a new codec or filter would be OK under GPL while a bugfix to LGPL code would not.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Common code is in its own files in libav* and is used by the individual codecs. They will not work without the common parts, you have to compile the whole libav*. If you wish, disable some parts with configure switches. You can also try to hack it and remove more, but if you had problems fixing the compilation failure then you are probably not qualified for this.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Visual C++ is not compliant to the C standard and does not support the inline assembly used in FFmpeg. If you wish - for whatever weird reason - to use Visual C++ for your project then you can link the Visual C++ code with libav* as long as you compile the latter with a working C compiler. For more information, see the Visual C++ compatibility section in the FFmpeg documentation.
There have been efforts to make FFmpeg compatible with Visual C++ in the past. However, they have all been rejected as too intrusive, especially since MinGW does the job perfectly adequately. None of the core developers work with Visual C++ and thus this item is low priority. Should you find the silver bullet that solves this problem, feel free to shoot it at us.
[Top] | [Contents] | [Index] | [ ? ] |
1. General Problems
1.1 I cannot read this file although this format seems to be supported by ffmpeg.2. Development
1.2 How do I encode JPEGs to another format ?
1.3 FFmpeg does not support codec XXX. Can you include a Windows DLL loader to support it ?
1.4 Why do I see a slight quality degradation with multithreaded MPEG* encoding ?
1.5 How can I read from the standard input or write to the standard output ?
1.6 Why does ffmpeg not decode audio in VOB files ?
1.7 Which codecs are supported by Windows ?
1.8 Why does the chrominance data seem to be sampled at a different time from the luminance data on bt8x8 captures on Linux?
1.9 How do I avoid the ugly aliasing artifacts in bt8x8 captures on Linux?
1.10 I have a problem with an old version of ffmpeg; where should I report it?
1.11 -f jpeg doesn't work.
1.12 Why can I not change the framerate?
1.13 ffmpeg does not work; What is wrong?
1.14 How do I encode XviD or DivX video with ffmpeg?
2.1 When will the next FFmpeg version be released? / Why are FFmpeg releases so few and far between?
2.2 Why doesn't FFmpeg support feature [xyz]?
2.3 Are there examples illustrating how to use the FFmpeg libraries, particularly libavcodec and libavformat ?
2.4 Can you support my C compiler XXX ?
2.5 Can I use FFmpeg or libavcodec under Windows ?
2.6 Can you add automake, libtool or autoconf support ?
2.7 Why not rewrite ffmpeg in object-oriented C++ ?
2.8 Why are the ffmpeg programs devoid of debugging symbols ?
2.9 I do not like the LGPL, can I contribute code under the GPL instead ?
2.10 I want to compile xyz.c alone but my compiler produced many errors.
2.11 Visual C++ produces many errors.
[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 | beginning of this chapter or previous chapter | 1 |
[ Up ] | Up | up section | 1.2 |
[ >> ] | FastForward | next chapter | 2 |
[Top] | Top | cover (top) of document | |
[Contents] | Contents | table of contents | |
[Index] | Index | concept index | |
[ ? ] | About | this page |
where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure: