mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-08 18:39:54 +00:00
GStreamer multimedia framework
9e67f9a283
Original commit message from CVS: 2004-01-25 Ronald Bultje <rbultje@ronald.bitfreak.net> * gst-libs/gst/riff/riff-read.c: (gst_riff_read_info): Additional pad usability check. * gst/mpeg1videoparse/gstmp1videoparse.c: (gst_mp1videoparse_init), (mp1videoparse_find_next_gop), (gst_mp1videoparse_time_code), (gst_mp1videoparse_real_chain): Fix MPEG video stream parsing. The original plugin had several issues, including not timestamping streams where the source was not timestamped (this happens with PTS values in mpeg system streams, but MPEG video is also a valid stream on its own so that needs timestamps too). We use the display time code for that for now. Also, if one incoming buffer contains multiple valid frames, we push them all on correctly now, including proper EOS handling. Lastly, several potential segfaults were fixed, and we properly sync on new sequence/gop headers to include them in next, not previous frames (since they're header for the next frame, not the previous). Also see #119206. * gst/mpegaudioparse/gstmpegaudioparse.c: (gst_mp3parse_chain), (bpf_from_header): Move caps setting so we only do it after finding several valid MPEG-1 fraes sequentially, not right after the first one (which might be coincidental). * gst/typefind/gsttypefindfunctions.c: (mpeg1_sys_type_find), (mpeg_video_type_find), (mpeg_video_stream_type_find), (plugin_init): Add unsynced MPEG video stream typefinding, and change some probability values so we detect streams rightly. The idea is as follows: I can have an unsynced system stream which contains video. In the current code, I would randomly get a type for either system or video stream type found, because the probabilities are being calculated rather randomly. I now use fixed values, so we always prefer system stream if that was found (and that is how it should be). If no system stream was found, we can still identity the stream as video-only. |
||
|---|---|---|
| common@0bcde34201 | ||
| examples | ||
| ext | ||
| gconf | ||
| gst | ||
| m4 | ||
| po | ||
| sys | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .gitmodules | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| gst-plugins.spec.in | ||
| INSTALL | ||
| LICENSE_readme | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| REQUIREMENTS | ||
| TODO | ||
WHAT IT IS
----------
This is gst-plugins, a set of plug-ins for GStreamer.
COMPILING FROM SOURCE
---------------------
- make sure you compiled and at least did a test-run of GStreamer (core)
- check output of ./configure --help to see if any options apply to you
- configure the source tree:
- if you installed GStreamer, then do:
./configure
If configure complains about missing GStreamer, you should try
./configure --with-pkg-config-path=prefix/lib/pkgconfig
where prefix should be replaced by the prefix you used to configure
GStreamer. (Be mindful NOT to ADD a trailing / to that option !)
If this doesn't fix it, you have other issues ;)
- if you didn't install GStreamer, you can still compile the plug-ins.
Add the path to gstreamer-uninstalled.pc (which lives in the gstreamer
source tree) to PKG_CONFIG_PATH
or run configure --with-pkg-config-path=(path to gstreamer uninstalled)
- the output of configure will give you a list of plug-ins with external
dependencies (ie, depending on other libs, see below). By no means
should you try to get them all built on your first run. This is hard
enough as it is ;) Resist the urge to get the most features for now.
It doesn't list all of the non-depending plug-ins, which get built
regardless (unless you explicitly asked it not to).
- build the tree:
make
If any plug-in causes a problem at this stage, you should re-configure
with --disable-(dependency)
and doublecheck if configure reports this plug-in as being disabled.
Then re-run make.
- install:
- if you installed GStreamer, and want to install the plug-ins as well, run
make install
and, as root, run
gst-register
- if you installed GStreamer, but don't want to install the plug-ins, run
gst-register --gst-plugin-path=.
- if you didn't install GStreamer, then do
path/to/gstreamer/tools/gst-register --gst-plugin-path=.
(Replace path/to/gstreamer obviously)
- test:
- run
gst-launch sinesrc ! fakesink
and prefix gst-launch with the path to gstreamer/tools if you didn't install
GStreamer.
If this doesn't give any errors, you can abort it.
- try replacing fakesink with your choice of
osssink/esdsink/artsdsink/alsasink/jacksink (depending on what output
method you have available) and see if you hear a C tone.
- After this, you should look into installing an application, like
gst-player, gst-editor or monkey-media with rhythmbox.
COMPILING FROM CVS
------------------
When building from CVS sources, you will need to run autogen.sh to generate
the build system files.
GStreamer is cutting-edge stuff. To be a CVS developer, you need
what used to be considered cutting-edge tools.
ATM, most of us have at least these versions :
* autoconf 2.52 (NOT 2.52d)
* automake 1.5
* libtool 1.4 (NOT Gentoo's genetic failure 1.4.2)
* pkg-config 0.8.0
autogen.sh will check for these 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.
You will probably have to pass at least --with-pkg-config-path to autogen.sh
to point to the CVS version of GStreamer.
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"
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.
The plug-ins which use a GPL library are as follows:
cdparanoia libcdparanoia (http://www.xiph.org/paranoia/)
aasink aalib (http://aa-project.sourceforge.net/aalib/)
xmms libxmms (http://www.xmms.org)
decdvd ac3dec,mpeg2dec (http://linuxvideo.org/mpeg2dec/,http://linuxvideo.org/ac3dec/)a
mad mad (http://www.mars.org/home/rob/proj/mpeg/)
Plug-ins which use an LGPL library are as follows:
colorspace Hermes (http://www.clanlib.org/hermes/)
httpsrc libghttp (ftp.gnome.org/pub/GNOME/stable/sources/libghttp/)
alsasink alsa (http://alsa-project.org)
arts aRts (http://arts-project.org)
sdlsink libsdl (http://www.libsdl.org)
gnomevfssource gnome-vfs (ftp.gnome.org//pub/GNOME/stable/sources/gnome-vfs)
gnomevfssink gnome-vfs
esdsink libesd (ftp.gnome.org/pub/GNOME/stable/sources/esound)
icastsend libshout (http://www.icecast.org)
lame libmp3lame (http://www.mp3dev.org/mp3/)
gst1394 libraw1394 (http://linux1394.sourceforge.net)
flac libFLAC (http://flac.sourceforge.net)
RTP ortp (http://www.linphone.org/ortp/)
Plug-ins which use a BSD covered library are as follows:
vorbisenc libogg/libvorbis (http://www.xiph.org/ogg/vorbis)
vorbisdec libogg/libvorbis
Plug-ins based on libraries with other free licenses:
xvideosink libXv (MIT X11 / X Consortium license)
gsm libgsm (MIT license http://kbs.cs.tu-berlin.de/~jutta/toast.html)
Plug-ins using non-free libraries:
wincodec win32ddl (http://divx.euro.ru/)