| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
consistence with the design doc
|
|
Via gst_event_set_running_time_offset()
|
|
|
|
passed running time
These durations can become negative in case of inaccuracies, and we need
to correct backwards in that case.
|
|
|
|
This can happen if upstream handles seeks with seek_type=NONE
incorrectly and actually changes the position into the past.
|
|
between start and stop
|
|
current segment
|
|
|
|
|
|
INSTANT_RATE_SYNC_TIME event
|
|
instant-rate-change event
|
|
message
|
|
GST_SEEK_FLAGS_INSTANT_RATE_CHANGE
A seek with that flag set must be non-flushing, not change the playback
direction and start/stop position. A seek handler will then send the new
GST_EVENT_INSTANT_RATE_CHANGE event downstream for downstream elements
to immediately apply the new playback rate before the new in-band segment
event arrives.
|
|
|
|
|
|
|
|
Probes were remembering a cookie that was used to check if the probe was
already called this time before the probes list changed. However the
same probes could've been called by another thread in between and thus
gotten a new cookie, and would then be called a second time.
https://bugzilla.gnome.org/show_bug.cgi?id=795987
|
|
strncpy() is assumed to be for strings so the compiler assumes that
it will need an extra byte for the string-terminaning NULL.
For cases where we know it's actually "binary" data, just copy it
with memcpy.
Fixes compiler warnings with gcc 8.
https://bugzilla.gnome.org/show_bug.cgi?id=795756
|
|
gst_buffer_list_new_sized(0) will cause an underflow in a calculation
which then makes it try to allocate huge amounts of memory, which
may lead to aborts.
https://bugzilla.gnome.org/show_bug.cgi?id=795758
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=795332
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=795332
|
|
cc.compiles() doesn't have a 'prefix' argument (yet) and the
prefix has already been prepended to the source code snippets.
https://github.com/mesonbuild/meson/issues/2364
|
|
|
|
Mostly related to out parameters and their transfer
|
|
|
|
When outputting debug logs on Windows, some sections are protected
with a non-recursive lock. Turns out though that gst_debug_message_get()
might indirectly, via our printf format extensions, call code which
in turn would try to log something when it can't handle something. If
that happens we end up in gst_debug_log_default() again recursively and
try to again take the lock that's already taken, thus deadlocking.
Format the debug message string outside of the critical section
instead to avoid this.
https://bugzilla.gnome.org/show_bug.cgi?id=784382
|
|
|
|
Remove unneeded reapplication of patterns. Besides being
superfluous (gst_debug_reset_threshold already applies
patterns) it was also wrong and didn't stop checking patterns
after the first match (broken in 67e9d139).
Also fix up unit test which checked for the wrong order.
https://bugzilla.gnome.org/show_bug.cgi?id=794717
|
|
Adding the bin to the child element doesn't really make sense.
|
|
g_object_ref() forwards the type of its argument nowadays.
./grammar.y:409:14: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
gstchildproxy.c:212:7: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
|
|
|
|
|
|
update g-i annotation value
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We need different export decorators for the different libs.
For now no actual change though, just rename before the release,
and add prelude headers to define the new decorator to GST_EXPORT.
|
|
We need different export decorators for the different libs.
For now no actual change though, just rename before the release,
and add prelude headers to define the new decorator to GST_EXPORT.
|
|
We need different export decorators for the different libs.
For now no actual change though, just rename before the release,
and add prelude headers to define the new decorator to GST_EXPORT.
|
|
We need different export decorators for the different libs.
For now no actual change though, just rename before the release,
and add prelude headers to define the new decorator to GST_EXPORT.
|
|
We need different export decorators for the different libs.
For now no actual change though, just rename before the release,
and add prelude headers to define the new decorator to GST_EXPORT.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=794153
|
|
Otherwise it's possible that we won't be able to start again
depending the implementation. We do start/stop in normal use cases
whenever GST_QUERY_SCHEDULING happens before we are started.
https://bugzilla.gnome.org/show_bug.cgi?id=794149
|
|
The flushing state is handled a bit differently, there is no need
to stop flushing in start_complete. This would other result in
unlock_stop being called without unlock_start.
Unlike what the old comment says, there is no need to take the live
lock here, we are still single threaded at this point (app thread
or the state change thread). Also, we will wait for playing state
in create/getrange, no need to do that twice.
https://bugzilla.gnome.org/show_bug.cgi?id=794149
|
|
This way gobject-introspection also picks it up and handles our
annotations.
See https://gitlab.gnome.org/GNOME/gobject-introspection/issues/194
|
|
All other variants of {peek,pop}_{head,tail}_{,struct} were already
implemented.
https://bugzilla.gnome.org/show_bug.cgi?id=794035
|
