From 4638f15de282d660c16449073536d66441ced1bd Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Fri, 6 Apr 2012 16:46:58 +0200 Subject: [PATCH] queue2: don't update the current reading_pos in flush A flush from the upstream element 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 anyway. --- plugins/elements/gstqueue2.c | 6 ------ 1 file changed, 6 deletions(-) diff --git a/plugins/elements/gstqueue2.c b/plugins/elements/gstqueue2.c index 0bda2e7..77f68d9 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 */ -- 2.7.4