gstreamer-devel Digest, Vol 39, Issue 61
sebastian at centricular.com
Wed Apr 23 00:48:17 PDT 2014
On Di, 2014-04-22 at 17:26 +0200, René Calles wrote:
> thank you for your fast response. I just corrected the command line to:
> GST_DEBUG=3 gst-launch-1.0 -v \
> filesrc location="MyFile.mp4" ! queue ! qtdemux name="dmux" \
> flvmux name="mux" streamable="true" ! queue ! rtmpsink location="rtmp://10.11.40.28/live/test live=1" \
> dmux. ! multiqueue name="mq" ! 'video/x-h264, width=1280, height=720, framerate=25/1' ! h264parse ! mux. \
> dmux. ! mq. mq. ! "audio/mpeg,mpegversion=4" ! aacparse ! mux.
> Adding aacparse / h264parse in front of the muxer did not help.
So, how exactly does it fail? :)
If you look at the debug logs (try GST_DEBUG=6), do you see that all
multiqueue pads are actually linked? Does it work better if you use
normal queues instead of a multiqueue? Does it work better if you
specify the exact pad names instead of letting gst-launch figure that
out? There is a bug with gst-launch that will cause linking to fail in a
few cases because it's choosing the wrong pads to link if you don't
specify them yourself with element_name.pad_name.
Sebastian Dröge, Centricular Ltd - http://www.centricular.com
Expertise, Straight from the Source
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 949 bytes
Desc: This is a digitally signed message part
More information about the gstreamer-devel