GitLab

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

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

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

Also add GstDevice and GstDeviceMonitorFactory
And add code to the registry to save them

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

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

The return value from gst_pad_forward() is the aggregated return value from the callback and the callback returns FALSE to continue iterating.

Instead of ignoring the return value and always return TRUE pass the already agregated result back.

From the test case:

/* This test creates a multiqueue with 2 streams. One receives
 * a constant flow of buffers, the other only gets one buffer, and then
 * new-segment events, and returns not-linked. The multiqueue should not fill.
 */

If one of the queues goes EOS and the other returns NOT_LINKED the stream
can be considerered EOS as a NOT_LINKED means that one of the branches has no
sink downstream that will block the EOS message posting.

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

This is done by introducing a new gst_adapter_copy_bytes() call that
returns a GBytes structure.

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

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

Has added benefit that compiler might warn if more values
are added to the enum.

Add a helper like gst_flow_get_name() for GstPadLinkReturn. Use this in core.
API: gst_pad_link_get_name()

Use the pad as object for logging to get more context. Use
gst_pad_store_sticky_event() instead of sending the event. This avoids a warning
as here the pad is not yet linked and we actually don't want to send anyway.

Avoids stall waiting for buffering to reach 100%

buffering_iteration was never used

Avoids mistakenly returning _OK when downstream is still
_NOT_LINKED on subsequent received pad pushes

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

Avoids stall waiting for buffering to reach 100%

Use the last result as a default when pushing a item from a single queue,
otherwise the status gets reset to _OK when pushing events.

This causes problems when mistakenly activating a not-linked stream
that is being ignored upstream as it is not being used (adaptive
scenarios), it will make the multiqueue post a buffering message
on a pad that won't receive buffers

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

It's nicer to only have it set when something noteworthy
happened and otherwise unset.

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

Also fix comment typos and add more detail in the logs.

The IN_CAPS flag does not exist any more.

This ensures that the lock of the internal pad is held while referencing
it's peer (= the target pad), which ensures that the peer is not
going to be unlinked/destroyed in the meantime.

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

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

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

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

This was plain text that had all list items one after the other (including a
repeated number). Now it will atleast look good when processed with gtk-doc
1.20.

From fe1672e to bcb1518

- Fix failing build
- Drop added trailing whitespace

FIxes previous commit.

The gtk-doc markup is less intrusive and better handled when creating docs for
language bindings. The titles (where used) where not adding much.

Check if the memory is writable before releasing the buffer into the
pool again.
Add unit test for this scenario.

Check if memory is writable in a buffer and thus is exclusively owned by
this buffer.

Tag allocated buffers with TAG_MEMORY. When they are released later,
only add them back to the pool if the tag is still there and the memory
has not been changed, otherwise throw the buffer away.
Add unit test to check various scenarios.

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

Add a flag to check if the memory changed in a buffer.

Refcount and writability are not related for memory objects.