Thibault Saunier authored Sep 19, 2013 and Olivier Crête committed Oct 04, 2013

So you can specify the PATHS where to look for scenario files

Vincent Penquerc'h authored Oct 03, 2013 and Olivier Crête committed Oct 04, 2013

Seeks will be done with no particular flags, unless specified
in the scenario.

Some gcc versions don't like the typedef being done twice

When elements do not have the same number of input and output pads
(such as miuxers), throw the towel before trying.

Change-Id: I965b9401ea157cfaf736ace97ab33ac9a5d0e9ad

baseparse may collapse segments into a single one.

Change-Id: I1deb14bf5a744fcd12a8b608ee95c553c9573afe

Change-Id: I012879fc2bdec8baaf14a3854a0237e30ebc88a3

If an element buffers segments, the pad monitor may compare
an outgoing segment with the wrong one if two segments are
received in quick succession, before being output. This can
happen when seeking, where an update segment is received,
followed by a new non update segment.

As it is not a mandatory field otherwize

https://bugzilla.gnome.org/show_bug.cgi?id=708499

Conflicts:
	validate/gst/validate/gst-validate-pad-monitor.c

And give a descrpition for actions

The "switch-track" command can be used to switch tracks. The "type"
argument selects which track type to change (can be "audio", "video",
or "text"). The "index" argument selects which track of this type
to use: it can be either a number, which will be the Nth track of
the given type, or a number with a "+" or "-" prefix, which means
a relative change (eg, "+1" means "next track", "-1" means "previous
track").

Conflicts:
	validate/gst/validate/gst-validate-scenario.c

And add support to user declared timestamps -1.0 as GST_CLOCK_TIME_NONE

Make the scenario files a list of GstStructure-s as strings

When used with LD_PRELOAD,  the application might use various pipelines
for several different thing, we need to make it possible to spcify a
specific pipeline (or set of pipelines) on which to run the scenario.

The format is in the form of:
            scenario_name:pipelinename_pattern*

Conflicts:
	tools/gst-validate.c

For instance, "fakesrc" will return a fakesrc, not a pipeline.

This is similar to what gst-launch does, and avoids calling
pipeline API on a non pipeline object (and thus asserting).

Instead, error out properly with the actual error, if available.

Also ensure that if just -l is passed, we don't try creating a
non existent pipeline.

This makes gst-validate -l work properly again.

Pass the correct variable to macro

It should always be acceptable to return GST_FLOW_FLUSHING when the
pad is flushing

Conflicts:
	gst/validate/gst-validate-pad-monitor.c

Elements are allowed to accumulate segments, they don't have to push
1:1 segments as they receive

Improve buffer timestamp range check:

* Only do it for encoders or decoders
* Audio has an acceptable tolerance of 100ms

To do this, keep track of the caps on the pad and store
if it is dealing with audio or video

Allows both src and sink pad to keep track of the current caps, but
the duplicated caps check is still only applied to sink pads as
src pads can push the same caps multiple times when it isn't linked

Conflicts:
	gst/validate/gst-validate-pad-monitor.c

Thanks to Thibault Saunier for most of the explanatory texts

Conflicts:
	gst/validate/gst-validate-pad-monitor.c

Use pad as the debug object to make logs more meaningful.

Also adds a FIXME note

Conflicts:
	gst/validate/gst-validate-pad-monitor.c

Conflicts:
	gst/validate/gst-validate-element-monitor.c

Clear as much as a flush-stop when pad is deactivated

Conflicts:
	gst/validate/gst-validate-pad-monitor.c
	gst/validate/gst-validate-pad-monitor.h

When seeking out of the media file length, the element should push an
EOS with the same seqnum of the seek event

Makes the result a bit more readable than a compact multi-line list.

FIXME: Figure out how to print the description of the issues (which can
spawn multiple lines) in a nice way.

Tag events are hard to track and check if properly serialized because
they mutate too much inside elements. There is no reliable way currently
to match a tag event pushed into an element and another tag event
leaving the element (other than if the pointers are actually the same).

Conflicts:
	gst/validate/gst-validate-pad-monitor.c