[gstreamer-bugs] [Bug 339356] GStreamer does not always provide feedback for bad pipelines

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=339356
 GStreamer | gstreamer (core) | Ver: 0.10.3


Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|gst-plugins-ugly            |gstreamer (core)




------- Comment #4 from Tim-Philipp Müller  2006-04-23 09:34 UTC -------
You always need a 'queue' element in each branch/stream after dvddemux (or any
demuxer really). If you don't have that, the pipeline might not be able to
preroll, ie. it hangs as you described. That's expected behaviour.

Of course GStreamer could theoretically detect things like you're asking, but
the benefit would be very small (IMHO) and it wouldn't be 100% correct from a
theoretical point of view (as it's not always clear with some type of streams
if there aren't more new pads going to be created later).

Generally, gst-launch is just a debug tool for developers who know what they're
doing. It does lots of things automagically in the background (like waiting for
a pad to be created etc.), but that 'magic' also has the side-effect of
stalling the pipeline if you're telling it to wait for something that won't
ever happen.

You can see what elements playbin/decodebin use if you pass the -v switch to
gst-launch.


-- 
Configure bugmail: http://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.