RFC: libav vs. ffmpeg, redux

RFC: libav vs. ffmpeg, redux

[Paul Eggleton]

Hi all,

A few years ago we made the switch from ffmpeg to libav (a mostly drop-in 
compatible fork), with fairly good justification at the time. However, it looks 
like Debian has just made the switch back to ffmpeg, citing a number of reasons 
- most notably more responsive security issue patching in recent history. 
Here's a page with their full reasoning:

  https://wiki.debian.org/Debate/libav-provider/ffmpeg

Gstreamer (gst-libav, specifically) has also just recently made the switch back 
for its internal copy:

  https://bugzilla.gnome.org/show_bug.cgi?id=751607

What do people think? Should we be looking to make the switch back in OE as 
well?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: RFC: libav vs. ffmpeg, redux

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 290 bytes --]

On 9 July 2015 at 11:24, Paul Eggleton <paul.eggleton@linux.intel.com>
wrote:

> What do people think? Should we be looking to make the switch back in OE as
> well?
>

I say we switch back to ffmpeg, and do it as soon as possible so we're not
making this change during M3.

Ross

[-- Attachment #2: Type: text/html, Size: 710 bytes --]

Re: [OE-core] RFC: libav vs. ffmpeg, redux

[Burton, Ross]

On 9 July 2015 at 11:24, Paul Eggleton <paul.eggleton@linux.intel.com>
wrote:

> What do people think? Should we be looking to make the switch back in OE as
> well?
>

I say we switch back to ffmpeg, and do it as soon as possible so we're not
making this change during M3.

Ross

Re: [OE-core] RFC: libav vs. ffmpeg, redux

[Christian Ege]

Am 09.07.2015 12:31 nachm. schrieb "Burton, Ross" <ross.burton@intel.com>:
>
> On 9 July 2015 at 11:24, Paul Eggleton <paul.eggleton@linux.intel.com>
> wrote:
>
> > What do people think? Should we be looking to make the switch back in
OE as
> > well?
> >
>
> I say we switch back to ffmpeg, and do it as soon as possible so we're not
> making this change during M3.
Switching to ffmpeg will be great, because kodi requires ffmpeg.

Another option could be supporting both.

Regards,
Christian
>
> Ross
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] RFC: libav vs. ffmpeg, redux

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 254 bytes --]

On 9 July 2015 at 11:35, Christian Ege <k4230r6@gmail.com> wrote:

> Another option could be supporting both.
>

I totally endorse having a layer that has the one that isn't in oe-core,
but oe-core should pick one and support it properly.

Ross

[-- Attachment #2: Type: text/html, Size: 661 bytes --]

Re: [OE-core] RFC: libav vs. ffmpeg, redux

[Burton, Ross]

On 9 July 2015 at 11:35, Christian Ege <k4230r6@gmail.com> wrote:

> Another option could be supporting both.
>

I totally endorse having a layer that has the one that isn't in oe-core,
but oe-core should pick one and support it properly.

Ross

Re: RFC: libav vs. ffmpeg, redux

[akuster808]

On 07/09/2015 03:24 AM, Paul Eggleton wrote:
> Hi all,
>
> A few years ago we made the switch from ffmpeg to libav (a mostly drop-in
> compatible fork), with fairly good justification at the time. However, it looks
> like Debian has just made the switch back to ffmpeg, citing a number of reasons
> - most notably more responsive security issue patching in recent history.
> Here's a page with their full reasoning:
>
>    https://wiki.debian.org/Debate/libav-provider/ffmpeg
>
> Gstreamer (gst-libav, specifically) has also just recently made the switch back
> for its internal copy:
>
>    https://bugzilla.gnome.org/show_bug.cgi?id=751607
>
> What do people think? Should we be looking to make the switch back in OE as
> well?
>

That make sense to me. Also libav has LICENSE_FLAGS = "commercial" so 
the change which will simplify things too.

- armin

> Cheers,
> Paul
>

Re: [OE-core] RFC: libav vs. ffmpeg, redux

[akuster808]

On 07/09/2015 03:24 AM, Paul Eggleton wrote:
> Hi all,
>
> A few years ago we made the switch from ffmpeg to libav (a mostly drop-in
> compatible fork), with fairly good justification at the time. However, it looks
> like Debian has just made the switch back to ffmpeg, citing a number of reasons
> - most notably more responsive security issue patching in recent history.
> Here's a page with their full reasoning:
>
>    https://wiki.debian.org/Debate/libav-provider/ffmpeg
>
> Gstreamer (gst-libav, specifically) has also just recently made the switch back
> for its internal copy:
>
>    https://bugzilla.gnome.org/show_bug.cgi?id=751607
>
> What do people think? Should we be looking to make the switch back in OE as
> well?
>

That make sense to me. Also libav has LICENSE_FLAGS = "commercial" so 
the change which will simplify things too.

- armin

> Cheers,
> Paul
>

Re: [oe] RFC: libav vs. ffmpeg, redux

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 242 bytes --]

On 9 July 2015 at 15:57, akuster808 <akuster808@gmail.com> wrote:

> That make sense to me. Also libav has LICENSE_FLAGS = "commercial" so the
> change which will simplify things too.
>

Why isn't that the case for ffmpeg too?

Ross

[-- Attachment #2: Type: text/html, Size: 660 bytes --]

Re: [OE-core] RFC: libav vs. ffmpeg, redux

[Burton, Ross]

On 9 July 2015 at 15:57, akuster808 <akuster808@gmail.com> wrote:

> That make sense to me. Also libav has LICENSE_FLAGS = "commercial" so the
> change which will simplify things too.
>

Why isn't that the case for ffmpeg too?

Ross

Re: RFC: libav vs. ffmpeg, redux

[Koen Kooi]

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

Paul Eggleton schreef op 09-07-15 om 12:24:
> Hi all,
> 
> A few years ago we made the switch from ffmpeg to libav (a mostly drop-in
>  compatible fork), with fairly good justification at the time. However,
> it looks like Debian has just made the switch back to ffmpeg, citing a
> number of reasons - most notably more responsive security issue patching
> in recent history. Here's a page with their full reasoning:
> 
> https://wiki.debian.org/Debate/libav-provider/ffmpeg
> 
> Gstreamer (gst-libav, specifically) has also just recently made the
> switch back for its internal copy:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=751607
> 
> What do people think? Should we be looking to make the switch back in OE
> as well?

As much as I like the libav guys, ffmpeg seems to win the popular vote which
makes it easier to use. Kodi/xbmc has been named, opencv is another.

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFVn9RlMkyGM64RGpERAqwwAJ9SXkQ8WFLRlweCx2CenlK3L1F34ACfZo+R
pQzjY9o32AwZTC+OCqpNLXE=
=HCXC
-----END PGP SIGNATURE-----

Re: [oe] RFC: libav vs. ffmpeg, redux

[Khem Raj]

On Thu, Jul 9, 2015 at 8:02 AM, Burton, Ross <ross.burton@intel.com> wrote:
> On 9 July 2015 at 15:57, akuster808 <akuster808@gmail.com> wrote:
>
>> That make sense to me. Also libav has LICENSE_FLAGS = "commercial" so the
>> change which will simplify things too.
>>
>
> Why isn't that the case for ffmpeg too?

it remains same, commercial is for the folks who ship the code to be
aware that there might be algorithms implemented in the code
which are governed by patents, so if you start making money on that
code then they might want a share of it. So you have to have agreement
with patent folks as ffmpeg code is not available under commercial
license.

Re: [OE-core] RFC: libav vs. ffmpeg, redux

[Khem Raj]

On Thu, Jul 9, 2015 at 8:02 AM, Burton, Ross <ross.burton@intel.com> wrote:
> On 9 July 2015 at 15:57, akuster808 <akuster808@gmail.com> wrote:
>
>> That make sense to me. Also libav has LICENSE_FLAGS = "commercial" so the
>> change which will simplify things too.
>>
>
> Why isn't that the case for ffmpeg too?

it remains same, commercial is for the folks who ship the code to be
aware that there might be algorithms implemented in the code
which are governed by patents, so if you start making money on that
code then they might want a share of it. So you have to have agreement
with patent folks as ffmpeg code is not available under commercial
license.