Age | Commit message (Collapse) | Author | Files | Lines |
|
The caps query cache adds a new ref to the caps and some tests
were checking the caps refcount
Also push reconfigure for selector tests to force cache cleanup
|
|
Source pads are less used in caps queries and it is unusual
to have to notificate downstream that upstream can now support
a new format. Upstream, in this case, just starts negotiating
again.
Besides, the reconfigure event is uptstream only.
|
|
|
|
Will cache the results of a caps query until the pad is flushed,
deactivated or a reconfigure event is seen.
This is an attempt to quickly reply to the same caps queries that
are common when pipeline is starting up
|
|
|
|
Cache the results for NULL and the last filter used, those should
cover the majority of cases a pad has to reply to a caps query
|
|
It should provide a caps->caps mapping, allowing cache of caps
queries by mapping filter->result.
|
|
It allows to properly emitting it for all newly created elements
https://bugzilla.gnome.org/show_bug.cgi?id=757045
|
|
To be able to get the time the elements were created instead of
just logging them without a time
|
|
Without this, flushing might not unblock the streaming thread and cause deadlocks.
https://bugzilla.gnome.org/show_bug.cgi?id=757257
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=757197
|
|
added
https://bugzilla.gnome.org/show_bug.cgi?id=757197
|
|
Implement gst_buffer_get_net_address_meta() as a function instead
of a macro in order to get gobject-introspection to work.
https://bugzilla.gnome.org/show_bug.cgi?id=702921
|
|
There is a similar explanation in gst_caps_make_writable, but the existing
documentation can be misleading since it does not define what 'is already
writable' means.
Also note when this function is meant to be used.
|
|
It is not necessarily clear from the existing introspection tags and
documentation alone.
|
|
The input of queue/queue2 might have DTS set, in which cas we want
to take that into account (instead of the PTS) to calculate position
and queue levels.
https://bugzilla.gnome.org/show_bug.cgi?id=756507
|
|
In order to accurately determine the amount (in time) of data
travelling in queues, we should use an increasing value.
If buffers are encoded and potentially reordered, we should be
using their DTS (increasing) and not PTS (reordered)
https://bugzilla.gnome.org/show_bug.cgi?id=756507
|
|
Simplifies code a bit
|
|
API: GST_BUFFER_DTS_OR_PTS
Many scenarios/elements require dealing with streams of buffers that
might have DTS set (i.e. encoded data, potentially reordered)
To simplify getting the increasing "timestamp" of those buffers, create
a macro that will return the DTS if valid, and if not the PTS
|
|
Very useful formats in debug output so best to have them in the
generated doc.
https://bugzilla.gnome.org/show_bug.cgi?id=756115
|
|
position not inside the segment
Fixes GstPipeline unit test.
https://bugzilla.gnome.org/show_bug.cgi?id=756564
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=757065
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=757065
|
|
Currently we only show element properties values, we should also show
pad properties values
https://bugzilla.gnome.org/show_bug.cgi?id=754166
|
|
|
|
position functions
See formula clarifications in design docs for calculation details.
https://bugzilla.gnome.org/show_bug.cgi?id=756564
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=755651
|
|
They take a GstBaseSink instance as argument at not a GstPad. Rename the
argument to 'obj' which is not miss leading and in line with
GST_BASE_SINK_PAD(obj).
https://bugzilla.gnome.org/show_bug.cgi?id=756954
|
|
|
|
From b99800a to b319909
|
|
It's not get_bufferlist(). Because of that it was ignored by the docs and
G-I, leading to crashes because of broken ownership transfer.
https://bugzilla.gnome.org/show_bug.cgi?id=756898
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=756870
|
|
From 9aed1d7 to b99800a
|
|
We always want to free the open file log if fopen() succeeded. Independently
of if fgets() succeeds or fails.
CID 1326055
https://bugzilla.gnome.org/show_bug.cgi?id=756864
|
|
Updated gst_segment_position_from_stream_time and gst_segment_to_stream_time to reflect correct calculations for the case when the applied rate is negative.
Pasting from design docs:
===============================
Stream time is calculated using the buffer times and the preceding SEGMENT
event as follows:
stream_time = (B.timestamp - S.start) * ABS (S.applied_rate) + S.time
For negative rates, B.timestamp will go backwards from S.stop to S.start,
making the stream time go backwards.
===============================
Therefore, the calculation for applied_rate < 0 should be:
stream_time = (S.stop - B.timestamp) * ABS (S.applied_rate) + S.time
and the reverse:
B.timestamp = S.stop - (stream_time - S.time) / ABS (S.applied_rate)
https://bugzilla.gnome.org/show_bug.cgi?id=756810
|
|
The subsystem reused the GST_TRACE var that is allready in use by the alloc tracer.
Fixes #756760
|
|
Previously this code was just blindly setting the cached flow return
of downstream to GST_FLOW_OK when we get a SEGMENT.
The problem is that this can not be done blindly. If downstream was
not linked, the corresponding sinqlequeue source pad thread might be
waiting for the next ID to be woken up upon.
By blindly setting the cached return value to GST_FLOW_OK, and if that
stream was the only one that was NOT_LINKED, then the next time we
check (from any other thread) to see if we need to wake up a source pad
thread ... we won't even try, because none of the cached flow return
are equal to GST_FLOW_NOT_LINKED.
This would result in that thread never being woken up
https://bugzilla.gnome.org/show_bug.cgi?id=756645
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=755657
|
|
An ASYNC READY->PAUSED might have failed without the bin code noticing during
the state change, in which case we will never get PAUSED->READY and would leak
messages.
https://bugzilla.gnome.org/show_bug.cgi?id=756611
|
|
|
|
So it's clearer what leaked.
|
|
Accept both filename and a URI as argument, and print
the error from the error message if there's an error.
https://bugzilla.gnome.org/show_bug.cgi?id=756630
|
|
It should be 1.2 unless this is a flag from the future
|
|
In the same way core now allows STREAM_START to remove the flushing
state from pads, we need to do the same thing in multiqueue
|
|
on failures
https://bugzilla.gnome.org/show_bug.cgi?id=748316
|
|
Our current position has nothing to do with being linked or not.
Avoids having stray segment updates fired every 2s
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=756208
|
|
It does not exist otherwise and linking will fail.
|
|
In file included from gst-ptp-helper.c:40:0:
/usr/include/net/if.h:265:19: error: field 'ifru_addr' has incomplete type
struct sockaddr ifru_addr;
https://bugzilla.gnome.org/show_bug.cgi?id=756136
|
|
This reverts commit 8ddbf76626a48420306869db1d171f854cc25310.
|