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.
This commit is contained in:
Wim Taymans 2012-04-06 16:46:58 +02:00
parent d8a61930af
commit 4638f15de2

View file

@ -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 */