RTSP server problems with uvch264src H/W+ encoded H.264 output

krakorar rob.krakora at messagenetsystems.com
Mon Apr 29 05:56:45 PDT 2013


Caps negotiation fails on this pipeline under GStreamer 0.10...


GST_DEBUG=*v4l2*:5,*uvch264*:5 GST_DEBUG_NO_COLOR=1 gst-launch-0.10
uvch264_src device=/dev/video0 name=src auto-start=true src.vidsrc !
video/x-h264,width=800,height=600,framerate=30/1 ! queue ! fakesink
src.vfsrc ! video/x-raw,width=432,height=240,framerate=30/1 ! xvimagesink


...under GStreamer 1.0 this pipeline runs until the APP4 marker is
encountered at the end of a buffer with no more data available to parse...


GST_DEBUG=*v4l2*:5,*uvch264*:5 GST_DEBUG_NO_COLOR=1 gst-launch-1.0
uvch264src device=/dev/video0 name=src auto-start=true src.vidsrc !
video/x-h264,width=800,height=600,framerate=30/1 ! queue ! fakesink
src.vfsrc ! video/x-raw,width=432,height=240,framerate=30/1 ! xvimagesink

It looks like the difference is that in the GStreamer 1.0 pipeline H.264 and
RAW data are multiplexed within the MJPEG container.




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/RTSP-server-problems-with-uvch264src-H-W-encoded-H-264-output-tp4659582p4659732.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list