Re: rtspsrc is not compatible with rtmpsink
hlasuj at atlas.sk
hlasuj at atlas.sk
Mon Apr 27 02:50:56 PDT 2015
Dear Baby Octopus,
Thank you for your interest. I also think there is a problem with tmestamps.
If I run any of these two pipes (the second assumes that rtsp is redirected to tcp by another gstreamer pipe)
gst-launch-1.0 -v --gst-debug=identity:8 rtspsrc location=rtsp://192.168.1.100/stream ! rtph264depay ! h264parse ! queue ! identity check-imperfect-timestamp=true check-imperfect-offset=true ! fakesink
gst-launch-1.0 -v --gst-debug=identity:8 tcpclientsrc host=127.0.0.1 port=5010 do-timestamp=true ! matroskademux ! h264parse ! queue ! identity check-imperfect-timestamp=true check-imperfect-offset=true ! fakesink
I allways get plenty of errors like these. There are roughly 30 of them per second.
1:gst_identity_check_imperfect_timestamp:<identity0> can't check data-contiguity, no offset_end was set on previous buffer
0:00:00.765881126 14103 0x93b3290 DEBUG identity gstidentity.c:455:gst_identity_check_imperfect_offset:<identity0> can't check offset contiguity, no offset and/or offset_end were set on previous buffer
0:00:00.804650999 14103 0x93b3290 DEBUG identity gstidentity.c:411:gst_identity_check_imperfect_timestamp:<identity0> can't check data-contiguity, no offset_end was set on previous buffer
0:00:00.804701247 14103 0x93b3290 DEBUG identity gstidentity.c:455:gst_identity_check_imperfect_offset:<identity0> can't check offset contiguity, no offset and/or offset_end were set on previous buffer
0:00:00.834635582 14103 0x93b3290 DEBUG identity gstidentity.c:411:gst_identity_check_imperfect_timestamp:<identity0> can't check data-contiguity, no offset_end was set on previous buffer
0:00:00.834686384 14103 0x93b3290 DEBUG identity gstidentity.c:455:gst_identity_check_imperfect_offset:<identity0> can't check offset contiguity, no offset and/or offset_end were set on previous buffer
0:00:00.865599646 14103 0x93b3290 DEBUG identity gstidentity.c:411:gst_identity_check_imperfect_timestamp:<identity0> can't check data-contiguity, no offset_end was set on previous buffer
0:00:00.865650187 14103 0x93b3290 DEBUG
Best regards, Hugo.
______________________________________________________________
> Od: Baby Octopus <jagadishkamathk at gmail.com>
> Komu: <gstreamer-devel at lists.freedesktop.org>
> Dátum: 27.04.2015 06:59
> Predmet: Re: rtspsrc is not compatible with rtmpsink
>
You are getting error 104(connection reset) and 32(broken pipe). Both
strongly point out to timestamp error, going by my past experience
When you are doing this through tcp internal pipe and matroskamux, I guess
the timestamp is getting corrected(Just assuming)
Put fakesink in both audio and video branch and check the timestamps
--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/rtspsrc-is-not-compatible-with-rtmpsink-tp4671698p4671707.html <http://gstreamer-devel.966125.n4.nabble.com/rtspsrc-is-not-compatible-with-rtmpsink-tp4671698p4671707.html>
Sent from the GStreamer-devel mailing list archive at Nabble.com.
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel <http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20150427/7ae6b58b/attachment-0001.html>
More information about the gstreamer-devel
mailing list