Quote:
|
Originally Posted by keratos
What is ffmpeg? How does it fit in with mencoder - is it an alternate application or simply a codec used by mencoder.
|
It’s both (sort of). The project called
ffmpeg implements various codecs as libraries. Historically, it started out as just part of mplayer (i.e., a bunch of
internal libraries used only by mplayer). Eventually, these libraries became big enough (and useful enough) to become a standalone project. The libraries I’m thinking of are named libavcodec (i.e., “lavc”), libavformat, libavutil, libpostproc, and libswscale. Incidentally, the project that delivers these libraries (named ffmpeg) comes with a program that uses them which is itself named “ffmpeg”. Of course the program ffmpeg can use other libraries (depending on how it was built). For example, my ffmpeg program uses these codec libraries (in addition to the ffmpeg libraries themselves):
- liba52
- libdts
- libfaac
- libfaad
- libmp3lame
- libmp4v2
- libogg
- libtheora
- libvorbis
- libvorbisenc
- libx264
- libxvidcore
(this information found by running “ldd /usr/bin/ffmpeg” and filtering out non-codec libraries).
Quote:
|
Originally Posted by keratos
Also, why do apps that use ffmeg direct seem to encode much faster than those that use mencoder
|
I don’t think this is true. At least not if you tell both to use the same libraries for encoding (usually lavc). You can probably construct a situation (e.g., tell mplayer to use lame and tell ffmpeg to use lavc) in which one beats the other in “speed”
