My thoughts on Slackware, life and everything

ffmpeg fully supports webm video

Today, the ffmpeg developers have completed the integration of the Google-sponsored VP8 codec and associated new WebM video container format.

The WebM video container format as well as VP8 decoding were added a little while ago, and the last part – VP8 video encoding – has entered the repository now. External patches are no longer required.

The ffmpeg package which I had built for Slackware 13.1 a couple of days ago, can encode VP8 too but I had to apply the patches made available by the WebM project (and which have now been more or less completely absorbed by ffmpeg). I’ll rebuild my ffmpeg package soon, getting rid of the patches, thus having a less complex build.

The only thing that seems to be missing compared to the patches from the WebM project, are the preset files specific to the VP8 encoder. As an example, ffmpeg has several preset files for x264 – they greatly simplify the ffmpeg commandline by gathering a lot of encoder settings into one configuration file. I’ll look at how I can add those presets to my package, in case the ffmpeg folk don’t do it first.



  1. Ponce

    hi eric,

    I tried to make some slackbuilds specific for libvpx, rtmpdump and added some stuff to’s ffmpeg based on the hints I found on yours ffmpeg slackbuild and I built some packages based on today’s libvpx, x264 and ffmpeg snapshots that seem to work

    thanks for the hints, vp8 codec is very fine and at our institution we are experimenting on it for our html5 streaming projects.

    I added also rtmp support cause we are trying also erlyvideo

  2. Ponce

    the slackbuilds of libvpx and rtmpdump are now on 🙂

    also, ffmpeg 0.6 is out

  3. Max Lapshin

    Hi, I’m author of erlyvideo.

    There is buzz around webm, so I’m really interested if it is required? Maybe I should add support for it?

  4. indix

    Why is libvorbis missing in your slackbuild? I can be wrong, but without libvorbis ffmpeg can’t produce proper webm video. Anyway, thanks for your great work Eric, I really appreciate your packages for slackware 64-bit.

  5. alienbob

    Well, since libvorbis is an integral part of Slackware, I did not add that as a static lib to ffmpeg. While compiling ffmpeg, the Slackware Vorbis library will be picked up and the resulting ffmpeg binary supports vorbis audio just fine.


  6. indix

    Eric, when I try to encode some webm video with ‘-acodec libvorbis’ option it complains like this: Unknown encoder ‘libvorbis’. And I have libvorbis-1.2.3-x86_64-1 in my slackware! I’m compiling ffmpeg with your slackbuild and ‘–enable-libvorbis’ and will give it a try.

  7. alienbob

    @indix –

    I had to think deep about this, until I checked the build log for the package.
    Ffmpeg _can_ use libvorbis but by default it will use its own internal implementation of the Vorbix codec.
    In my package, that internal version is compiled in. That codec is not called “libvorbis” (which is the name for the external libvorbis codec) but just “vorbis”.

    You can get the list of available codecs with the command “ffmpeg -codecs”.


  8. indix

    Thank you Eric, works perfect now.

  9. Peter

    ffmpeg.SlackBuild fails to build ffmpeg 8.2 if libx264 is already installed. But you might not notice the error message. The script continues and builds a .tgz package which contains lots of stuff – but no /usr.bin/ffmpeg.

    Uninstalling libx264 then all was OK.

    ffmpeg.SlackBuild also works OK with the latest ffmpeg 0.8.5 – after editing the version number (of course!).

    Keep up the good work.


  10. alienbob

    Hi Peter

    I am currently compiling ffmpeg-0.8.5 into a package and I have fixed the SlackBuild so that it no longer fails in the presence of an already installed x264 package.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2024 Alien Pastures

Theme by Anders NorenUp ↑