Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Fix missing index in syncword searching
https://bugzilla.gnome.org/show_bug.cgi?id=745585
|
|
Use the object lock instead of the splitmux lock to protect
internal property variables, so they're not locked when
switching to a new file.
https://bugzilla.gnome.org/show_bug.cgi?id=744420
|
|
We need to set up the transport in any case, not just if we have a container
stream or a non-interleaved stream. Only if we have an interleaved stream and
are retrying, we should not set up the stream again.
https://bugzilla.gnome.org/show_bug.cgi?id=745599
|
|
|
|
Otherwise we will get not-negotiated later from rtpbin, and will never be able
to send RTCP packets back to the server. Note that error flow returns from the
RTCP pads are ignored, that's why it didn't fail more visible before.
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=745587
|
|
This is helpful to provide statistics in the format defined in
http://w3c.github.io/webrtc-stats/#dictionary-rtcrtpstreamstats-members.
https://bugzilla.gnome.org/show_bug.cgi?id=745587
|
|
Duration accumulation can cause rounding errors and generate wrong
duration with different buffers that share the same timestamp.
https://bugzilla.gnome.org/show_bug.cgi?id=745192
|
|
... and replace GST_BUFFER_TIMESTAMP that always return PTS with this method
that return PTS or DTS based on stream type.
https://bugzilla.gnome.org/show_bug.cgi?id=745192
|
|
And also create only one, there's no need yet to create all 32 until
we implement RFC2762.
|
|
This reverts commit 1591adf4cd843d13d8622a30c619425691a84128.
https://bugzilla.gnome.org/show_bug.cgi?id=745586#c1:
It's the beginning of an implementation of RFC 2762, which is needed for
large multicast groups. The implementation is not yet complete but why
not leave what is there and implement RFC 2762 instead?
|
|
rtpsession declares an array of maps to store srrcs but only the
the key 0 is being used. This patch replaces the array of maps
for just one map and remove useless parameters in rtpsession
https://bugzilla.gnome.org/show_bug.cgi?id=745586
|
|
In gst_avi_demux_handle_src_query, there is not needed code.
We already check about stream is vbr or not at the upper line.
o, we don't need to check this condition becase stream is not
vbr 100% in this case.
https://bugzilla.gnome.org/show_bug.cgi?id=745276
|
|
Unlike many other seek flags, the KEY_UNIT seek
flag is not copied over into the GstSegment,
since it's only relevant for the seek itself,
so we need to pass it explicitly to the seek
handler here.
https://bugzilla.gnome.org/show_bug.cgi?id=745339
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=745192
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=745192
|
|
|
|
This is implemented by the default query handler now.
|
|
This is now implemented in the default latency query handler.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=745226
|
|
When such stream is present demuxer should set DTS on buffers instead
of PTS. This is consistent with how VLC and libav/ffmpeg handle VFW
streams.
Sample file
https://s3.amazonaws.com/MatejK/Samples/Matroska-VFW-DTS-Only.mkv
https://bugzilla.gnome.org/show_bug.cgi?id=745192
|
|
Make use of NOT_AUTHORIZED error code instead of falling back to generic
READ error.
https://bugzilla.gnome.org/show_bug.cgi?id=601733
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=744983
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=737810
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=737810
|
|
Chrome uses a different one than gstreamer.
https://bugzilla.gnome.org/show_bug.cgi?id=737810
|
|
Otherwise we will just send buffers on the pad without any events beforehand
and will get g_warnings() about that.
|
|
gst_buffer_replace can handle NULL inputs by itself
|
|
The tfdt should be more accurate as the buffer timestamp is provided
by the fragmented format manifest and it might just be an approximation.
|
|
don't flush sticky events
We will otherwise flush away STREAM_START, CAPS or SEGMENT events and will
confuse downstream with buffers that come before such events.
|
|
We need different symbol names, because these symbols are also present
in the fragmented plugin ... which will cause conflicts when doing
static linking
|
|
|
|
Every instance of goto beach has buf_info equal NULL. Don't check
for a condition that never happens.
CID #1268399
|
|
The number of FFTs is calculated with the following formula:
guint nfft = 2 * bands - 2;
nfft is passed to gst_fft_f32_new() as the len argument and is of type
unsigned integer. This method required that len is at leas 1, then
maximum G_MAXINT, as other values would be negative. If we extrapolate
from the formula above it means we need "bands" to be between 2 and
((guint)G_MAXINT + 2) / 2).
https://bugzilla.gnome.org/show_bug.cgi?id=744213
|
|
Using the sparse streams can make the push-based seeking return
too far in the stream. It also can lead to issues as the
sparse streams will be ignored when restarting playback and,
if the sparse stream is the one that has the earliest sample,
it will confuse qtdemux's offsets as one stream will have
an earlier offset than the demuxer's one which might lead to
early EOS.
https://bugzilla.gnome.org/show_bug.cgi?id=742661
|
|
|
|
Parse the 'sidx' atom and update the total duration according to the
parser result. The isoff parser code is imported from
gst-plugins-bad's dashdemux and a gst_isoff_sidx_parser_add_data()
function was factored out of the gst_isoff_sidx_parser_add_buffer()
function.
https://bugzilla.gnome.org/show_bug.cgi?id=743578
|
|
Use gst_video_guess_framerate() from libgstvideo to guess
sensible common framerates where possible from the
floating point fps in the stream.
|
|
This now follows the design docs everywhere, especially the maximum latency
handling.
https://bugzilla.gnome.org/show_bug.cgi?id=744106
|
|
According to RFC 4585 section 3.5.3 step 1 we are not allowed to send
an early RTCP packet for the very first one. It must be a regular one.
Also make sure to not use last_rtcp_send_time in any calculations until
we actually sent an RTCP packet already. In specific this means that we
must not use it for forward reconsideration of the current RTCP send time.
Instead we don't do any forward reconsideration for the first RTCP packet.
|
|
|
|
x264enc might not have a max-key-int property, but it
has a key-int-max property...
|
|
|
|
Element x264enc doesn't have a max-key-int property
|
|
If execution goes to the beach in line 981, buf_info goes out of scope without
the memory being free'd. Handle this case.
CID #1268403
|
|
|
|
Add a unit test for file splitting, and fix the leaks in the
splitmuxsink it found
|
|
Assignment is done to variable segment.stop when the intention was to assign to
local variable stop. Instead of overwriting it, the value is now clamped and
segment.stop is set to it soon after.
CID #1265773
|