| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
When getting sample from taglist, the memory is not being freed resulting in memory leak.
https://bugzilla.gnome.org/show_bug.cgi?id=756070
|
|
|
|
| |
Identical to how the z-order property is proxied
|
|
|
|
|
|
|
|
| |
Build error due to wrong argument type in debug message
aagg->priv->offset and next_offset are of type int64, but uint64
formatter is being used in logs. Changing all those to int64
https://bugzilla.gnome.org/show_bug.cgi?id=756065
|
|
|
|
|
|
|
| |
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=755892
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755981
|
|
|
|
|
|
| |
offset
https://bugzilla.gnome.org/show_bug.cgi?id=755824
|
|
|
|
|
|
|
| |
instead of always using 0. Otherwise we might output a lot of silence in the
beginning instead of outputting from the relevant position.
https://bugzilla.gnome.org/show_bug.cgi?id=755623
|
| |
|
|
|
|
|
|
|
| |
segment.time and segment.start can stay the same, and were always the same
before anyway because of a mistake.
https://bugzilla.gnome.org/show_bug.cgi?id=755623
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Doing the contrary has no effect and the consequence is that playback
will start with the lowest bitrate even if we can already handle
higher bitrate.
https://bugzilla.gnome.org/show_bug.cgi?id=755108
|
|
|
|
|
|
|
|
|
| |
Not doing this can lead the demuxer to attempt downloading fragments
for an invalid start time. The server would then send a HTTP
Precondition failed error, the demuxer would try some more times to
download the invalid fragment and eventually error out.
https://bugzilla.gnome.org/show_bug.cgi?id=754523
|
|
|
|
|
|
|
| |
This unbreaks building when some headers are under a non-standard path.
e.g. /usr/X11R6/include as on OpenBSD.
https://bugzilla.gnome.org/show_bug.cgi?id=755850
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755852
|
|
|
|
|
|
|
| |
While creating caps in audiointerleave tests, bitmask is being set as 0x9
This is resulting in segmentation fault. Fix the same by typecasting to guint64
https://bugzilla.gnome.org/show_bug.cgi?id=755840
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The buffer timestamps in the collect function will already be
running time, don't try to convert them again to running time,
this would yield CLOCK_TIME_NONE now that the segment is shifted
to account for negative dts.
This fixes x264enc ! mpegtsmux ! hlssink, which was broken
because mpegtsmux would send a downstream key unit event with
running time NONE and then hlssink would immediately send
another one upstream and it would just be a flood of force
keyframe events in both directions after the first one. This
would then break hlssink because it uses multifilesink in
next-file=key-unit-event mode, and starting a new file after
every few kB does not work well for HLS.
|
|
|
|
|
|
|
| |
Remove weird use of private gtype defines and fix compilation
with older glib versions such as 2.36.
https://bugzilla.gnome.org/show_bug.cgi?id=755754
|
|
|
|
|
|
|
|
| |
Move handling of a GstSample in a separate function, and unref the
sample after calling it. libass copies the font data so we don't need to
keep it around.
https://bugzilla.gnome.org/show_bug.cgi?id=755759
|
|
|
|
|
|
| |
We don't want the gap event to be forwarded
https://bugzilla.gnome.org/show_bug.cgi?id=755759
|
| |
|
|
|
|
|
|
|
| |
When proxying keyboard/navigation/mouse events, only unref a successfully
retreived peer pad.
https://bugzilla.gnome.org/show_bug.cgi?id=755738
|
|
|
|
|
|
|
|
|
| |
Ignore the normal gap threshold for laggy streams and
immediately catch all streams up to the end of the segment
when processing gap updates for a segment during a
still frame sequence.
https://bugzilla.gnome.org/show_bug.cgi?id=755680
|
|
|
|
|
|
| |
U and V were inverted
https://bugzilla.gnome.org/show_bug.cgi?id=755239
|
|
|
|
|
| |
This makes the audiomixer unit test time out in master.
Broke with 587e7c4
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fixes this error with chromium gpu process:
GL_INVALID_OPERATION, glBindBuffer: buffer bound to more than 1 target
https://bugzilla.gnome.org/show_bug.cgi?id=755618
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755456
|
|
|
|
| |
We're not doing anything at all from the main thread in other cases.
|
|
|
|
|
|
|
|
|
| |
In case the format changed fast and the pending format is different
than the currently set but the currently set is equal to the pending
one we could end up having mismatch between the finally set format
and the data stream format.
https://bugzilla.gnome.org/show_bug.cgi?id=755542
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755542
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755251
|
|
|
|
|
|
|
| |
Gtk is not MT safe thus we need to make sure that everything is done
in the main thread when working with it.
https://bugzilla.gnome.org/show_bug.cgi?id=755251
|
|
|
|
|
|
|
| |
Otherwise we're going to return times starting at 0 again after shutting down
an element for a specific input/output and then using it again later.
https://bugzilla.gnome.org/show_bug.cgi?id=755426
|
|
|
|
|
|
| |
again from there
https://bugzilla.gnome.org/show_bug.cgi?id=755426
|