After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759355 - splitmuxsink: documented pipeline example too simplistic to be useful
splitmuxsink: documented pipeline example too simplistic to be useful
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Mac OS
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-12-11 15:05 UTC by minfrin
Modified: 2018-11-03 15:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description minfrin 2015-12-11 15:05:39 UTC
In the docs at http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-splitmuxsink.html an example pipeline is given where a single file stream is split into multiple individual files.

This example is excessively simple, only in rare cases will you ever want to deal with streams containing just video and nothing else. In typical real world usage, streams consisting of video, audio and subtitles are processed, and there is no workable example to demonstrate how this is done.

Given that the splitmuxsink element wraps the muxer element, how do you target the muxer element with sources?

None of this makes any sense.
Comment 1 Tim-Philipp Müller 2015-12-11 18:23:20 UTC
It's an example. It's simplistic on purpose to distil the essence of what the element does and how it works. Hooking up multiple streams to it is not much different than hooking up multiple input streams to a muxer.

I'd be happy to add an example that involves both audio and video if you want to suggest an example pipeline or example scenario.


> None of this makes any sense.

I have no idea what that means. Could you elaborate please? Just because an example doesn't cover something you would like to see covered doesn't mean that nothing makes sense. It's also not really a particularly helpful thing to say.
Comment 2 minfrin 2015-12-11 18:34:28 UTC
"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.
Comment 3 GStreamer system administrator 2018-11-03 15:06:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/246.