| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Looks like this file was missed in Bug 728960:
https://bugzilla.gnome.org/show_bug.cgi?id=728960
https://bugzilla.gnome.org/show_bug.cgi?id=730459
|
|
|
|
|
|
| |
Allows us to selectively use EGLImages only when available
https://bugzilla.gnome.org/show_bug.cgi?id=728234
|
|
|
|
|
|
|
|
| |
Expose one more libcurl option: CURLOPT_SSH_HOST_PUBLIC_KEY_MD5.
This allows authenticating the server by the MD5 fingerprint of
the server's public key.
https://bugzilla.gnome.org/show_bug.cgi?id=723167
|
|
|
|
|
|
|
| |
Otherwise we will cause assertions everywhere by passing NULL to functions
and eventually crash when dereferencing a NULL pointer.
https://bugzilla.gnome.org/show_bug.cgi?id=730069
|
|
|
|
| |
CID 1214604
|
|
|
|
|
|
|
| |
Check gst_buffer_map return and remember to unmap and free memory before
returning
https://bugzilla.gnome.org/show_bug.cgi?id=730133
|
| |
|
|
|
|
| |
In finalize, also release the playlist
|
|
|
|
|
|
| |
Avoid leaking the GstDateTime instances when summing dates
CID #1212143
|
|
|
|
|
|
|
|
| |
The parsing function already frees the old value (if any), avoid a double
free by not freeing it before calling the function without setting the
pointer to NULL
Coverity ID: 1212178
|
|
|
|
|
|
|
|
|
| |
The _parse_url function already frees the previous pointer, avoid
freeing it before without setting to null or we have a double free.
Coverity ID: 1212181
Coverity ID: 1212180
Coverity ID: 1212179
|
|
|
|
|
|
| |
It was leaking the config, but also not using it...
CID #1212155
|
|
|
|
|
|
|
|
| |
And avoid useless call to _get_output_state (set_output_state() already
returns it).
CID #1212160
CID #1212161
|
|
|
|
| |
CID #1212142
|
|
|
|
|
| |
It might get stuck when posting the message while
a reconfigure event is being pushed upstream
|
| |
|
|
|
|
|
| |
set up a bin message handler to get notified of error messages from
the internal source element
|
|
|
|
|
| |
Upstream or internal elements are irrelevant and we should
always succeed.
|
|
|
|
|
| |
Store the latest pushed timestamp so that mssdemux streams know
where they are in time
|
|
|
|
| |
There is no internal storage of buffers anymore
|
|
|
|
| |
new bitrate = (old bitrate + (last fragment bitrate * 3)) / 4
|
|
|
|
|
|
| |
Refactor mssdemux to remove uridownloader to use an internal
source element which reduces startup latency and provides smaller
buffers for better buffering management downstream
|
| |
|
|
|
|
| |
The uridownloader for the stream fragments isn't used anymore.
|
|
|
|
|
|
| |
It does not makes sense and asserts
Based on 7f9aac386fd5d5921c80100889a5f212c0148a88 from gst-plugins-base.
|
|
|
|
| |
It's not really right to just go EOS as if nothing was wrong.
|
|
|
|
|
|
|
|
|
|
| |
data does not have to be freed at all here, it's a pointer to
an arbitrary position inside the current line. Also don't reuse
the data variable for anything else, that will cause crashes
in playlists that have the I-frame playlist URI followed by
other attributes.
CID 1212127
|
| |
|
|
|
|
| |
Rename init_format to set_format
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=729658
|
|
|
|
|
| |
It is not used as dashdemux doesn't have a internal buffer
for fragments anymore
|
|
|
|
|
| |
The 'catch up mode' isn't needed anymore since dashdemux
is downloading and pushing from the same thread
|
| |
|
|
|
|
|
| |
related to missing plugins, bad URI and a lockup on dealing with
errors from the source.
|
|
|
|
|
| |
Setting it to the other parts of the fragment is slightly wrong
and misleading as it isn't accurate enough.
|
|
|
|
|
|
| |
Set up a message handling function to be able to catch errors
from the source element and signal the cond to allow the download
loop to retry the download.
|
|
|
|
| |
To abort earlier in case of failures
|
|
|
|
|
| |
Upstream or internal elements are irrelevant and we should
always succeed.
|
|
|
|
| |
new bitrate = (old bitrate + (last fragment bitrate * 3)) / 4
|
|
|
|
|
|
| |
Instead, use a source element linked to a ghostpad to provide
smaller buffers and more granular control for downstream
buffering elements while also reducing startup latency
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=729542
|
| |
|
| |
|
|
|
|
|
| |
Removing all the keys can be a problem as it also resets the various
counters, so instead add an option to remove a single key.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Only the first buffer of a fragment has its timestamp set, so only
update the segment.position when pushing those buffers to avoid
having GST_CLOCK_TIME_NONE set to the position
https://bugzilla.gnome.org/show_bug.cgi?id=729364
|
|
|
|
| |
the playlist
|
| |
|
| |
|