next steps with ffmpeg and mplayer
Reinhard Tartler
siretart at tauware.de
Thu Mar 5 16:26:47 UTC 2009
Christian Marillat <marillat at debian.org> writes:
> Reinhard Tartler <siretart at tauware.de> writes:
> [...]
>>>> mplayer is currently severly broken in unstable, see #516933. mennucc1
>>>> decided to update the internal ffmpeg copy to match debian's using a
>>>> dpatch. Since ffmpeg was updated, the mplayer package must do so as
>>>> well. However, I think we don't need that dpatch of mplayers copy of
>>>> ffmpeg matches the copy of the ffmpeg-debian package.
>
> Do you intent to build mplayer statically against the included ffmpeg
> in mplayer ?
Actually not. The security team actively hunts down code copies in
Debian.
> The main reason is that mplayer is 10% faster if linked statically
> with ffmpeg.
As seen on #mplayerdev this night:
23:37:54 < Mikachu> is there any speed difference between static and shared linking to ffmpeg?
23:38:22 <@DonDiego> static should be faster
23:38:36 <@DonDiego> but i haven't seen benchmarks recently
Day changed to 05 Mär 2009
00:01:07 <@uau> there's no reason why static would be faster
00:01:27 <@uau> however if the shared library is built with PIC then _that_ can cause slowdown
At least ffmpeg-debian is built with PIC only on architectures that
require it. Last time I've checked your ffmpegcvs, I think it has been
built PIC on all architectures.
I take this as reason to believe that dynamic linking mplayer against
libavcodec has no significant performance impact. However this would
need to be tested.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
More information about the pkg-multimedia-maintainers
mailing list