GNOME Bugzilla – Bug 657316
capsfilter is racy when changing the caps during initial pipeline startup
Last modified: 2011-08-26 08:24:32 UTC
_set_caps only gets called when the buffer is actually pushed, so there is a reasonably big window between when the initial caps are retrieved and when the caps are set on our src pad. So we can't assume the not having negotiated caps on our src pad means _get_caps still has to be called.
Created attachment 194687 [details] [review] proposed patch
commit 341d7a4c0dbd69f86faaf1ffd2e94e99bac6f8c9 Author: Sjoerd Simons <sjoerd.simons@collabora.co.uk> Date: Wed Jul 20 14:05:27 2011 +0200 capsfilter: don't assume _get_caps still has to be _set_caps only gets called when the buffer is actually pushed, so there is a reasonably big window between when the initial caps are retrieved and when the caps are set on our src pad. So we can't assume the not having negotiated caps on our src pad means _get_caps still has to be called. Instead simply always suggest the new caps on buffer_alloc.