What happens to just-requested tee srcpad in PLAYING pipeline?
Andrey Utkin
andrey.krieger.utkin at gmail.com
Fri Jan 10 03:14:27 PST 2014
When new requestable srcpad of tee element is created, it is
immediately activated, so pushed data and events from upstream
consider passing through it. Is this statement correct?
When data tries to pass through unlinked pad, it raises an error and
pauses pushing task (i.e. GstBaseSrc's or GstQueue's one) . Is this
statement correct?
If both above statements are correct, then how should we safely attach
another branch to tee in a pipeline in PLAYING state?
Another question. How can API user force GstBaseSrc's or GstQueue's
task to get back from paused state to running state? Which events can
lead to that? Is setting a pipeline to PLAYING state is right and sure
way to do that?
--
Andrey Utkin
More information about the gstreamer-devel
mailing list