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 774321 - GstStream: need API to deactivate streams
GstStream: need API to deactivate streams
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
unspecified
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-11-12 14:22 UTC by Tim-Philipp Müller
Modified: 2018-11-03 12:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim-Philipp Müller 2016-11-12 14:22:43 UTC
+++ This bug was initially created as a clone of Bug #646638 +++

We now have new API to select and thus also deselect streams in form of the SELECT_STREAMS event.

We also want API that can be used to deactivate streams, which goes one step further, and would instruct the demuxer to not even read/demux/expose it.

This could be used for example in a thumbnailing application to deactivate decoding of all audio streams, or in GES which uses separate sources/decodebins for audio/video from the same input file.

Question is if we only want to be able to deactivate streams, or if we also want to allow re-activating them again later at runtime.
Comment 1 GStreamer system administrator 2018-11-03 12:38:07 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/gstreamer/issues/204.