Here's what I got when using --gst-debug: .... 0:00:40.041460639 29100 0x91ac738 DEBUG rtph264depay gstrtph264depay.c:560:gst_rtp_h264_depay_process:<rtph264depay0> queueing 1386 bytes 0:00:40.041587089 29100 0x91ac738 DEBUG rtph264depay gstrtph264depay.c:404:gst_rtp_h264_depay_process:<rtph264depay0> receiving 1132 bytes 0:00:40.041702807 29100 0x91ac738 DEBUG rtph264depay gstrtph264depay.c:421:gst_rtp_h264_depay_process:<rtph264depay0> NRI 2, Type 28 0:00:40.041814445 29100 0x91ac738 DEBUG rtph264depay gstrtph264depay.c:519:gst_rtp_h264_depay_process:<rtph264depay0> S 0, E 1 0:00:40.041929402 29100 0x91ac738 DEBUG rtph264depay gstrtph264depay.c:560:gst_rtp_h264_depay_process:<rtph264depay0> queueing 1130 bytes 0:00:40.042042693 29100 0x91ac738 DEBUG rtph264depay gstrtph264depay.c:568:gst_rtp_h264_depay_process:<rtph264depay0> output 1130 bytes 0:00:40.042204307 29100 0x91ac738 DEBUG rtph264depay gstrtph264depay.c:404:gst_rtp_h264_depay_process:<rtph264depay0> receiving 2 bytes 0:00:40.042320160 29100 0x91ac738 DEBUG rtph264depay gstrtph264depay.c:421:gst_rtp_h264_depay_process:<rtph264depay0> NRI 0, Type 9 .... I haven't found anything like 'codec_data buffer is pushed'. I had tried to set caps like this: gst-launch rtsp://localhost:8554/h264 ! rtph264depay ! video/x-h264 ! ffdec_h264 ! ffmpegcolorspace ! autovideosink but still got this message: ... 0:00:03.521963200 29480 0x94ef290 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one ... Tried to set byte-stream=false to rtph264depay, I got this message: 0:00:03.536385694 29480 0x94ef290 ERROR ffmpeg :0:: no frame! So do you know if is there anything wrong ? <div class="gmail_quote">2009/10/13 Arnout Vandecappelle <<a href="mailto:arnout@mind.be">arnout@mind.be</a>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Tuesday 13 Oct 2009 10:03:44 Thành Trung Nguyễn wrote: > Here's what I got from gst-launch -v on rtph264depay elements: > > /GstPipeline:pipeline0/GstRtpH264Depay:rtph264depay0.GstPad:src: caps = > video/x-h264 > > /GstPipeline:pipeline0/GstRtpH264Depay:rtph264depay0.GstPad:sink: caps = > application/x-rtp, media=(string)video, payload=(int)96, > clock-rate=(int)90000, encoding-name=(string)H264, > profile-level-id=(string)4d401f, > sprop-parameter-sets=(string)\"Z01AH5JUAoAt2AiAAAADAIAAAB5HjBlQ\\,aO48gA\\= > \\=\", a-tool=(string)GStreamer, a-type=(string)broadcast, > clock-base=(guint)2373374152, seqnum-base=(guint)13660, > npt-start=(guint64)0, play-speed=(double)1, play-scale=(double)1 > > I'm not sure but I think video/x-h264 is the codec data you said, isn't it > ? </div> The 'sprop-parameter-sets' is the config string I mentioned. The 'video/x- h264' should have codec data as a parameter, or it may send the codec-data as an in-stream buffer (and now I seem to remember that's actually the default). But since the sprop-parameter-sets are there, the codec data will be there as well. Run with --gst-debug=rtph264depay:5,ffdec:3 to get a bit (well, actually a lot) more detail. If that mentions that the codec_data buffer is pushed, then something else is wrong... Maybe the problem is that the codec data gets discarded again because the discontinuity that comes from the errors of your first two frames. That is solved by setting it as caps instead of pushing it as a buffer. Add the 'byte-stream=false' property to rtph264depay. Regards, Arnout PS Please send replies to the list, other people may benefit from these messages. <div><div></div><div class="h5"> > > 2009/10/13 Arnout Vandecappelle <<a href="mailto:arnout@mind.be">arnout@mind.be</a>> > > > On Monday 12 Oct 2009 13:18:01 Thành Trung Nguyễn wrote: > > > Hi, > > > > > > I'm working on a project that use gst-rtsp-server as the streaming > > > server and got the following message on the client with h264 and mpeg4 > > > video format: > > > > > > ffmpeg :0:: warning: first frame is no keyframe > > > ffmpeg :0:: Missing reference picture > > > ffmpeg :0:: number of reference frames exceeds max (probably corrupt > > > input), discarding one > > > ffmpeg :0:: non-existing PPS referenced > > > ffmpeg :0:: sps_id out of range > > > > This sounds like you're missing codec_data for your decoder. Can you > > check > > on your client which caps are set on the elements? You typically have a > > config string on rtph264depay's sink pad and a codec-data buffer on its > > src pad. > > > > If your rtsp server is not sending out the codec data (e.g. because you > > start > > in the middle of a stream), then you have a problem :-) > > > > Regards, > > Arnout > > > > -- > > Arnout Vandecappelle arnout at mind be > > Senior Embedded Software Architect +32-16-286540 > > Essensium/Mind <a href="http://www.mind.be" target="_blank">http://www.mind.be</a> > > G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR > > Leuven > > LinkedIn profile: <a href="http://www.linkedin.com/in/arnoutvandecappelle" target="_blank">http://www.linkedin.com/in/arnoutvandecappelle</a> > > GPG fingerprint: D206 D44B 5155 DF98 550D 3F2A 2213 88AA A1C7 C933 > -- Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286540 Essensium/Mind <a href="http://www.mind.be" target="_blank">http://www.mind.be</a> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: <a href="http://www.linkedin.com/in/arnoutvandecappelle" target="_blank">http://www.linkedin.com/in/arnoutvandecappelle</a> GPG fingerprint: D206 D44B 5155 DF98 550D 3F2A 2213 88AA A1C7 C933 </div></div></blockquote></div> -- Cheers ! trungnt