From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: libav vs. ffmpeg, redux
Date: Fri, 10 Jul 2015 16:19:17 +0200 [thread overview]
Message-ID: <mnok95$fuc$1@ger.gmane.org> (raw)
In-Reply-To: <2219152.1ss8pFxefq@peggleto-mobl.ger.corp.intel.com>
-----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-----
prev parent reply other threads:[~2015-07-10 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 10:24 RFC: libav vs. ffmpeg, redux Paul Eggleton
2015-07-09 10:30 ` Burton, Ross
[not found] ` <CAALGJZbmg2kqahBp5jFL4mk2N6upacQpmi9bpd3jSf5A-c4T8A@mail.gmail.com>
2015-07-09 11:41 ` [oe] " Burton, Ross
2015-07-09 14:57 ` akuster808
2015-07-09 15:02 ` [oe] " Burton, Ross
2015-07-11 5:46 ` Khem Raj
2015-07-10 14:19 ` Koen Kooi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mnok95$fuc$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox