[Bug 777572] GstStream: Thread-safety concerns and modification/refinement of stream details
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Wed Feb 8 17:58:13 UTC 2017
https://bugzilla.gnome.org/show_bug.cgi?id=777572
--- Comment #1 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
As discussed at FOSDEM with Edward, the idea here would be that
a) demuxer (or other elements that split streams, e.g. h264parse splitting off
a CC stream) will create a new GstStream with the same stream-id (plus new
collection) whenever something is changing, and sends that downstream
b) parsers, decoders, etc are adding their things to the GstStream whenever
they know something. While this can cause inconsistencies, the idea is that
further downstream elements will always also get the updated stream (via the
event), and parallel elements would extract the same information. So it would
converge after a short while
And elements would never ever use the information from the stream for anything
related to how they work, for that the relevant other events are to be used
which are always in sync with the current situation at the element.
--
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