- Sep 19, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Sep 18, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Sep 17, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
It was unintuitive that GstContext was actually a list of different contexts. GstContext now is only a type string and a structure to contain the actual context.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
Non-persistent contexts are removed when elements go back to NULL state, persistent contexts are not. Applications most likely want to set persistent contexts.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
This is going to be implemented with an upstream query instead for consistency and simplicity.
-
- Sep 13, 2013
-
-
Since the default number of max unused threads in GThreadPool has been changed from 0 to 2 it needs to be set to 0 to stop all threads or valgrind will report them as memory leaks.
-
- Sep 10, 2013
-
-
The change should have been from PARAM_CONSTRUCT_ONLY to PARAM_CONSTRUCT, otherwise bindings are affected, since they look for the CONSTRUCT flag. See ec55363d
-
Sebastian Dröge authored
Otherwise queue->level is NULL and dereferencing that is not a good idea in general. https://bugzilla.gnome.org/show_bug.cgi?id=707648
-
- Sep 09, 2013
-
-
Sebastian Dröge authored
The GQuarks are not exported by any public API
-
-
If a metadata has no dependency as shown by the tags, copy it.
-
-
Sebastian Dröge authored
-
-
In some cases the wait for more data was happening without updating the buffering state, meaning the API user would not be able to notice it should pause the pipeline and update UI to indicate that is the case, the video would likely stutter instead. https://bugzilla.gnome.org/show_bug.cgi?id=707648
-
- Sep 05, 2013
-
-
Thiago Santos authored
The seqnum of the segment after a seek should be the same of the seek event. Downstream elements might rely on seqnums to identify events related to a seek. This is particularly important when a demuxer maps a TIME seek into a BYTES seek for upstream and it needs to identify the corresponding segment event and map it back into TIME to push downstream, possibly using the values from the original seek event. https://bugzilla.gnome.org/show_bug.cgi?id=707530
-
If a pad is removed while a collectpads element (say adder) is in a chain function waiting to be collected, there is a possibility that an unref happens on a NULL pointer. https://bugzilla.gnome.org/show_bug.cgi?id=707536
-
- Sep 04, 2013
-
-
Christian Fredrik Kalager Schaller authored
-
Sebastian Dröge authored
Thanks to Edward Hervey for noticing.
-
Tim-Philipp Müller authored
So it's not in PATH in an uninstalled setup (thwarting gst-play autocompletion).
-
If the multiqueue has automatically grown chances are good that we will cause the pipeline to starve if the maximum level is reduced below that automatically grown size. https://bugzilla.gnome.org/show_bug.cgi?id=707156
-
- Sep 02, 2013
-
-
Sebastian Dröge authored
This does not make any sense at all and breaks timestamp->running_time calculations in unpredictable ways. https://bugzilla.gnome.org/show_bug.cgi?id=707130
-
- Aug 30, 2013
-
-
When removing a segment event. https://bugzilla.gnome.org/show_bug.cgi?id=707088
-
- Aug 29, 2013
-
-
Tim-Philipp Müller authored
-
- Aug 28, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Aug 27, 2013
-
-
Alessandro Decina authored
-