[Bug 759355] splitmuxsink: documented pipeline example too simplistic to be useful

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Fri Dec 11 10:34:28 PST 2015


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

--- Comment #2 from minfrin at sharp.fm ---
"None of it makes any sense" -> The example given doesn't make any practical
sense that will translate from what is written in those instructions to
something that is practically usable by an ordinary user of gstreamer.

Remember the examples and documentation are written for the benefit of people
who come to these elements for the very first time. These people didn't write
the code, nor are they expected to have to reverse engineer the code to figure
out what to do.

"Hooking up multiple streams to it is not much different than hooking up
multiple input streams to a muxer." -> this tells me that what I want to
achieve is possible, it also tells me that what I want to achieve is very close
to the docs, but doesn't actually tell me how to do it, and so is not useful.

The typical scenario is this:

- A video pipeline and an audio pipeline are processed in various ways
(decoded, resized, encoded) and then passed to mpegtsmux which muxes these
streams together, like this:

This is achieved as follows:

[video pipeline] ! mpegtsmux name=mux ! [hls processing pipeline]
[audio pipeline] ! mux.

Now I need to replace mpegtsmux with splitmuxsink, but I must also make
splitmuxsink targetable by the incoming audio and video pipelines muxed by
mpegtsmux, and there is no documentation on how to do that.

-- 
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