All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Gstreamer 0.10 vs. Gstreamer 1.0, gst-ffmpeg vs. gst-libav, ffmpeg vs. libav confusion
Date: Sat, 19 Jan 2013 05:00:16 +0200	[thread overview]
Message-ID: <50FA0C40.30907@petroprogram.com> (raw)

Hi everyone

Im going to start building some multimedia capabilities to my buildroot
system soon and
hit to this confusion about gstreamer 0.10 vs. gstreamer 1.0, gst-ffmeg
vs. gst-libav,
and ffmpeg vs libav.

What I have read from
http://www.linuxfromscratch.org/blfs/view/svn/multimedia/gstreamer.html
and all over the Net I have come to following conclusion:

1 )
gstreamer 0.10 and gstreamer 1.0  (and their plugins) are totally
incompatible versions but if need to be
they can be installed both into same system.

2 )
gstreamer 0,10 has the following plugins:
gst-plugins-bad 0.10.x
gst-plugins-good 0.10.x
gst-plugins-ugly 0.10.x
and
gst-plugins-ffmpeg 0.10.x which uses ffmpeg library

3 )
gstreamer 1,0 has the following plugins:
gst-plugins-bad 1.0.x
gst-plugins-good 1.0.x
gst-plugins-ugly 1.0.x
and
gst-plugins-libav 1.0.x which uses libav library (either external or
internal, tarball provided)

4 ) libav is a fork of ffmpeg

5 ) ffmpeg is not dead but kicking and all well and alive.


In the latest git of buildroot there is gstreamer 0.10.x series and all
it's 0.10.x series plugins which is all good and well
and I think it should be keeped in that way.

But what about 1.0 ?
Maybe gstreamer 1.0.x  package for buildroot should be called
gstreamer-1.0 or something similar
and also in it's Config.in file BR2_PACKAGE_GSTREAMER1.0 ???
And it's own plugins named similary with just -1.0 suffix ?
With the exception of gst-libav, which is renamed gst-ffmpeg for
gstreamer 1.0


And is it worth adding libav as an separate package to buildroot at all
or just use the internal version provided by gst-libav plugin
when compiling ?

Best Regards
Stefan

P.S.
Hate it when people have to make things difficult to end users just
because large egos:
http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html












-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130119/b8877d57/attachment-0001.html>

             reply	other threads:[~2013-01-19  3:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19  3:00 Stefan Fröberg [this message]
2013-01-19 19:24 ` [Buildroot] Gstreamer 0.10 vs. Gstreamer 1.0, gst-ffmpeg vs. gst-libav, ffmpeg vs. libav confusion Arnout Vandecappelle
2013-01-19 21:49   ` Peter Korsgaard
2013-01-20 12:14   ` Stefan Fröberg

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=50FA0C40.30907@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --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.