GitLab

If a device provider fails to start (for instance the pulseaudio provider unable
to connect to the PulseAudio daemon) then the monitor should not keep track of
it in its `started` providers list. Otherwise a false positive critical warning
would be raised.

This patch also switches the started_count type from bool to int, for
consistency. This is a counter, after all.

API: gst_device_provider_is_started
Part-of: <gstreamer/gstreamer!679>

non-*Ex methods are not allowed for UWP

Part-of: <gstreamer/gstreamer!610>

fstat() fails on Windows in various situations if the file metadata has
invalid values, and we only care about getting attributes and the file
size.

Part-of: <gstreamer/gstreamer!610>

Part-of: <gstreamer/gstreamer!610>

Part-of: <gstreamer/gstreamer!676>

While we can fixe the upstream latency using the min-upstream-latency, we
are now forced to use queues (hence more thread) in order to store the pending
data whenever we have an upstream source that has lower latency.

This fixes the issue by allowing to buffer the fixed upstream latency. This is
particularly handy on single core systems were having too many threads can
cause serious performance issues.

Part-of: <gstreamer/gstreamer!677>

This is inspired by the stats on rtpjitterbuffer, it's useful
to be able to get some simple stats out of the pipeline without having
to write yet another pad probe.

Part-of: <gstreamer/gstreamer!615>

In order to support the symbol g_enum_to_string in various
project using GStreamer ( gst-validate etc.), the glib minimum
version should be 2.56.0.

Remove compat code as glib requirement
is now > 2.56

Version used by Ubuntu 18.04 LTS

Part-of: <gstreamer/gstreamer!199>

Our various deserializing functions require NULL terminators
to not over consume substrings (eg fields of an array). Instead
of writing a NULL terminator to the passed-in string, which may
result in segfaults, make a copy of the substring we're interested
in.

Fixes gstreamer/gstreamer#446

Part-of: <gstreamer/gstreamer!672>

Part-of: <!4>

Most symbols in DbgHelp.h are not allowed for UWP

Part-of: <gstreamer/gstreamer!665>

Having this just to log a debug message in case we're
running inside valgrind doesn't seem very useful, and
the code that used to use this no longer exists it seems.

Part-of: <!595>

gstinfo.c(3086): error C2094: label 'done' was undefined

Part-of: <gstreamer/gstreamer!662>

e.g. on 32-bit arm, we may have armv6, armv7l, armv7hf, etc which all
generally have the same layouts.  cpu_family() groups all of these into
just 'arm' that the ABI check table is expecting.

Part-of: <gstreamer/gstreamer!664>

The default implementation doesn't actually use its buffer parameters,
but this error might have been the cause of some actual confusion in
the plugins code.

Part-of: <gstreamer/gstreamer!663>

When doing a static build, gstreamer-full-1.0 defines that symbol to
register static plugins. Cerbero's Android build will be updated to
implement that symbol too.

Part-of: <gstreamer/gstreamer!641>

Typing hints can only be passed to gst_value_deserialize()
through the type of the passed-in value. This means deserialization
can only target the desired type for the top-level elements,
making it for example impossible to deserialize an array of
flags to the expected type.

This commit exposes a new function, gst_value_deserialize_full(),
that takes an optional pspec as the extra parameter, and updates
the deserialization code to pass around that pspec, or the
element_spec when recursively parsing the elements of a list-type
value.

This allows for example passing arrays of flags through the
command line or gst_util_set_object_arg, eg:

foo="<bar,bar+baz>"

Part-of: <gstreamer/gstreamer!629>

... and update meson file so that enable it only using required headers.

"dependency(...)" is unlikely successful for Windows SDK libraries
since it doesn't ship pkg-config file. So it needs to be changed
to "find_library()" to link corresponding .lib file. That would
result to most MSVC build system will link dbghelp.dll. However,
one drawback of the change is that gstreamer-1.0.dll will mandate
dbghelp.dll although it should be optional. So g_module_open() way
can be the most safe way in this case.

Part-of: <gstreamer/gstreamer!626>

The template itself is already marked as such and the caps, the
documentation caps are a logical extension of those two.

Part-of: <gstreamer/gstreamer!650>

Adds missing "transfer full" annotation for caps parameter in
gst_pad_template_set_documentation_caps()

Part-of: <gstreamer/gstreamer!648>

Commit e9c99c05 added a deprecation message, but this message is not
displayed in the html page since the format was not correct.

Part-of: <gstreamer/gstreamer!648>

Custom meta is backed by a GstStructure, and does not require
that users of the API expose their GstMeta implementation as
public API for other components to make use of it.

In addition, it provides a simpler interface by ignoring the
impl vs. api distinction that the regular API exposes.

This new API is meant to be the meta counterpart to custom events
and messages, and to be more convenient than the lower-level API
when the absolute best performance isn't a requirement.

Part-of: <gstreamer/gstreamer!609>

This flag always causes problems as it prevents subbuffering,
instead one should create a custom GstAllocator to pool the GstMemory objects
and not rely on the lifetime of the GstBuffer object they were originally
attached to.

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

Part-of: <gstreamer/gstreamer!614>

Subsequent lookups in the hashtable are probably better done
on memory we're confident is allocated to us :)

It was easy to trigger invalid reads by calling gst_meta_register
with dynamically allocated memory, freeing that memory, then
calling gst_meta_get_info()

Part-of: <gstreamer/gstreamer!628>

This should make the API usage more consistent. Also document that the subclasses
should just return the devices as floating.

Part-of: <gstreamer/gstreamer!558>

If one pad returns not-negotiated from a caps event, then all other sink
pads were returning not-negotiated.

In our case, we can't reliably easily fail at all so just remove that
code.

Part-of: <gstreamer/gstreamer!623>

e.g. h264parse ! video/x-h264,stream-format=avc receives the following:
- caps: video/x-raw,stream-format=byte-stream
- gap event: baseparse tries to choose some default caps but would
  override the downstream chosen caps field with upstreams value.

Part-of: <gstreamer/gstreamer!581>

Otherwise the clock id we access might not be a valid pointer anymore.

Part-of: <gstreamer/gstreamer!630>

In case that no available stack tracer, leak tracer will set
null string value for `trace` field. I would likely happen
on Windows.

Part-of: <gstreamer/gstreamer!625>

g_thread_yield() doesn't ensure thread switching actually.
It would result to adding so many pads. Depending on system,
timeout might happen then.

Part-of: <gstreamer/gstreamer!625>

Expected segment-done message might not be seen within expected
time if system is not powerful enough.

Part-of: <gstreamer/gstreamer!625>

gstvalve.c(285) : warning C4715: 'gst_valve_event_needs_dropping':
not all control paths return a value

Part-of: <gstreamer/gstreamer!624>

This allows to signal the reason for the gap, for example missing data
like packet loss.

Based on a patch by Mikhail Fludkov <misha@pexip.com>

Part-of: <gstreamer/gstreamer!551>

By default each harness returns is_live=TRUE in latency queries. This is
often not desired and can now be overridden.

Part-of: <gstreamer/gstreamer!599>

Some base classes like videoaggregator try retrieving the latency during
construction, which causes the latency values to be set already until
reconfiguration happens.

By resetting them the same way as in stop() we ensure that we always
start cleanly.

Part-of: <gstreamer/gstreamer!599>

Part-of: <!620>

Part-of: <gstreamer/gstreamer!621>

When going to PLAYING we will now have a clock and can stop waiting on
the condition variable and instead start waiting on the clock if
necessary for the current configuration.

In the other direction when going to PAUSED the clock might have
disappeared and we might need to wait on the condition variable again
instead.

Part-of: <gstreamer/gstreamer!601>

Otherwise deactivating them will cause a deadlock as they're blocking
inside the streaming thread.

Fixes gstreamer/gstreamer#601

Part-of: <gstreamer/gstreamer!606>

Fixes gstreamer/gstreamer#587
Fixes gstreamer/gstreamer#84

Part-of: <gstreamer/gstreamer!594>