[Bug 749966] videoaggregator: add wait-sinks property to wait for inputs before creating output frames

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Fri May 29 12:46:23 PDT 2015


https://bugzilla.gnome.org/show_bug.cgi?id=749966

--- Comment #7 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
(In reply to Nicolas Dufresne (stormer) from comment #6)
> (In reply to Philippe Renon from comment #5)
> > This issue might be related (or not) to this one :
> > https://bugzilla.gnome.org/show_bug.cgi?id=749517
> 
> Not entirely. This is about having the ability to choose the first frame
> behaviour.
> 
> - Produce first frame on deadline (background/silence if nothing came in)

In live pipelines we always must produce frames on deadline, no matter what.
But the property could influence if we actually wait until the deadline, or if
we already produce data before if some pads have data.

> - Produce first frame only when at least one pad has data
> - Produce first frame only when all pad have data

This is only about the very first frame, and after that you wait as usual? That
doesn't sound right.

How does 3) is differ from 1), considering that for live streams we always must
produce data on deadline, and that for non-live streams the deadline is
infinity (i.e. we produce data when all pads have data).



I still think a per-pad configuration makes more sense for this. Usually from
the application side you know which pads will have data when, which are
important to wait for and which not.


Also I think it would make sense in aggregator to calculate the running time of
the segment.start of each pad, and don't wait for the pads where the running
time of segment.start is smaller than the current output running time.
(Maybe not aggregator, but audio/videoaggregator only).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list