Re: ffmpeg

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Georg Seidel wrote:
| Maybe we should write a ffmpeg input driver for the frbinmodule.
| It's used by a lot of applications
| (mplayer, xine, video lan, veejay, ...).
| It builds on windows (vlc nicely proofs that).

It also supports non x86 plattforms like ppc and sparc64.

| We could avoid the libavifile problems (libavifile seems
| really not well maintained).

But avifile supports using binary win32 codec dlls and ffmpeg not.

| The ffmpeg mailinglist is much more active than the avifile
| mailinglist.

| I am currently looking at the ffmpeg api....

| We already discussed ffmpeg shortly, and someone (I believe it
| was martin) said that you had to include the ffmpeg sources
| if you use it.

It seems that ffmpeg doesn't guarantee a stable api. Most projects that
use ffmpeg have its own copy in their source tree and link static to the
lib to avoid api incompatibilities. And most distributions don't provide
~ -devel packages and .so file of ffmpeg for the same reason.

| I don't see why this is true. The latest release is from september
| 2003. If this is sufficient for our needs there should be no
| problem.

The other projects like mplayer also just take the cvs head and include
it in their projects. But if the september release is stable and good in
video playback, why shouldn't we try the release first.

Martin

- --
GnuPG (ID B3D1B1BB) C2F4 F775 5022 1891 48F4  761D 0A6D E2E7 B3D1 B1BB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA2KjeCm3i57PRsbsRAsm1AKCkxIVf2ywpT68JTbC+qlNH49FCGgCgq0as
9xyrjOVdJT/semgsLB2M7PA=
=FlCP
-----END PGP SIGNATURE-----