Linux Ffmpeg Binaries F.A.Q.

What is a static binary?

Usually an executable binary ("program") depends on other libraries to work or extend its functionality, while providing modularity. These external libraries come in the form of dll files in Microsoft Windows operating systems. or ".so" files in Linux/Unix. Because of these external requirements you can't just usually copy a .exe between PCs and expect it to work, or in Linux systems software must be compiled or use a binary specially compiled for your distribution.

A static binary, on the other hand, includes all the dependencies that the program needs to work within the file, increasing the portability between systems of the same operating system.

Why use a static binary?

You should use a static Ffmpeg binary if:

  • Your Linux distribution does not offer a decent build of Ffmpeg, i.e. lack of popular codecs like x264.
  • You can't compile Ffmpeg no matter how hard you bang your head against the wall, or you can't afford to pay a sysadmin to compile it for you.
  • You don't have the permission to install software in your server by the usual means (shared server).
  • The previous options are meaningless to you, or you are just too lazy :)
  • You can spare 5 minutes to provide feedback after using the binary so we can improve.

I have an online video gallery, but my provider does not support Ffmpeg. Does it work in a shared server?

I'm glad you asked! This static binary is mainly intended for use in environments where the usual methods of installing Ffmpeg does not work, like shared servers.

Ffmpeg, and video conversion in general, consumes a big deal of CPU and server resources. If you run Ffmpeg in a shared server frequently your provider probably won't be happy and may cancel your account, or will kindly suggest you to upgrade to a VPS or dedicated server.

Some shared hosting companies provide a version of Ffmpeg, but sometimes it is too old or lack of some bleeding edge codecs or important features you can take advantage of.

IMPORTANT: I strongly encourage you to ask your server provider before using the binaries in a shared server. I cannot be help responsible if your account is cancelled because of the high usage of resources Ffmpeg makes!

If you are on a shared server ask your host if you are allowed to use a static Ffmpeg binary. They will use a lot of server resources so you need to ask your host before you use it. If you don't, they might cancel your account without warning. We are not responsible for this.

Who should use these binaries?

The optimum recommended way of installing Ffmpeg and the codecs in your system is to compile them from the source code, or download a binary compiled specifically for your distribution and processor type. Think of the statically compiled binary as a last resort.

What does the binary include?

The binaries includes ffmpeg and some external codecs required to add support for popular video and audio codecs.  We have released two flavours of the build:

  • ffmpeg "lite":  Includes ffmpeg plus the mp3 lame codec. Intented for basic usage: video resize, thumbnail generation, mp3 conversion, encoding in Flash video format...
  • ffmpeg "full": Includes a wider coverage of video and audio codecs: faac, faad, amr, xvid, theora, vorbis, x264, amr.

Licensing

The binaries is a mere compilation of the original source codec. By no means we modify the code of ffmpeg or codecs.

FFmpeg is licensed under the GNU General Public License (GPL) version 2 license

LAME in licensed under the LGPL license

FAAD2 is licensed under GNU General Public License (GPL) version 2 license

FAAC is licensed under the LGPL license

Theora and Vorbis are licensed under BSD license

xvid is released under GNU GPL license

x264 is released under GNU GPL license

opencore-amr is released under Apache License V2.0

 

Facebook MySpace Twitter Digg Delicious Stumbleupon Google Bookmarks RSS Feed 

Copyright © 2009-2010 Video Conversion Blog | Your Details | Terms of Use
This is a Free resource for webmasters and system administrators.