GitLab

clocked -> clock

Not from the external one.

Don't abbreviate to 'mono' and use 'monotonic' instead.

They will return useless values from get_time().

There's not much lost by having the clock idle around a bit longer but it will
potentially allow anybody wanting to use the same clock server again to sync
much faster.

If multiple net/NTP clocks are created for the same server, reuse the same
internal clock for all of them. This makes sure that we don't flood the server
with too many requests and also possibly allows faster synchronization if
there already was an earlier synchronized clock when creating a new one.

Bindings don't like that much and as we're using GIO here anyway we can as
well use GInitable for possibly failing initialization.

They can't sensibly be changed after construction.

Add two macros to build nicer element/pad name strings. The macros avoid
printing "(NULL)" and print the element type in addition to the name.

The parse-launch API automagically handles dynamic pads and performs delayed
linking as needed, without any feedback about whether the linking succeeded or
not however. If a delayed dynamic link can't be completed for whatever reason,
parse-launch will simply wait in case a suitable pad appears later. This may
never happen though, in which case the pipeline may just hang forever.

Try to improve this by connecting to the "no-more-pads" signal of any element
with dynamic pads and posting a warning message for the related outstanding
dynamic links when "no-more-pads" is emitted.

Fixes #760003

Tests data/strings as well, not just that we received
something non-NULL back.

Just allowing IPs here is not ideal and implementing DNS resolval is easy.

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

To make clear caller is responsible to unref them.

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

This gives us the property documentation for example.

Simply call fail() in the condition after the first memcmp.

Update the -Bsymbolic check with the version glib has. This version
works with clang.

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

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

If not, go back to the automatic pad numbering.

CID 1195129

For CAPS events we will never ever have a FALSE return value here, so just
remove the dead code instead of causing future confusion.

This reverts commit 78614c50.

The code it was fixing does not have any effect anyway and will be removed in
the next commit.

Once event is pushed to pad, then queue should not access the event.
This is leading to invalid read valgrind errors

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

Otherwise we'll take ownership of the event only if it's implemented, and
leak the event in all other situations.

Use GST_PAD_PROBE_PASS to pass through all events other than EOS instead of
blocking on the first non-EOS event forever. Also fix a typo in a comment in
that function.

Thanks to David Jaggard for reporting this on the mailing list.

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

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