caps problem in using gstreamer

[Sebastian Dröge]

On Do, 2013-10-17 at 13:42 +0530, M Suneel Kumar wrote:
> Hi
> 
> 
> I am sending the video packets to udpsrc and also decoding on the server
> side both audio and video.
> 
> This is the pipe line i am using on the server side.*
> *
> *Server pipe line:*
> gst-launch-0.10 -v filesrc location=../test.mp4 ! qtdemux name=demux demux.
> ! tee name=videoTee videoTee. ! queue ! rtph264pay ! udpsink  port=5000
> videoTee. ! queue ! ffdec_h264 !  ffmpegcolorspace ! autovideosink demux. !
> decodebin ! audioconvert ! audioresample ! autoaudiosink
> 
> 
> *Receiver side pipe line:*
> gst-launch-0.10 udpsrc port=5000 caps = "application/x-rtp,
> media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264,
> sprop-parameter-sets=(string)\"Z2QAH6y0AoAt0IAAAAMAgAAAGQeMGVA\\=\\,aO48sA\\=\\=\",
> payload=(int)96, ssrc=(uint)2425249179, clock-base=(uint)921766476,
> seqnum-base=(uint)49848" ! rtph264depay ! ffdec_h264 ! autovideosink
> 
> on the client pipe line i am providing the caps information that i got from
> the server.
> 
> 
> This set up is working fine . But when change the source file from
>  location=../test.mp4 to some other vector i have again feed the new caps
> to the client.
> 
> How can we do this using gstreamer plugins only..

The RTP/h264 sprop-parameter-sets caps field is specific for that
specific h264 stream. You have to provide it to all receivers (e.g. via
RTSP, check gst-rtsp-server).

You can also omit that field and then it should work even if you switch
streams, but it might take a bit longer for the stream to start on your
clients then (as the receiver has to wait until that data, the h264
SPS/PPS, is sent inside the stream).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20131017/ed988083/attachment.pgp>