Select provider of libav* libraries

[Bálint Réczey]

Hi,

2014-08-27 16:52 GMT+02:00 Reinhard Tartler <siretart at gmail.com>:
>
> On Aug 27, 2014 10:43 AM, "Fabian Greffrath" <fabian at greffrath.com> wrote:
>>
>> Am Mittwoch, den 27.08.2014, 09:52 +0200 schrieb Matteo F. Vescovi:
>> > Libav for me, of course.
>>
>> I am for libav for the next stable release. However, I am open for
>> anything else after that. To be honest, I recently find the sheer number
>> of "my bug instantly vanished once I replaced libav with ffmpeg" reports
>> a bit emberrassing.
>
> Did you check how many of those bugs are fixed in a later libav upstream
> release? Note that even the current libav release frequency is tough for
> Debian, even faster releases won't make integration any easier.
If Libav 11 fixes #742896 and #741170 I will be very happy.

>
>> > I've spent too much time on getting it working fine with Blender
>> > that it'd be crazy to change it now. ;-)
>>
>> Then Bálint must clearly be crazy to do all the porting work the other
>> way round for XBMC. ;)
>
> Xbmc works best with its embedded copy of FFmpeg. I predict similar problems
> with an outdated system copy of FFmpeg.  The time spent in fixing that does
> not seem significantly smaller than fixing bugs in libav.
While it is true that XBMC builds with an internal FFmpeg copy they
switched a vanilla version instead of carrying many patches
themselves.
Usually they target latest stable release. For Debian if we can update
to the latest XBMC right before the freeze (I can assure that) and we
update to latest FFmpeg at the same time (FFmpeg maintainer probably
targets this as well) then we don't have to do extra work, upstream
already performed the integration.
I don't know how much time is needed for fixing Libav bugs affecting
XBMC, but if they are as easy as switching to FFmpeg, then please push
their resolution upstream.

Cheers,
Balint