| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
In this case the socket callback has not been called
by libcurl and the curlsink has not been notified about any
connection problems by libcurl.
This indicates that it's a bug in libcurl so catch it as
an unknown error.
https://bugzilla.gnome.org/show_bug.cgi?id=754432
|
|
|
|
|
|
|
| |
gnome-shell doesn't the support wl_scaler interface which makes creating a
wayland display fail creation.
Found in the generic state changes test
|
|
|
|
|
|
| |
[Matthew Waters]: add NULL checks before unreffing
https://bugzilla.gnome.org/show_bug.cgi?id=762999
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
date string
The code in the gst_dash_demux_parse_http_xsdate() was trying to
handle the case where the string is not null terminated by resizing
the buffer and appending a zero byte. This does not work if the buffer
is exactly the length of the string because the gst_buffer_resize()
function does not re-allocate the buffer, it just changes its size.
If a buffer is passed to gst_dash_demux_parse_http_xsdate() that is
exactly the length of the string, the function fails with an assert
failure in gst_buffer_resize().
https://bugzilla.gnome.org/show_bug.cgi?id=762148
|
|
|
|
|
|
| |
Fixes problem in curlhttpsink when qtmux uses faststart.
https://bugzilla.gnome.org/show_bug.cgi?id=762013
|
|
|
|
|
| |
It can be used as a resource to verify if the server has updated
something in the Manifest when downloads are failing
|
|
|
|
|
|
|
| |
This caused a decoding error if the resulting (wrong) buffer size
was passed to the Opus decoding API.
https://bugzilla.gnome.org/show_bug.cgi?id=758158
|
|
|
|
| |
The format was provided as 'I420' instead of "I420", causing a crash.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
It's possible that the sink element will be freed before the widget is
destroyed. When the widget was eventually destroyed, it was attempting to
access member variables of the freed sink struct which resulted in undefined
behaviour.
Fix by disconnecting our signal on finalize.
https://bugzilla.gnome.org/show_bug.cgi?id=762098
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=760925
|
|
|
|
|
|
|
|
| |
On some embedded systems, sqrt() is not supported in the shader,
use the actual value of sqrt(2) instead.
Signed-off-by: Haihua Hu <b55597@freescale.com>
Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=761271
|
|
|
|
|
|
|
|
|
| |
SBC frame length calculation wasn't being rounded up to the nearest byte
(as specified in the A2DP 1.0 specification, section 12.9). This could
cause 'stereo' and 'joint stereo' mode SBC streams to have incorrectly
calculated frame lengths.
https://bugzilla.gnome.org/show_bug.cgi?id=742446
|
|
|
|
|
|
| |
Qt might not redraw the scene otherwise.
https://bugzilla.gnome.org/show_bug.cgi?id=758286
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=758943
|
|
|
|
|
| |
Otherwise composition will result in a black frame outside the transformed
video.
|
| |
|
|
|
|
|
|
| |
Fixes a memory leak leaking the texture objects.
https://bugzilla.gnome.org/show_bug.cgi?id=758286
|
|
|
|
|
|
| |
Mitigates the following critical
gst_gl_context_thread_add: assertion 'context->priv->active_thread == g_thread_self ()' failed
|
|
|
|
|
|
|
|
| |
The scene graph can be initialized when the we receive window handle change
notification and so we will not receive a scenegraph initialization
notification. Initialize ourself in this case.
https://bugzilla.gnome.org/show_bug.cgi?id=758337
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=758205
|
|
|
|
|
|
|
|
| |
There is a possibility that the _get_caps impl will be called with the
feature in the filter caps which when interecting with the template,
will return EMPTY and therefore fail negotiation.
https://bugzilla.gnome.org/show_bug.cgi?id=757854
|
|
|
|
|
|
|
|
|
|
| |
It's for the upstream element driving the pipeline to
handle seeks and send flush events or not, filters
should not interfere here, otherwise downstream pads
could be flushing before upstream pads are flushing,
which can result in GST_FLOW_ERROR being sent instead
of GST_FLOW_FLUSHING when trying to forward sticky
events at just the wrong moment.
|
|
|
|
| |
For all the other sample rates the encoder will have to resample internally.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This wl_display proxy is temporary only until waylandsink goes NULL,
at which point the connection to the display is disposed. Unfortunately,
if this is advertised as a GstContext, playbin will cache it and re-feed
it to the sink when it goes PLAYING again, but the wl_display pointer
will at that point be invalid and cause a crash.
Another solution to the problem would be to also cache the GstWlDisplay
object inside the GstContext, which would automatically ref-count
the display connection, but I see no reason in doing that at the moment,
as there are no known users of this GstContext outside waylandsink.
It's probably better to avoid chasing hidden refcounts.
https://bugzilla.gnome.org/show_bug.cgi?id=756567
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a (master) playlist contains a variant list entry without a
URI then during parsing of the next variant list entry we are
a) leaking the entry we're currently parsing (new_list), and
b) free'ing the pointer to the previous list entry (list) without
updating the pointer.
Hence when then adding the URI for the latest parsed entry, incorrect
information is stored, as the information is used from 'list' which
is not valid memory anymore, also leading to crashes.
Fix this by correctly storing the new variant list entry pointer
as needed.
https://bugzilla.gnome.org/show_bug.cgi?id=756861
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=756876
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=756653
|
|
|
|
|
|
|
| |
The value is optional in the range, and if it is absent it means we should
download until the end of stream. Not until position 0.
https://bugzilla.gnome.org/show_bug.cgi?id=748316
|
|
|
|
|
|
|
|
|
|
| |
In order to ensure the sequence_position will always be consistently updated,
store the current file duration.
This way, when we advance, we can always increment the position based on what
was previously outputted.
https://bugzilla.gnome.org/show_bug.cgi?id=752132
|
|
|
|
|
|
|
| |
Fixes assertion due to the sink_finalize() being run before the widget destroy
callback.
https://bugzilla.gnome.org/show_bug.cgi?id=755969
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=756592
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For live streams, we want to make sure there's a certain distance
between the sequence to play and the last (earliest) fragment.
The problem is that it assumes there are at least 3 fragments in
the playlist, which might not always be the case (like in the case
of a server restarting and gradually adding fragments).
In order to avoid ending up with negative sequence numbers (which
will just loop forever), limit the new target sequence number to
the highest of:
* either the first sequence number of the playlist (fallback)
* or 3 fragments from the last one (standard behaviour)
|
|
|
|
|
|
| |
Found with gst-inspect-1.0 -b in gst-uninstalled env.
https://bugzilla.gnome.org/show_bug.cgi?id=756383
|
|
|
|
| |
Identical to how the z-order property is proxied
|
|
|
|
|
|
|
| |
gst_mpd_client_has_next_period now calls gst_mpd_client_setup_media_presentation
to refresh the period information.
https://bugzilla.gnome.org/show_bug.cgi?id=756186
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=756001
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755981
|
|
|
|
|
|
| |
offset
https://bugzilla.gnome.org/show_bug.cgi?id=755824
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=752230
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=752230
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=752230
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=752230
|
|
|
|
|
|
|
|
|
|
|
| |
The same has to be done for AdaptationSet and SegmentList nodes still.
Also this does not correctly implement the semantics: by default Period (and
other nodes) should only be loaded when needed, not in the very beginning. We
need to implement lazy loading for them, which means adjusting
gst_mpd_client_setup_media_presentation().
https://bugzilla.gnome.org/show_bug.cgi?id=752230
|
|
|
|
|
|
| |
MPD resources if needed
https://bugzilla.gnome.org/show_bug.cgi?id=752230
|
|
|
|
|
|
|
| |
We still have to do something useful with them, like actually loading the
content behind the URL.
https://bugzilla.gnome.org/show_bug.cgi?id=752230
|
|
|
|
|
|
|
| |
gst_uri_join_strings() will return the second parameter if it is an absolute
URI. No need to do a (wrong) check if the URI is absolute or not beforehand.
https://bugzilla.gnome.org/show_bug.cgi?id=755134
|
|
|
|
|
|
| |
before the indexRange
https://bugzilla.gnome.org/show_bug.cgi?id=755132
|