are you (fedora devels) using fluendo codecs?

Tom "spot" Callaway tcallawa at redhat.com
Fri Nov 16 14:39:01 UTC 2007


On Fri, 2007-11-16 at 12:47 +0000, Bastien Nocera wrote:
> On Thu, 2007-11-15 at 23:54 -0500, Jesse Keating wrote:
> > On Fri, 16 Nov 2007 01:20:57 +0000
> > Bastien Nocera <bnocera at redhat.com> wrote:
> > 
> > > > Fluendo could use a non-closed source compiler (I suggest gcc) so
> > > > that the binaries could be made to not need execmem.  
> > > 
> > > I'm trying to find a way to show you're talking rubbish without being
> > > insulting, but I'm failing. The problem isn't the compiler, but the
> > > libraries used, in this case Intel's IPP library. It provides
> > > convenience functions for optimised decoding of a number of codecs,
> > > and various other optimised decoding routines.
> > > 
> > > Fluendo doesn't have access to the IPP library sources, so we're
> > > waiting for Intel to fix this. I'm not holding my breath.
> > 
> > Ok, fine, s/compiler/library/.  Are you really going to tell me that
> > it's impossible to build the mp3 library (and others) without using
> > closed source software?
> 
> It is extremely incovenient, as you need to reimplement, and reoptimise
> large portions of code.

Seriously, how optimized does the mp3 codec need to be? I used to play
mp3s on a Windows 3.1 box with 128 MB of memory. RPM Fusion is full of
players using gcc, and I've yet to run into a place where I needed to
optimize beyond -O2 with gcc.

~spot




More information about the devel mailing list