[gst-devel] Why does this working gst-launch pipeline not work when compiled?
wmiller at sdr.com
Thu Apr 22 19:13:08 CEST 2010
Tim-Phillip Muller replied:
> That sounds like you already know that that's not going to work ;-)
> multipartdemux has sometimes pads, and matroskamux has request pads, so
> you can't just link them all from the start (you did check the return
> value of _link_many()?)
I finally got my head around what is going on here, mostly. But my solution
is still not quite right. I get an output file, but it won't "play".
I want to turn this gst-launch pipeline into C code.
gst-Launch souphttpsrc location="my_url" ! multipartdemux ! matroskamux
! filesink location="my_file"
I have all the elements built and added to the pipeline. The souphttpsrc is
linked to the multipartdemux.
The matroskamux is linked to the filesink. All return codes are ok.
I have a signal connected to the demuxer tied to a callback function. The
callback is being called.
In the callback I have tried just hooking the pad from the src (demuxer
sometimes pad) to a compatible on-requestsink pad in the muxer using the src
pad's default caps I have also tried setting the src pad's caps to
image/jpeg then getting the compatible pad. Both configs will produce am
output file. but neither file can be played back using this playback pipe:
gst-launch filesrec ! matroskademux ! jpegdec ! ffmpegcolorspace !
How should I configure my caps and/or what pad should I be asking for?
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Why-does-this-working-gst-launch-pipeline-not-work-when-compiled-tp1837570p2020856.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
More information about the gstreamer-devel