summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWim Taymans <wim.taymans@collabora.co.uk>2012-04-06 15:42:04 +0200
committerWim Taymans <wim.taymans@collabora.co.uk>2012-04-06 15:42:04 +0200
commitef8a5b3a2a9ba18af23f67b5dc10708adcac3aec (patch)
tree1221303606cba5bf564f1b8a2e95860e43f4790e
parent88c4234fa2d89c59b8cadb9ca2b04d67069899f4 (diff)
queue2: don't update the current reading_pos in flushtp-vision
An upstream flush from the decoder should not make buffering go to 0, the next pull request might be inside a range that we have and then we don't need to buffer at all. If the next pull is outside anything we have, buffering will happen as usual.
-rw-r--r--plugins/elements/gstqueue2.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/plugins/elements/gstqueue2.c b/plugins/elements/gstqueue2.c
index 0bda2e780..77f68d94f 100644
--- a/plugins/elements/gstqueue2.c
+++ b/plugins/elements/gstqueue2.c
@@ -2629,12 +2629,6 @@ gst_queue2_handle_src_event (GstPad * pad, GstEvent * event)
/* now unblock the getrange function */
GST_QUEUE2_MUTEX_LOCK (queue);
queue->srcresult = GST_FLOW_OK;
- if (queue->current) {
- /* forget the highest read offset, we'll calculate a new one when we
- * get the next getrange request. We need to do this in order to reset
- * the buffering percentage */
- queue->current->max_reading_pos = 0;
- }
GST_QUEUE2_MUTEX_UNLOCK (queue);
/* when using a temp file, we eat the event */