Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This is a prepatory step for adding tests for `GstNetControlMessageMeta`.
`GstNetControlMessageMeta` is likely to be harder to test than
`GstNetAddressMeta`, so this commit helps by focusing on the aspects of
GstMeta that need to be tested.
|
|
In case there is an IDLE probe fired from gst_pad_push_data and it
doesn't return GST_FLOW_OK, the code jumps to the probe_stopped
label which tries to unref the data object. However, at this point
the data object belongs downstream and must not be touched.
By setting data = NULL, the code skips this unref.
https://bugzilla.gnome.org//show_bug.cgi?id=753151
|
|
Don't use 'glbufferrefmeta' as the debug category for the
parent buffer meta.
|
|
upstream_size can be negative but queue->upstream_size is unsigned type.
to get a chance to update queue->upstream_size in gst_queue2_get_range()
it should keep the default value.
https://bugzilla.gnome.org/show_bug.cgi?id=753011
|
|
Don't export the debug variable for the parent_buffer_meta.
This was accidentally exported and shouldn't be public
|
|
Helps to distiguish multiple filesinks.
|
|
We don't "iterate" bins or pipelines any more.
|
|
Fixes make check-valgrind
|
|
This fixes miss-use of @ instead of % to refer to enumeration
values.
|
|
|
|
This is documentation for the HTML documentation.
|
|
This is purely for documentation purpose. This way the values will
show up in the HTML documentation.
|
|
It's not GstAllocatorParams but GstAllocationParams.
|
|
sink_elenment_name is not a parameter of gst_harness_add_sink_harness()
function, but still it show up in documentation.
|
|
for something
If nobody ever saw the previous filter caps, nothing could've negotiated with
them and we can just pretend they never existed at all.
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=752800
|
|
|
|
gst_query_find_allocation_meta() requires the query to be
writable to work. This patch ensure avoids taking a reference
on the query, so we can now check if a certain allocation meta
is present.
https://bugzilla.gnome.org/show_bug.cgi?id=752661
|
|
No GBytes involved.
|
|
Resetting the flushing state of the pads at the end of the
PAUSED_TO_READY transition will make pads handle serialized
queries again which will wait for non-active pads and might
cause deadlocks when stopping the pipeline.
Move the reset to the READY_TO_PAUSED instead.
https://bugzilla.gnome.org/show_bug.cgi?id=752623
|
|
By introducing gst_harness_add_src_harness and gst_harness_add_sink_harness
we collect all sub-harness setup in one function, making the previous
sub-harness creation functions now calls these directly, and making it
much easier (and less error-prone) to add your own src or sink-harness
using the more generic harness-creation functions.
|
|
This line has no purpose, clearly gst_segment_do_seek() is doing
the right job, also, having the start time (a timestamp) be that
same as time (the stream time) is quite odd.
https://bugzilla.gnome.org/show_bug.cgi?id=750783
|
|
The stop shall be relative to start if extrapolated from the
duration.
https://bugzilla.gnome.org/show_bug.cgi?id=750783
|
|
Release the monitor lock when calling the provider start/stop methods.
Because we release the lock now, We need to make sure we check the
cookie again and keep track of started and removed providers.
|
|
Protect against wrong arguments.
Clean up the header file indentation.
|
|
The deviceproviders are added to the array sorted by their rank. Make
sure we keep this ordering when removing a provider.
We use _prepend to collect the devices, use g_list_reverse to get the
devices in the right order; sorted by rank and in the same order as
returned by the provider.
|
|
|
|
|
|
|
|
Given that the element has the possibility to have one, they should
already be there.
https://bugzilla.gnome.org/show_bug.cgi?id=752498
|
|
The element flag does not indicate wether a bin should be tested as a
source or as a sink, eg. a bin with the sink flag may still have a
source pad and a bin with the source flag may have a sink pad. In this
case it is better to determine the element type by looking at the
available pads and pad templates.
Also rename srcpad and sinkpad where it actually represents
element_srcpad_name and element_sinkpad_name.
https://bugzilla.gnome.org/show_bug.cgi?id=752493
|
|
Fixes issue where if a sink harness was added late the sticky events
would not be forwared.
https://bugzilla.gnome.org/show_bug.cgi?id=752494
|
|
|
|
|
|
Add a generic structure to hold any additional properties about the
device.
|
|
|
|
|
|
Should only access the object structure after checking
it's valid in gst_task_join().
https://bugzilla.gnome.org/show_bug.cgi?id=746385
https://bugzilla.gnome.org/show_bug.cgi?id=746431
|
|
Copy the GstMeta contents over to the new buffer.
https://bugzilla.gnome.org/show_bug.cgi?id=749590
|
|
For files which are smaller than 1.5 seconds, the duration
estimation does not happen. So the duration will always be
displayed as 0. Updating the duration on EOS when the estimation
has not happened already
https://bugzilla.gnome.org/show_bug.cgi?id=750131
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=752116
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=749873
|
|
get_list/get_buffer_list should be done with buffers in adapter remaining
while take_list/take_buffer_list flushes each buffer one by one.
https://bugzilla.gnome.org/show_bug.cgi?id=752116
|
|
|
|
We must make the buffer writable to write its PTS and DTS, and also
reset its duration.
The behaviour is now the same as before commit c3bcbadd, except metas
might still be attached to the buffer extracted from the adapter.
https://bugzilla.gnome.org/show_bug.cgi?id=752092
|
|
These screw with indentation and seem a bit trivial. Just copy'n'paste.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=751778
|
|
Writing a test for unscheduling the gst_clock_id_wait inside the
identity element, found an invalid read, caused by removing the clock-id
when calling _unschedule instead of letting the code calling _wait remove
the clock-id after being unscheduled.
https://bugzilla.gnome.org/show_bug.cgi?id=752055
|