[gstreamer-bugs] [Bug 598533] Get stream topology of a bin/pipeline

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=598533
  GStreamer | gst-plugins-base | git

--- Comment #11 from Wim Taymans <wim.taymans at gmail.com> 2009-10-28 12:47:09 UTC ---
To me it sounds like (at the lowest level) you want an API to walk the pipeline
graph so that you can collect information about each element/pad you encounter.

This is all pretty straightforward when using the internally linked pads of an
element. Problems arrise when you come to an element that splits or merges
'streams' because then you have to decide which path to follow or that streams
end.

The proposed API seems to implement a subset of this functionality. It only
provides the caps (no elements, no pads). This might be enough for your current
use case but I don't think we can call this a generic API. 

I think you should focus on making decodebin2 provide you with the info you
need right now instead of trying to solve this problem generically. I believe
that's why I was wondereding about but not too opposed to the message that
decodebin2 now posts.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.