weird behaviour of rtsp element. Possible bug? Follow up (yes, it is a bug).

Tim-Philipp Müller t.i.m at
Sat Dec 22 02:33:38 PST 2012

On Sat, 2012-12-22 at 00:19 +0200, Guetcho Guetchev wrote:


> Today I saw that this assertion: GStreamer-CRITICAL **: gst_segment_to_running_time: assertion `segment->format == format' failed
> remains valid even with the classic usage of get-launch (Gstreamer 1.0.4): 
> gst-launch-1.0 rtspsrc location=rtsp:// ! capsfilter caps=application/x-rtp,media=video,payload=96,clock-rate=90000,encoding-name=H264 ! rtph264depay ! h264parse ! capsfilter caps=video/x-h264,alignment=au ! avdec_h264 ! filesink location=./
> Just before that call you need to start the executable built from that git repository:
> You can initiate the stream by using the command line:
> ./gsttest <file> --no-reception
> Where <file> is the bunzip2-ed file 1.move.bz2 from the same repository.
> I believe this is a bug in Gstreamer. 

Yes, I'm quite certain it's a bug. (Did we talk about this on IRC a few
days ago?)

As such, it's best dealt with in bugzilla. Have you filed a bug yet?


More information about the gstreamer-devel mailing list