GStreamer multimedia framework
Find a file
David Schleef 277ab581df Getting tired of debugging. Disabled all the unreffing of plugins and features, which fixes the segfaults, but of co...
Original commit message from CVS:
* check/gst/gstplugin.c:
* gst/gstelementfactory.c:
* gst/gstplugin.c:
* gst/gstpluginfeature.c:
* gst/gstregistry.c:
Getting tired of debugging.  Disabled all the unreffing of
plugins and features, which fixes the segfaults, but of
course leaks like crazy.  At least playbin works.
2005-09-16 04:54:24 +00:00
check Getting tired of debugging. Disabled all the unreffing of plugins and features, which fixes the segfaults, but of co... 2005-09-16 04:54:24 +00:00
common@62cd70d46e check/gst/gstplugin.c: More testing 2005-09-16 03:46:14 +00:00
components don't mix tabs and spaces 2004-03-15 19:27:17 +00:00
docs docs/gst/: Documentation updates for registry changes. 2005-09-15 00:42:03 +00:00
examples maintenance updates 2005-09-05 11:54:55 +00:00
gst Getting tired of debugging. Disabled all the unreffing of plugins and features, which fixes the segfaults, but of co... 2005-09-16 04:54:24 +00:00
include configure.ac: remove all mmx stuff, because it's not used. 2004-12-14 06:20:10 +00:00
libs some whitespace to trigger a build 2005-09-16 00:08:15 +00:00
pkgconfig need to add -lcheck to the pkgconfig file 2005-09-04 11:01:44 +00:00
plugins check/gst/gstplugin.c: More testing 2005-09-16 03:46:14 +00:00
po po/POTFILES.in: remove gst-register.c 2005-09-15 00:48:45 +00:00
scripts gst/gstelement.h (GstState): Renamed from GstElementState, changed to be a normal enum instead of flags. 2005-09-02 15:42:00 +00:00
tests Getting tired of debugging. Disabled all the unreffing of plugins and features, which fixes the segfaults, but of co... 2005-09-16 04:54:24 +00:00
testsuite gst/gstelement.h (GstState): Renamed from GstElementState, changed to be a normal enum instead of flags. 2005-09-02 15:42:00 +00:00
tools remove 2005-09-15 00:13:26 +00:00
win32 gst/gstelement.h (GstState): Renamed from GstElementState, changed to be a normal enum instead of flags. 2005-09-02 15:42:00 +00:00
.gitignore ignore more; fix README 2005-06-17 08:59:41 +00:00
.gitmodules Added a first stab at a better clocking system. 2002-02-03 20:07:09 +00:00
AUTHORS put the same mail for Zaheer Merali everywhere 2004-12-11 13:42:02 +00:00
autogen.sh maintenance updates 2005-09-05 17:55:10 +00:00
ChangeLog Getting tired of debugging. Disabled all the unreffing of plugins and features, which fixes the segfaults, but of co... 2005-09-16 04:54:24 +00:00
CHANGES-0.9 Some docs updates 2005-07-27 18:33:03 +00:00
configure.ac configure.ac: Add -no-undefined to GST_PLUGIN_LDFLAGS (bug #316076) 2005-09-15 05:58:37 +00:00
COPYING COPYING: replace by LGPL (former COPYING.LIB). The core is completely licensed LGPL. 2004-03-29 13:32:32 +00:00
DEVEL more registry fixes 2002-04-12 18:50:48 +00:00
DOCBUILDING fix really old / no more relevant info on devhelp support/integration 2004-09-27 19:59:08 +00:00
gst-element-check.m4 Only check for gst-inspect if we haven't already found it in previous element check runs 2005-01-25 14:03:12 +00:00
gst-element-check.m4.in Only check for gst-inspect if we haven't already found it in previous element check runs 2005-01-25 14:03:12 +00:00
gstreamer.spec.in check/: adding a test for pipelines and state changes 2005-09-09 12:02:41 +00:00
idiottest.mak idiottest was failing because of change of PLUGIN_USE_SRCDIR to 2001-06-19 12:53:05 +00:00
INSTALL initial checkin 2000-01-30 09:03:00 +00:00
LICENSE Adding explicit license information, since quite a large number of source files don't have the LGPL header. This is ... 2000-08-05 03:53:00 +00:00
MAINTAINERS adding more people to maintainers doc and minor cosmetic change to REQUIREMENTS doc 2004-12-17 14:10:59 +00:00
Makefile.am enable docs build for distcheck 2005-09-03 14:20:10 +00:00
NEWS releasing 0.9.2 2005-09-06 14:02:17 +00:00
README releasing 0.9.2 2005-09-06 14:02:17 +00:00
RELEASE releasing 0.9.2 2005-09-06 14:02:17 +00:00
REQUIREMENTS adding more people to maintainers doc and minor cosmetic change to REQUIREMENTS doc 2004-12-17 14:10:59 +00:00
stamp.h.in initial checkin 2000-01-30 09:03:00 +00:00
TODO have a real TODO, move old TODO 2005-06-09 12:03:04 +00:00

WHAT IT IS
----------
This is GStreamer, a framework for streaming media.

This package is in the 0.9.x series.  This means that this is a
development series leading up to a stable 0.10.x series.
You have been warned.

GStreamer 0.9 development series - Hung by a Thread
---------------------------------------------------

Starring

  GSTREAMER

The core around which all other modules revolve.  Base functionality and
libraries, some essential elements, documentation, and testing.

  BASE

A well-groomed and well-maintained collection of GStreamer plug-ins and
elements, spanning the range of possible types of elements one would want
to write for GStreamer.  

And introducing, for the first time ever, on the development screen ...

  THE GOOD

 --- "Such ingratitude.  After all the times I've saved your life."

A collection of plug-ins you'd want to have right next to you on the
battlefield.  Shooting sharp and making no mistakes, these plug-ins have it
all: good looks, good code, and good licensing.  Documented and dressed up
in tests.  If you're looking for a role model to base your own plug-in on,
here it is.

If you find a plot hole or a badly lip-synced line of code in them,
let us know - it is a matter of honour for us to ensure Blondie doesn't look
like he's been walking 100 miles through the desert without water.

  THE UGLY

  --- "When you have to shoot, shoot.  Don't talk."

There are times when the world needs a color between black and white.
Quality code to match the good's, but two-timing, backstabbing and ready to
sell your freedom down the river.  These plug-ins might have a patent noose
around their neck, or a lock-up license, or any other problem that makes you
think twice about shipping them.

We don't call them ugly because we like them less.  Does a mother love her
son less because he's not as pretty as the other ones ? No  - she commends
him on his great personality.  These plug-ins are the life of the party.
And we'll still step in and set them straight if you report any unacceptable
behaviour - because there are two kinds of people in the world, my friend:
those with a rope around their neck and the people who do the cutting.

  THE BAD

  --- "That an accusation?"

No perfectly groomed moustache or any amount of fine clothing is going to
cover up the truth - these plug-ins are Bad with a capital B. 
They look fine on the outside, and might even appear to get the job done, but
at the end of the day they're a black sheep. Without a golden-haired angel
to watch over them, they'll probably land in an unmarked grave at the final
showdown.

Don't bug us about their quality - exercise your Free Software rights,
patch up the offender and send us the patch on the fastest steed you can
steal from the Confederates. Because you see, in this world, there's two
kinds of people, my friend: those with loaded guns and those who dig.
You dig.

The Lowdown
-----------

  --- "I've never seen so many plug-ins wasted so badly."

GStreamer Plug-ins has grown so big that it's hard to separate the wheat from
the chaff.  Also, distributors have brought up issues about the legal status
of some of the plug-ins we ship.  To remedy this, we've divided the previous
set of available plug-ins into four modules:

- gst-plugins-base: a small and fixed set of plug-ins, covering a wide range
  of possible types of elements; these are continuously kept up-to-date
  with any core changes during the development series.

  - We believe distributors can safely ship these plug-ins.
  - People writing elements should base their code on these elements.
  - These elements come with examples, documentation, and regression tests.

- gst-plugins-good: a set of plug-ins that we consider to have good quality
  code, correct functionality, our preferred license (LGPL for the plug-in
  code, LGPL or LGPL-compatible for the supporting library).

  - We believe distributors can safely ship these plug-ins.
  - People writing elements should base their code on these elements.
 
- gst-plugins-ugly: a set of plug-ins that have good quality and correct
  functionality, but distributing them might pose problems.  The license
  on either the plug-ins or the supporting libraries might not be how we'd
  like. The code might be widely known to present patent problems.

  - Distributors should check if they want/can ship these plug-ins.
  - People writing elements should base their code on these elements.

- gst-plugins-bad: a set of plug-ins that aren't up to par compared to the
  rest.  They might be close to being good quality, but they're missing
  something - be it a good code review, some documentation, a set of tests,
  a real live maintainer, or some actual wide use.
  If the blanks are filled in they might be upgraded to become part of
  either gst-plugins-good or gst-plugins-ugly, depending on the other factors.

  - If the plug-ins break, you can't complain - instead, you can fix the
    problem and send us a patch, or bribe someone into fixing them for you.
  - New contributors can start here for things to work on.

INSTALLING FROM PACKAGES
------------------------
You should always prefer installing from packages first.  GStreamer is
well-maintained for a number of distributions, including Fedora, Debian,
Ubuntu, Mandrake, Gentoo, ...

Only in cases where you:
- want to hack on GStreamer
- want to verify that a bug has been fixed
- do not have a sane distribution
should you choose to build from source tarballs or CVS.

Find more information about the various packages at
http://gstreamer.freedesktop.org/download/

COMPILING FROM SOURCE TARBALLS
------------------------------
- again, make sure that you really need to install from source !
  If GStreamer is one of your first projects ever that you build from source,
  consider taking on an easier project.

- check output of ./configure --help to see if any options apply to you
- run
  ./configure
  make

  to build GStreamer.
- if you want to install it (not required), run
  make install
- You should create a registry for things to work.
  If you ran make install in the previous step, run
  gst-register
  as root.

  If you didn't install, run
  tools/gst-register
  as a normal user.

- try out a simple test:
  gst-launch fakesrc num_buffers=5 ! fakesink
  (If you didn't install GStreamer, again prefix gst-launch with tools/)

  If it outputs a bunch of messages from fakesrc and fakesink, everything is
  ok.

- After this, you're ready to install gst-plugins, which will provide the
  functionality you're probably looking for by now, so go on and read
  that README.

COMPILING FROM CVS
------------------
When building from CVS sources, you will need to run autogen.sh to generate 
the build system files.

You will need a set of additional tools typical for building from CVS,
including:
- autoconf
- automake
- libtool

autogen.sh will check for recent enough versions and complain if you don't have
them.  You can also specify specific versions of automake and autoconf with
--with-automake and --with-autoconf

Check autogen.sh options by running autogen.sh --help

autogen.sh can pass on arguments to configure - you just need to separate them
from autogen.sh with -- between the two.
prefix has been added to autogen.sh but will be passed on to configure because
some build scripts like that.

When you have done this once, you can use autoregen.sh to re-autogen with
the last passed options as a handy shortcut.  Use it.

After the autogen.sh stage, you can follow the directions listed in
"COMPILING FROM SOURCE"

You can also run your whole cvs stack uninstalled.  The script in
the gstreamer module /docs/faq/gst-uninstalled) is helpful in setting
up your environment for this.

PLUG-IN DEPENDENCIES AND LICENSES
---------------------------------
GStreamer is developed under the terms of the LGPL (see LICENSE file for
details). Some of our plug-ins however rely on libraries which are available
under other licenses. This means that if you are using an application which
has a non-GPL compatible license (for instance a closed-source application)
with GStreamer, you have to make sure not to use GPL-linked plug-ins.
When using GPL-linked plug-ins, GStreamer is for all practical reasons
under the GPL itself.

HISTORY
-------
The fundamental design comes from the video pipeline at Oregon Graduate
Institute, as well as some ideas from DirectMedia.  It's based on plug-ins that
will provide the various codec and other functionality.  The interface
hopefully is generic enough for various companies (ahem, Apple) to release
binary codecs for Linux, until such time as they get a clue and release the
source.