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

yusuf.husainy yusuf.husainy at gmail.com
Tue Apr 23 00:46:32 PDT 2013

Hi Robert,

I have used the same pipeline as you have mentioned. This pipeline cannot be
launched via gst-launch-1.0 on command line.

It can run only through the server. Also as KaKaRoTo's blog says here:
we cannot leave the vfsrc pad of uvch264src(without the '_', as i am using
gst-1.0) unlinked. The pipeline gives an unlinked error and stops. I have
attached vfsrc to a local xvimagesink and vidsrc to the rtsp pipeline. So
the log earlier is the most correct(I presume). Also the pt of rtph264pay is
pt=96 in my server pipeline.

My server pipeline:
uvch264src device=/dev/video0 name=src auto-start=true iframe-period=1000
src.vidsrc ! queue ! video/x-h264,width-1920,height=1080,framerate=30/1 !
h264parse ! rtph264pay pt=96 name=pay0 src.vfsrc ! queue !
video/x-raw,width=432,height=240,framerate=30/1 ! xvimagesink

Updated log for above pipeline: http://pastebin.com/A5bhfHRz

My client pipeline:
gst-launch -v rtspsrc location=rtsp:// latency=0 !
rtph264depay ! ffdec_h264 ! xvimagesink sync=0

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

More information about the gstreamer-devel mailing list