- Apr 12, 2012
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Apr 11, 2012
-
-
Wim Taymans authored
-
Wim Taymans authored
-
Wim Taymans authored
-
Wim Taymans authored
Conflicts: gst/gsttoc.c plugins/elements/gstqueue2.c
-
Wim Taymans authored
When we don't have the requested data in the ringbuffer and we move our read pointer to the requested position, signal the delete cond to inform the writer that we changed the current fill level. If we don't, the writer might stay blocked and we might wait forever.
-
Wim Taymans authored
-
Wim Taymans authored
When we don't have enough bytes in the ringbuffer to satisfy the current request, first update the current read position before waiting. If we don't do that, the ringbuffer might appear full and the writer will never write more bytes to wake us up.
-
Wim Taymans authored
Only add the range when we receive a segment event on the sinkpad. The add_range method will modify the write position, which only makes sense to do on the sinkpad.
-
Wim Taymans authored
We're not writing to the offset of the buffer
-
Wim Taymans authored
-
Alexander Saprykin authored
-
Alexander Saprykin authored
-
Alexander Saprykin authored
-
Alexander Saprykin authored
-
Alexander Saprykin authored
-
Alexander Saprykin authored
-
Sreerenj Balachandran authored
-
- Apr 10, 2012
-
-
Wim Taymans authored
-
Wim Taymans authored
Also clear the seeking flag when downstream is in pull mode.
-
Wim Taymans authored
Conflicts: gst/gst.c plugins/elements/gstqueue2.c
-
Wim Taymans authored
-
Wim Taymans authored
-
Wim Taymans authored
Set the seeking flag right before we send a seek event upstream and discard all data untill we see a flush-stop again. We need to do this because we activate the range that we seek to immediately after sending the seek event and it is possible that we receive data in our chain function from before the seek which would then be added to the wrong range resulting in data corruption.
-
Wim Taymans authored
When using the ringbuffer, handle the newsegment event like we handle it when using the temp-file mode: create a new range for the new byte segment. The new segment should normally already be created when we do a seek.
-
- Apr 09, 2012
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Add gst_element_class_{add,set}_metadata() variants for static strings, so we can avoid unnecessary g_strdup()s. API: gst_element_class_add_static_metadata() API: gst_element_class_set_static_metadata()
-
- Apr 08, 2012
-
-
Tim-Philipp Müller authored
It doesn't actually do anything.
-
-
Tim-Philipp Müller authored
-
- Apr 07, 2012
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Fixes 'make check'.
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-