GitLab

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

This is needed by the unit tests in gst-plugins-base, -good etc.

Spotted by Alex Kaye.

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

This is equal to any other caps features but results in unfixed caps. It
would be used by elements that only look at the buffer metadata or are
currently working in passthrough mode, and as such don't care about any
specific features.

Let's not use ugly leading underscores for
static functions.

Extract formatters into local functions. Change the structure filtering so that
it works for taglists too.

These are meant to specify features in caps that are required
for a specific structure, for example a specific memory type
or meta.

Semantically they could be though of as an extension of the media
type name of the structures and are handled exactly like that.

So demuxers can signal which audio/video/subtitle streams should
be selected by default and which should not be selected
automatically.

API: GST_STREAM_FLAG_SELECT
API: GST_STREAM_FLAG_UNSELECT

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

API: gst_event_set_stream_flags()
API: gst_event_parse_stream_flags()
API: GST_STREAM_FLAG_NONE
API: GST_STREAM_FLAG_SPARSE

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

Elements should override GstElement::set_context() and also call
gst_element_set_context() to keep this context up-to-date with
the very latest context they internally use.

This will reduce the number of caps created downstream and we don't
need to intersect in the very end with the pad's own caps.

gstbasesink.c: In function 'gst_base_sink_chain_unlocked':
gstbasesink.c:3204: warning: 'ret' may be used uninitialized in this function

This reverts commit 5d64f27d.

*sigh*

When flushing, it is expected that upstream will send a SEGMENT
event afterwards.
This also avoids stray SEGMENT events from coming through after a
flush.

This was misassigning the control sources. It was also leaking the old values if
a control source would be replaced.

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

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

API: gst_buffer_extract_dup

To indicate that format strings should be alpha sortable.

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

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

Negotiation may be aborted by a flush from another thread that need to
stop the task (i.e. seek). Check that case and silently pause the task.

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

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

pop() in collected callback.

There were three threads in the test cases that hanged: the test thread and two
threads that push buffers. Each thread push one buffer on one pad. There are
two pads in the collectpads so the second buffer will trigger the
collect-callback.

This is what happens when the hang occurs:

The first thread pushes a buffer and initializes a cookie to the value of a
counter in the collectpads object and waits on a cond for the counter to change
and for someone to consume the buffer (i.e. _pop() it).

The second thread pushes a buffer and calls the collected callback, which
signals the cond that the test thread is waiting for.

The test thread pops both buffers (without holding any lock). Each call to
_pop() increases the counter broadcasts the condition that the first thread is
now waiting for. It then joins both threads (hangs).

The first thread wakes up and returns, since its buffer has been consumed.

The second thread starts executing again. When the callback, called by the
second thread, has returned it initializes a cookie to the value of a counter,
which has already prematurely been increased by the test thread when it popped
the buffers, and wait's on a cond for the counter to change and for someone to
consume the buffer (i.e. _pop() it). Since the buffer has already been poped
and the counter has already been increased it will be stuck forever.

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

We link those libs into the plugin statically, or use external
system libs, but never the internal snapshot dynamically.