Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
Most functions are automatically chosen from the _FILE_OFFSET_BITS
define, the remaining one (fstat) is only available on API >= 21 so
check for that
|
|
Fixes make check
|
|
The queue gets filled by the tail, so a query will always be the tail
object, not the head object. Also add a _peek_tail_struct() method to the
GstQueueArray to enable looking at the tail.
With unit test to prevent future regression.
https://bugzilla.gnome.org/show_bug.cgi?id=762875
|
|
|
|
Modeled on the autotools build, -W flags are only
added if the compiler supports them.
https://bugzilla.gnome.org/show_bug.cgi?id=793958
|
|
Document this, and take advantage of that fact to use
GstAggregator.srcpad.segment instead of GstAggregator.segment
https://bugzilla.gnome.org/show_bug.cgi?id=793942
|
|
This reverts commit 9774b3775d8483e5697f9196a26c1e5831113bd6.
Pushed by mistake
|
|
When we construct from a custom GType
|
|
|
|
Document this, and take advantage of that fact to use
GstAggregator.srcpad.segment instead of GstAggregator.segment
https://bugzilla.gnome.org/show_bug.cgi?id=793942
|
|
See https://bugzilla.gnome.org/show_bug.cgi?id=793917
https://bugzilla.gnome.org/show_bug.cgi?id=793934
|
|
Also make sure the GType passed to the with_gtype versions
of the template constructors is_a GstPad
https://bugzilla.gnome.org/show_bug.cgi?id=793933
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=793284
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=793284
|
|
update_interval may be -1
https://bugzilla.gnome.org/show_bug.cgi?id=793284
|
|
For Mac OS, GST_EXTRA_MODULE_SUFFIX should be set as '.dylib'.
Otherwise, GStreamer fails to load its plugins.
https://bugzilla.gnome.org/show_bug.cgi?id=793584
|
|
API: gst_queue_array_pop_tail()
API: gst_queue_array_peek_tail()
These will be needed later for appsrc.
|
|
Mostly related to out parameters and their transfer
|
|
Position queries with GST_FORMAT_TIME are supposed to return stream
time.
gst_base_sink_get_position() estimates the current stream time on its
own instead of using gst_segment_to_stream_time(), but the algorithm
used was not taking segment.offset into account, resulting in invalid
values when this field was set to a non-zero value.
https://bugzilla.gnome.org/show_bug.cgi?id=792434
|
|
Such a setup is used in rtspsrc for its TCP connection
https://bugzilla.gnome.org/show_bug.cgi?id=793478
|
|
|
|
|
|
Occasionally this test would fail, especially if the system is under load,
because the position query would pick up the last position from the
last buffer timestamp which has a lower timestamp than what we're
looking for. The sleep is long enough, however. It's unclear to me why
exactly this happens but there seems to be some kind of scheduling
issue going on as the streaming thread floods the sink with buffers.
Let's throttle the fakesrc to 100 buffers per second and make the sink
sync to the clock to restore some sanity. It should be totally sufficient
to test what we want to test, and seems to make things reliable here.
|
|
Must undefine it before including gst headers, since the test
tests deprecated API.
|
|
Fix inverted logic. If GST_DISABLE_DEPRECATED is undefined,
we don't want warnings about deprecated API, and if it's
defined we do want warnings.
|
|
|
|
So new-in-1.12 index actually has some entries.
|
|
|
|
|
|
WARNING: Trying to compare values of different types (str, int).
The result of this is undefined and will become a hard error
in a future Meson release.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=769183
|