GNOME Bugzilla – Bug 676304
queues: Should reset last downstream flow-return on reconfigure event
Last modified: 2013-07-17 13:13:01 UTC
See summary. The reconfigure event could indicate that the stream is now linked. Passing not-linked upstream should be stopped as soon as possible. Also in multiqueue the streams that saw a reconfigure event should be assumed to be "active" and linked again until downstream returns not-linked again.
According to the same principle, sources should start pushing again after a reconfigure event.
commit 9ac409df48a1c8af0e5084023dd699f493b4c94d Author: Wim Taymans <wim.taymans@collabora.co.uk> Date: Thu Apr 4 19:07:29 2013 +0200 queue2: start pushing again on RECONFIGURE When we got NOT_LINKED before and we receive a RECONFIGURE event, start pushing again on the source pad. See https://bugzilla.gnome.org/show_bug.cgi?id=676304 commit c955ddc712f3b4de9ef5d822b95a6f4bd9985eb3 Author: Wim Taymans <wim.taymans@collabora.co.uk> Date: Thu Apr 4 19:06:35 2013 +0200 queue: start pushing again on RECONFIGURE When we got NOT_LINKED before and we receive a RECONFIGURE event, start pushing again on the source pad. See https://bugzilla.gnome.org/show_bug.cgi?id=676304
commit bda406c42f4005dd07e7997a1a2443a1543d69f6 Author: Wim Taymans <wim.taymans@collabora.co.uk> Date: Thu Apr 4 19:16:23 2013 +0200 multiqueue: start pushing again on RECONFIGURE When we got NOT_LINKED before and we receive a RECONFIGURE event, start pushing again on the source pad. See https://bugzilla.gnome.org/show_bug.cgi?id=676304