[gst-devel] spider related discussion
in7y118 at public.uni-hamburg.de
in7y118 at public.uni-hamburg.de
Fri Feb 20 05:31:02 CET 2004
Quoting Stefan Kost <kost at imn.htwk-leipzig.de>:
> just forgot the NULL here, in the code it is null terminated. Updated from
> CVS
> and now I just get
>
> (process:9627): GStreamer-WARNING **: internal error: push on pad
> sink_ident:sink but it has no chainhandler
>
-ENOCLUE
> > debugging categories probably have names starting with "spider".
> > So something like --gst-debug=spider*:5 should give you a good output.
> >
> Well that helps. Still spider is not reporting what it plugs in :-(
>
There's a
GST_DEBUG ("Adding element %s of type %s and syncing state with autoplugger",
GST_ELEMENT_NAME (element), GST_PLUGIN_FEATURE_NAME (plugpath->data));
in the code. So it's supposed to tell you what it does.
(Anyone noticing I can't test myself atm? ;))
> I'll have a look at it. I was only aware of the gstreamer, gst-plugins and
> gst-edit modules (there is no overview of the available modules on the
> homepage).
>
That's because we only market the "finished" stuff. All of the other code in
the other modules ranges from bitrotten and ages old to current, from ideas to
proof-of-concept, from free to not free and from interesting to boring.
gst-monkeymedia, gst-shorten, gst-recorder, gst-tv, gst-overlay, gst-autoplug
etc. are all examples of code that is not quite finished for one reason or
another.
More information about the gstreamer-devel
mailing list