gstreamer/validate
Thibault Saunier 5b82274f17 validate:flow: Add a way to set the types of events to log/ignore
Added two properties to the plugin:
     * ignored-event-types: A list of event types to be ignored when logging events
     * logged-event-types: A list of event types to be logged when logging events

This commits also moves the "ignored-event-fields" property to using a proper
GstValueList for the list of event fields to be taken into account, instead
of the home grown separated by comas list of string, making the API more
uniform.

This also adds a simple helper method: `gst_validate_utils_get_strv`
2020-02-04 16:09:36 -03:00
..
data validate: remove autotools build 2019-10-15 00:24:00 +01:00
docs validate: remove autotools build 2019-10-15 00:24:00 +01:00
gst validate:flow: Add a way to set the types of events to log/ignore 2020-02-04 16:09:36 -03:00
gst-libs validate: remove autotools build 2019-10-15 00:24:00 +01:00
launcher gst-validate-launcher: separate known error from passed tests 2020-01-24 14:52:49 +00:00
pkgconfig validate: remove autotools build 2019-10-15 00:24:00 +01:00
plugins validate:flow: Add a way to set the types of events to log/ignore 2020-02-04 16:09:36 -03:00
tests validate: Fix memory leaks 2019-11-20 10:19:00 +01:00
tools validate: remove autotools build 2019-10-15 00:24:00 +01:00
win32/common validate:flow: Add a way to set the types of events to log/ignore 2020-02-04 16:09:36 -03:00
.gitignore validate: remove autotools build 2019-10-15 00:24:00 +01:00
AUTHORS
ChangeLog Release 1.16.0 2019-04-19 00:36:54 +01:00
COPYING
gst-validate.doap Release 1.16.0 2019-04-19 00:36:54 +01:00
meson.build doc: Port to hotdoc 2019-05-13 11:37:38 -04:00
NEWS Release 1.16.0 2019-04-19 00:36:54 +01:00
README validate: remove autotools build 2019-10-15 00:24:00 +01:00
RELEASE Back to development 2019-04-19 10:42:30 +01: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

Build with:

meson build --prefix=<installation-prefix>
ninja -C build
sudo ninja -C build 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