GNOME Bugzilla – Bug 721655
basesrc activation order logs error in some cases where it should not
Last modified: 2017-07-14 13:57:53 UTC
gst-launch-1.0 fakesrc can-activate-pull=false num-buffers=0 ! fakesink can-activate-pull=true This is a followup for the discussion after I submitted commit 74adc33982e08dd3bf1c1a991f8519dd821df549 Author: Stefan Sauer <ensonic@users.sf.net> Date: Mon Jan 6 21:04:32 2014 +0100 basesrc: demote error to warning This is not an error. A subclass returning FALSE for is_seekable() is one way of saying that we can't operate in pull mode. Here is a better patch. Main question is wheter we should end up calling start() before the pad is activated(). Previously I tried to make gst_base_src_activate_pull() fail if !gst_base_src_seekable(), but that code is not yet called at that moment.
Created attachment 265476 [details] [review] don't confuse GST_PAD_MODE_NONE and PULL
Comment on attachment 265476 [details] [review] don't confuse GST_PAD_MODE_NONE and PULL I think this looks good and makes sense
wtay, any comments?
I intentionally left this open, as I am not sure if we should even get there with unactivated pads in the first place ...
Then let's reopen it :) How do we get there with unactivated pads?
Let's close this again, I think it's not worth keeping this open :)