gstreamer/validate
2015-08-15 19:07:02 +02:00
..
common@92e7a485ce Update common submodule 2015-04-23 11:24:14 +02:00
data validate: scenarios: Change start time for reverse playback 2015-08-04 15:24:14 +02:00
docs validate: Add a method to get action->scenario in a thread safe way 2015-07-25 10:54:19 +02:00
gst validate: scenario: fix leak during error cases 2015-08-07 10:18:56 +02:00
gst-libs validate:ssim: Fix calls to the converters 2015-07-16 16:30:52 +02:00
launcher validate/launcher: De-blacklist some HLS tests 2015-08-15 19:07:02 +02:00
pkgconfig validate: fix installation 2013-11-25 16:56:11 -03:00
plugins validate:gtk: Handle the case were we are 'pressing' only a modifier 2015-07-14 20:31:59 +02:00
po validate: Update autogen.sh 2015-04-23 11:52:41 +02:00
tests pad-monitor: Check that an ERROR GstMessage has been posted on GST_FLOW_ERROR 2015-06-03 11:43:12 -04:00
tools validate: tools: transcoding error due to wrong condition check 2015-08-05 17:19:24 -04:00
.gitignore gitignore: Add more generated files 2015-07-24 17:06:29 -04:00
AUTHORS qa: adds gst-qa binary and basic classes to run the QA tests 2013-07-09 16:08:30 -03:00
autogen.sh validate: Always git submodule update from the toplevel directory 2015-05-12 09:55:58 +02:00
ChangeLog Release 1.5.2 2015-06-24 17:42:16 +02:00
configure.ac Back to development 2015-06-24 17:43:53 +02:00
COPYING qa: adds gst-qa binary and basic classes to run the QA tests 2013-07-09 16:08:30 -03:00
gst-validate.doap Release 1.5.2 2015-06-24 17:42:16 +02:00
Makefile.am validate: Fix make distcheck 2015-06-08 18:20:33 +02:00
multi-pre-commit.hook validate: update pre-commit hook. 2014-10-30 15:40:17 +01:00
NEWS Release 1.5.2 2015-06-24 17:42:16 +02:00
pre-commit-python.hook validate: pre commit hook: Do not try to run pep8 on non python files! 2014-11-25 19:41:01 +01:00
README docs: update and improve 2013-09-02 16:09:07 -03:00

== Gst-Validate

The goal of GstValidate is to be able to detect when elements are not
behaving as expected and report it to the user so he knows how things
are supposed to work inside a GstPipeline. In the end, fixing issues
found by the tool will ensure that all elements behave all together in
the expected way.

The easiest way of using GstValidate is to use one of its command-line
tools, located at tools/ directory. It is also possible to monitor
GstPipelines from any application by using the LD_PRELOAD gstvalidate
lib. The third way of using it is to write your own application that
links and uses libgstvalidate.

== BUILDING

Getting the code:

Releases are available at <URL>, download and extract the tarball. If you
want to use latest git version, do:

git clone <URI>

After cloning or extracting from a tarball, enter the gst-validate directory:

cd gst-validate

The 'master' branch uses gstreamer 1.0, there is a '0.10' branch for
gstreamer 0.10. The default is the 'master' branch, if you want to use it
for 0.10, do:

git checkout --track origin/0.10

Build with:

./autogen.sh --prefix=<installation-prefix>
make
sudo make install (only if you want to install it)

Replace <installation-prefix> with your desired installation path, you can omit
the --prefix argument if you aren't going to install it or if you want the
default /usr/local. It is possible to use gst-validate CLI tools without
installation.

== INSTRUCTIONS

If you are looking for informations on how to use gst-validate -> docs/validate-usage.txt
If you are looking for informations on gst-validate design -> docs/validate-design.txt