- Sep 18, 2017
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Sep 17, 2017
-
-
Sebastian Dröge authored
-
- Sep 08, 2017
-
-
-
This will be needed later when we switch to using -fvisibility=hidden.
-
- Sep 07, 2017
-
-
Add libunwind and dw to the .pc Requires.private. Fixes static library compilation if gstreamer was compiled with one of those dependencies https://bugzilla.gnome.org/show_bug.cgi?id=784795
- Sep 01, 2017
-
-
We would constantly re-post the taglist because posted_avg_rate only gets set to avg_bitrate if parse->priv->post_avg_bitrate is true, so if it's false the posted rate will always differ from the current average rate and we'd queue an update, which leads to us spamming downstream and the application with taglist updates. Fix this by only queuing an update if the average rate will actually be posted. These taglists updates could cause expensive operations on the application side, e.g. in Totem. https://bugzilla.gnome.org/show_bug.cgi?id=786561
-
- Aug 26, 2017
-
-
Thibault Saunier authored
Consider them as an empty array and do not segfault... https://bugzilla.gnome.org/show_bug.cgi?id=786670
-
- Aug 17, 2017
-
-
Tim-Philipp Müller authored
From 48a5d85 to dd9d403
-
Sebastian Dröge authored
Otherwise we might try unscheduling a clock id (that does not exist yet), then the streaming thread waits for id and the state change never continues because the streaming thread is blocked. Also shutting down and flushing and similar should return FLUSHING, not EOS. The stream is not over, we're just not accepting any buffers anymore.
-
- Aug 11, 2017
-
-
Sebastian Dröge authored
After EOS, it is possible for a pad to be resetted by sending either a STREAM_START or SEGMENT event Mimic the same behaviour when receiving STREAM_START/SEGMENT events in queue if we are EOS'd https://bugzilla.gnome.org/show_bug.cgi?id=786056
-
After EOS, it is possible for a pad to be resetted by sending either a STREAM_START or SEGMENT event Mimic the same behaviour when receiving STREAM_START/SEGMENT events in queue2 if we are EOS'd https://bugzilla.gnome.org/show_bug.cgi?id=786056
-
When queue-like elements are in "EOS" situation (received GST_FLOW_EOS from downstream or EOS was pushed), they drain buffers/events that wouldn't be processed anyway and let through events that might modify the EOS situation. Previously only GST_EVENT_EOS and GST_EVENT_SEGMENT events were let through, but we also need to allow GST_EVENT_STREAM_START to go through since it resets the EOS state of pads since 1.6 https://bugzilla.gnome.org/show_bug.cgi?id=786034
-
When downstream returns NOT_LINKED, we return the buffering level as being 100%. Since the queue is no longer being consumed/used downstream, we want applications to essentially "ignore" this queue for buffering purposes. If other streams are still being used, those stream buffering levels will be used. If none are used, upstream will post an error message on the bus indicating no streams are used. https://bugzilla.gnome.org/show_bug.cgi?id=785799
-
Sebastian Dröge authored
Without the former, event changes (e.g. setting a pad offset) does not take effect for the current buffer but only for the next one. Without the latter, non-blocking event probes would not see any updated events yet.
-
Sebastian Dröge authored
-
- Jul 14, 2017
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
buffer is not unreferened if preroll failed :Detailed Notes: - Problem : video freeze when switching from pause to 1/2-FF repeatedly - RootCause : buffer leaks in basesink - Solution : unref the buffer if prerolled failed :Testing Preformed: How to Test : pause -> 1/2 FF -> resume -> pause -> 1/2 FF ... https://bugzilla.gnome.org/show_bug.cgi?id=784932
-
- Jul 03, 2017
-
-
Tim-Philipp Müller authored
-
Otherwise when the glib is used as a subproject config.h is the glib one, not ours.
-
-
This was causing harmless assertion about the unreffed caps not being of type caps. https://bugzilla.gnome.org/show_bug.cgi?id=784041
-
- Jun 20, 2017
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Jun 17, 2017
- Jun 15, 2017
-
-
Sebastian Dröge authored
The gst_uri_construct function was escaping the location string as a generic uri string. This is incorrect since the slash('/') characters are reserved for use in this exact case. The patch changes the escape_string function mode to handle the path correctly. In 1.14 this function will be deprecated. https://bugzilla.gnome.org/show_bug.cgi?id=783787
-
- May 29, 2017
-
-
Otherwise in gst_base_src_query_latency(), it ended up sometimes thinking it wasn't -1 when it was actually.
-
Sebastian Dröge authored
Same as already used in GstControlBinding.
-
Sebastian Dröge authored
-