All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/4] package/ffmpeg: bump to version 4.1
Date: Sun, 10 Feb 2019 11:01:05 +0100	[thread overview]
Message-ID: <1c95jfxr7e.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20190206104749.1ae23e1b@windsurf

Hi,

Am Wed, 06 Feb 2019 10:47:49 +0100 schrieb Thomas Petazzoni:

> Is there a stable version of gstreamer that was released and that is
> compatible with ffmpeg 4.x ? If so, that's what we want to use.

no:
https://bugzilla.gnome.org/show_bug.cgi?id=792900#c14
"I wouldn't worry about the backwards compatibility, but we would have to 
wait until 1.16 in that case. Can't be included in 1.14."

https://github.com/GStreamer/gst-libav/blob/master/NEWS
"GStreamer 1.16 has not been released yet. It is scheduled for release in
January/February 2019."

Only unstable 1.15.1 was released yet.

> If not, then presumably there are upstream GStreamer changes that make
> it compatible with ffmpeg 4.x, and we would like to see those patches
> backported rather than using home-grown patches.

No, upstream says backporting is not possible:
https://github.com/GStreamer/gst-libav/commit/
8886a016fce625e1c25a4902be4021196a6784a2#diff-
ff4e2dc4962dc25a1512353299992c8dR1400

"-   The gst-libav module in 1.14 will only build against older ffmpeg
    3.x versions and won?t build against the newly-released ffmpeg 4.0
    (as in RPM Fusion for Fedora 28) due to API changes. Use the
    internal ffmpeg copy instead if you build using autotools. This is
    fixed in git master / upcoming 1.16, but won?t be backported to the
    1.14 branch as it is rather intrusive and difficult to support both
    old and new APIs at the same time."

Regards, Bernd

PS: ffmpeg 4.1.1 was released.

  reply	other threads:[~2019-02-10 10:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 18:19 [Buildroot] [PATCH v3 0/4] *** Add Intel QuickSync support to ffmpeg *** Louis-Paul Cordier
2019-02-05 18:19 ` [Buildroot] [PATCH v3 1/4] package/intel-mediadriver: new package Louis-Paul Cordier
2019-04-16 20:26   ` Thomas Petazzoni
2019-02-05 18:19 ` [Buildroot] [PATCH v3 2/4] package/intel-mediasdk: " Louis-Paul Cordier
2019-04-16 20:28   ` Thomas Petazzoni
2019-02-05 18:19 ` [Buildroot] [PATCH v3 3/4] package/ffmpeg: bump to version 4.1 Louis-Paul Cordier
2019-02-06  8:47   ` Thomas Petazzoni
2019-02-06  9:33     ` lpdev at cordier.org
2019-02-06  9:47       ` Thomas Petazzoni
2019-02-10 10:01         ` Bernd Kuhls [this message]
2019-02-10 10:27           ` Thomas Petazzoni
2019-02-10 18:53             ` Bernd Kuhls
2019-02-05 18:19 ` [Buildroot] [PATCH v3 4/4] package/ffmpeg: enable Intel QuickSync support Louis-Paul Cordier
2019-04-16 20:28   ` Thomas Petazzoni
2019-02-25  9:05 ` [Buildroot] [PATCH v3 0/4] *** Add Intel QuickSync support to ffmpeg *** lpdev at cordier.org

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=1c95jfxr7e.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.