On Fri, 2010-09-17 at 13:42 +0200, Kocsis Tibor wrote:
> Hi,
>
> can somebody explain me what's this warning message means and what can
> i do to avoid it:
>
> rtpsource rtpsource.c:1391:rtp_source_get_new_sr: no clock-rate,
> cannot interpolate rtp time
This usually means that the application didn't tell gstrtpbin what the
clock-rate is for a source. You need to provide complete RTP caps on the
rtpbin or connect to the request-pt-map signal to provide this info to
gstrtpbin.
>
> It shows up when i connect an rtp sink to a running pipeline, and
> sometimes come these criticals with that:
You probably also add a new sender source, which explains the warning
above.
>
> (unknown:13994): GStreamer-CRITICAL **: gst_mini_object_unref:
> assertion `mini_object->refcount > 0' failed
> (unknown:13994): GStreamer-CRITICAL **: gst_mini_object_unref:
> assertion `mini_object->refcount > 0' failed
>
That suggests a serious refcounting bug somewhere. runnning the
application with --gst-fatal-warnings and inside gdb can give a
backtrace that can give a hint what's going on.
Wim
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Locked
