mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-10-04 17:52:29 +00:00
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:
parent
d8a61930af
commit
4638f15de2
1 changed files with 0 additions and 6 deletions
|
@ -2629,12 +2629,6 @@ gst_queue2_handle_src_event (GstPad * pad, GstEvent * event)
|
||||||
/* now unblock the getrange function */
|
/* now unblock the getrange function */
|
||||||
GST_QUEUE2_MUTEX_LOCK (queue);
|
GST_QUEUE2_MUTEX_LOCK (queue);
|
||||||
queue->srcresult = GST_FLOW_OK;
|
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);
|
GST_QUEUE2_MUTEX_UNLOCK (queue);
|
||||||
|
|
||||||
/* when using a temp file, we eat the event */
|
/* when using a temp file, we eat the event */
|
||||||
|
|
Loading…
Reference in a new issue