- Dec 24, 2015
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Dec 21, 2015
-
-
Update the -Bsymbolic check with the version glib has. This version works with clang. https://bugzilla.gnome.org/show_bug.cgi?id=759713
-
- Dec 16, 2015
-
-
Sebastian Dröge authored
-
- Dec 14, 2015
-
-
Sebastian Dröge authored
If not, go back to the automatic pad numbering. CID 1195129
-
Sebastian Dröge authored
For CAPS events we will never ever have a FALSE return value here, so just remove the dead code instead of causing future confusion.
-
Sebastian Dröge authored
This reverts commit 78614c50. The code it was fixing does not have any effect anyway and will be removed in the next commit.
-
Once event is pushed to pad, then queue should not access the event. This is leading to invalid read valgrind errors https://bugzilla.gnome.org/show_bug.cgi?id=759430
-
Sebastian Dröge authored
Otherwise we'll take ownership of the event only if it's implemented, and leak the event in all other situations.
-
Sebastian Dröge authored
Use GST_PAD_PROBE_PASS to pass through all events other than EOS instead of blocking on the first non-EOS event forever. Also fix a typo in a comment in that function. Thanks to David Jaggard for reporting this on the mailing list.
- Dec 13, 2015
-
-
- Dec 12, 2015
-
-
Reynaldo H. Verdejo Pinochet authored
-
Reynaldo H. Verdejo Pinochet authored
-
Reynaldo H. Verdejo Pinochet authored
-
Reynaldo H. Verdejo Pinochet authored
-
Reynaldo H. Verdejo Pinochet authored
+fix typo on return value comment
-
- Dec 10, 2015
-
-
'gst_element_post_message' takes the ownership of the message, so it shall unref it when there is no post_message implementation. Otherwise message is leaked. https://bugzilla.gnome.org/show_bug.cgi?id=759300
-
Sebastian Dröge authored
This lock seems to exist only to prevent elements from changing states while events are being processed. However events are going to be processed nonetheless in those elements if sent directly via pads, so protection must already be implemented inside the elements for event handling if it is needed. As such having the lock here is not very useful and is actually causing various deadlocks in different situations as described in https://bugzilla.gnome.org/show_bug.cgi?id=744040
-
- Dec 09, 2015
-
-
Reynaldo H. Verdejo Pinochet authored
-
segment.position is meant for internal usage only, but the various GST_EVENT_SEGMENT creationg/parsing functions won't clear that field. Use the appropriate segment boundary as an initial value instead
-
Sebastian Dröge authored
Otherwise each bin might have a different latency in the end, causing synchronization problems. The bin will still first handle latency internally as before, but gives the overall pipeline the opportunity to update the latency of the whole pipeline afterwards. https://bugzilla.gnome.org/show_bug.cgi?id=759125
- Dec 08, 2015
-
-
Watching videos with variant bitrate is common to have delta more than 10 kbps, resulting in tag list spam. Instead of relying on fixed 10 kpbs delta, it is better to calculale the difference in percentage and update tag list only when bitrate changes more than 2%. https://bugzilla.gnome.org/show_bug.cgi?id=759055
-
- Dec 07, 2015
-
-
Nicolas Dufresne authored
From b319909 to 86e4663
-
Sebastian Dröge authored
The pad could be activated but flushing because of a FLUSH_START event. That's not what we're looking for here, we want to check for activated pads. https://bugzilla.gnome.org/show_bug.cgi?id=758928
-
- Dec 04, 2015
-
-
Thiago Santos authored
Changing states up and down while buffers are being pushed is not a valid use case. If a pad is deactivated and reactivated during a buffer push it is racy with the check of pushed sticky events and the actual chainfunction call. As it might call the chain without noticing the peer pad lost its previous sticky events. https://bugzilla.gnome.org/show_bug.cgi?id=758340
-
Nicolas Dufresne authored
In case of a run-time error message, the process return value was left unset. This would lead to error not being caught at shell level. https://bugzilla.gnome.org/show_bug.cgi?id=759019
-
Nicolas Dufresne authored
This reverts commit 2ee4cba2.
-
Tim-Philipp Müller authored
When an error happens in playing state, still return a non-0 exit code. https://bugzilla.gnome.org/show_bug.cgi?id=759019
-
My previous fix for #758029 wasn't quite right and simply made the race rarer. Some of the files are installed by install-exec and others by install-exec, so the hooks need to be split too. https://bugzilla.gnome.org/show_bug.cgi?id=758029
-
Wim Taymans authored
The allocation query has parameters with the meta API, not flags.
-
- Dec 02, 2015
-
-
Reynaldo H. Verdejo Pinochet authored
-