GitLab

Don't add empty labl/note chunks. Always pass instance as the first param. Add more logging.

This allows to use the GstChildProxy interface to adjust
properties on it.

When the server suggests a GstNetTimeProvider in the SDP, set up a
GstNetClientClock that slaves to the remote clock and suggest this clock in
provide_clock.

Avoid doing alloc and free in the render function for each buffer. Instead,
allocate the needed arrays in _init and use those.

The variables already point to the start of the list.

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

Add 'note' chunk support in TOC as GST_TAG_COMMENT

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

From 04c7a1e to aed87ae

Use fakesrc instead of filesrc with /dev/null.

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

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

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

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

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

Drop pending data on discont and start a new cycle with a new base timestamp.
Cleanup some variables.

Decode failures and missing keyframes should get different debug
output.

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

This way, it will be selected by decodebin
Bug reported by andreas.fenkart@streamunlimited.com

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

Previously we would skip level message when processing buffers > the requested
interval. Also the message frequency would contain quite some jitter due to only
considering them at the end of buffers.

Cleanup the tests while we're at it.

Don't pretend that we have a timestamp on a buffer when we never set one.

Don't just loop over the first num_queued buffers but loop over
all the buffers and check if they need to be freed. It is possible that
not all buffers are queued and then the entry in our array will be NULL.
Those buffers that are not queued were freed in stop().

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

Otherwise we get a race where if the RTCP packet comes in first and while
it is added the pads, the segment event arrives on the RTP stream, the event
may be lost completely and never forwarded.

They are forwarded with the other events

Use the gst_pad_forward() mechanic, this way we won't miss pads that are
added while we are pushing

We had the wrong condition to check for the internal links, so RTP and RTCP
pads got crossed!

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