Comments on: VP8 And FFmpeg

By: Hanspeter

Hanspeter — Tue, 01 Jun 2010 16:39:03 +0000

Doug: your issue is that libvpx-0.9.0 has the headers in $PREFIX/include, but ffmpeg-svn looks for them in $PREFIX/vpx/. So update to libvpx-git. But now ffmpeg has the issue that Hellfred has stated in comment #9.

By: Hellfred

Hellfred — Sun, 30 May 2010 16:12:17 +0000

doug:
Maybe you have to configure FFmpeg with --enable-nonfree to get latest libvpx to work with FFmpeg: http://git.ffmpeg.org/?p=ffmpeg;a=commitdiff;h=b706fceb7a10538abf1e74c27c5584d634bfdb04

By: doug

doug — Wed, 26 May 2010 21:37:09 +0000

It seems as if ffmpeg is hardcoded to reject encoding now. Adding the lines to configure to have encoding work break it with vpx_encoder.h and friends automatically cause it to fail, even if libraries are there…

By: Anonymous

Anonymous — Mon, 24 May 2010 19:44:15 +0000

Thanks for the info Mike. Until ffmpeg does roll their own vp8 though, I’d like to get it into my ffmpeg binaries, so I don’t want to install libvpx.

I presume my steps are:
make the ffmpeg encoder/decoder find the vpx includes,
link in the libvpx static library?

Do you know of a standard ffmpeg build method to do that, or should I patch the makefiles?

Bruce

By: Conan Kudo (ニール・ゴンパ)

Conan Kudo (ニール・ゴンパ) — Sun, 23 May 2010 08:33:48 +0000

Well…. I’ve got the insane order to add a CMake buildsystem for libvpx… Only that I can’t understand what the hell the current buildsystem DOES!!!! I barely understand autotools (probably about as much as anyone else), but at least I can figure out how to make a CMake script from an autotools one.

But this? This is a mess…. Is there anybody that knows WHAT the buildsystem is supposed to do?

By: Mirkus

Mirkus — Fri, 21 May 2010 18:43:34 +0000

Realized his mistake.
cd ~/libvpx
./configure –target=x86-linux-gcc
make
make install
Folder vpx-vp8-nodocs-x86-linux-v0.9.0 generated
a thank you for the article and help.

By: Multimedia Mike

Multimedia Mike — Fri, 21 May 2010 18:04:35 +0000

@Mirkus: If the ‘make’ step succeeded, then the stuff probably got build somewhere, just in another strangely-named path depending on your OS and CPU architecture. From where you built, ‘find . -name simple_decoder’ and you will find where the binaries are built. Go play with those binaries until we get better at hooking libvpx up to FFmpeg.

By: Mirkus

Mirkus — Fri, 21 May 2010 17:33:41 +0000

Hello
I tried to install libvpx, but I can not.
I am not clear what should be done
after I enter. /configure and then make?

vpx-vp8-nopost-nodocs-generic-gnu-v0.9.0 I can not generate.
where the folder is include and lib, the files which must be manually copied to /usr/local/include and /usr/local/lib ?

By: Multimedia Mike

Multimedia Mike — Fri, 21 May 2010 14:50:06 +0000

@John: Thanks for the tip. I knew there would be hiccups early in the process and I still think all that Google has managed in this VP8 front is incredible.

By: John Koleszar

John Koleszar — Fri, 21 May 2010 14:43:21 +0000

Mike,

You got bit by the build system not not working as you’d expect. Unexpected behavior is a legit bug, just haven’t had time to polish it up — was designed with different goals in mind. No autodetect because the cross-compile case was more common than not. Add –target=x86-linux-gcc (or x86_64-…) to get an optimized build, and add –disable-multithread if you don’t want the pthreads dependency.