Comment 12 for bug 575798

On Mon, May 10, 2010 at 01:13:23 (CEST), Doug McMahon wrote:

> While I forgot that the lucid mplayer uses the system ffmpeg libs - still don't see the connection to the faad2 package in lucid (libfaad
> It's my understanding that mplayer uses it's own internal faad decoder even in it's present lucid build.

In order to playback aac, mplayer has 3 options:

 - libavcodec (called ffaac)
 - system libfaad2 (faad2)
 - internal copy of faad2 (internal faad)

According to the analysis pasted above, the problem cannot be reproduced
with the attached testfile and the decoder shipped by the ubuntu
libavcodec package.

In ubuntu we generally avoid internal library copies, i.e. if mplayer
indeed uses the internal faad over the system libfaad2, then this would
be a (seperate) bug against the mplayer package, which should be fixed.

> This can be seen by removing libfaad2 (no faad2 libs installed
> whatsoever) - mplayer by default still decodes aac thru faad (internal)
> and does LC properly while Main contines to be the issue.

which indicates that the internal copy of faad in mplayer inhibits the
same problem. not very surprising.

> Further - as a small test the other day I built vlc 1.0.6 on lucid
> statically linked to faad2 -2.6.1 (source used in karmic)
>
> It plays aac LC files fine, exhibited the same (mis)behavior with aac
> Main

another indication that the libfaad2 package fails to playback aac main

thanks for your analysis!

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4