projects / platform / upstream / gstreamer.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d8a6193) | patch
queue2: don't update the current reading_pos in flush
authorWim Taymans <wim.taymans@collabora.co.uk>
Fri, 6 Apr 2012 14:46:58 +0000 (16:46 +0200)
committerWim Taymans <wim.taymans@collabora.co.uk>
Fri, 6 Apr 2012 14:46:58 +0000 (16:46 +0200)
commit4638f15de282d660c16449073536d66441ced1bd
tree6d4e48f03ccccb0c9ab8d7c9471156a3d9e825dftree | snapshot
parentd8a61930afa10592c24031023df9a30444ae5b66commit | diff
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 diff | blob | history
Domain: Multimedia / Media Common;