[gstreamer-bugs] [Bug 566881] New: [GstIndex] support/caching in GstBin
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Wed Jan 7 02:23:14 PST 2009
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=566881
GStreamer | gstreamer (core) | Ver: HEAD CVS
Summary: [GstIndex] support/caching in GstBin
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gstreamer (core)
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: bilboed at gmail.com
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
Currently GstBin implements index support in a very 'simple' way, i.e. it just
forwards _set_index()/_get_index() on its *current* children.
What it should ideally do is the following:
* When _set_index() is called:
* cache internally (with refcount) the new index
* call _set_index on all current children (current behaviour)
* When a new child is added to a bin:
* call _set_index on the new child with the currently cached index
* When _get_index() is called:
* If we have a cached index, return that one
* If not, call _get_index() on each child until we get one and return that
one.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=566881.
More information about the Gstreamer-bugs
mailing list