GitLab

It returns a ref to the pool.

Queries will be sent when pipeline goes down to NULL, which would
result in the probe being called ... but can't take the lock.

Use the peer of the internal pad to forward them, instead of the
target which only exists for the ghostpad (and not the internal
proxy pad).

Instead of letting the default query handler fail.

Fixes "Unexpected event of kind caps can't be added in temp file"
warning when doing download buffering.

Make _foreach_meta return FALSE when the foreach function returned FALSE.

Make the foreach function return FALSE when one of the function calls returned
FALSE.

When we escape spaces to keep arguments together, only escape when the space is
outside a "" string.

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

This reverts commit dd9fedb4.

This is not the right place to escape the \, we should only escape the spaces to
keep the arguments together that were provided as one group (with quotes on the
shell).

Stop querying the duration once an element return unknown and return unknown
as a final result. This avoid eventually cutting off a stream too early.
Add a tests to docuement the behavior.

We want to be able to use this function on random non-NULL input,
this should not result in a runtime-critical.

Move code that checks for upstream seekability and all that to
the right place, otherwise it will never be done for formats
that have headers such as FLAC, as handle_and_push frame will
be called the first time only after headers have been processed
(and framecount is > 0). This then makes us report that we
can't seek, which disables the seek bar in totem.

Keep it private until we have a reason to make it public.

First try to let upstream handle the seek event, then fail if the event is
something we don't understand.

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

The ghostpad code directly activates/deactivates the child code by
calling gst_pad_activate_mode, rather than gst_pad_set_active, so
make sure to clear the flags in gst_pad_activate_mode(), which should
catch all cases.

when we have a new step event with a -1 amount, make sure that we follow the
regular code path so that the stop_end handler is called as usual. This takes
care of flushing the buffer in case of a flushing step and also posts a step end
message.

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

Recursive search for the required entry, instead of returning the
top-level entry that contains an entry with the search UID.