[Bug 774321] New: GstStream: need API to deactivate streams
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Sat Nov 12 14:22:43 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=774321
Bug ID: 774321
Summary: GstStream: need API to deactivate streams
Classification: Platform
Product: GStreamer
Version: unspecified
OS: Linux
Status: NEW
Severity: enhancement
Priority: Normal
Component: gstreamer (core)
Assignee: gstreamer-bugs at lists.freedesktop.org
Reporter: t.i.m at zen.co.uk
QA Contact: gstreamer-bugs at lists.freedesktop.org
CC: arun at arunraghavan.net, bcxa.sz at gmail.com,
bilboed at bilboed.com, bugzilla at hadess.net,
ensonic at sonicpulse.de, lrn1986 at gmail.com,
michael.coracin at st.com, mili.gauri at st.com,
mnauw at users.sourceforge.net, slomo at coaxion.net,
suresh.shukla at st.com, t.i.m at zen.co.uk,
vincent.penquerch at collabora.co.uk
GNOME version: ---
+++ 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.
--
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