rtspsrc: don't emit ugly warnings with older rtpjitterbuffer versions

The on-npt-stop signals was added only recently to rtpjitterbuffer in
-bad, so check if the signal exists before g_signal_connect()ing to
it, to avoid warnings.
This commit is contained in:
Tim-Philipp Müller 2009-04-01 12:26:12 +01:00
parent b037369d5b
commit cb15d09c4a

View file

@ -1948,8 +1948,13 @@ gst_rtspsrc_stream_configure_manager (GstRTSPSrc * src, GstRTSPStream * stream,
src);
g_signal_connect (src->session, "on-timeout", (GCallback) on_timeout,
src);
g_signal_connect (src->session, "on-npt-stop", (GCallback) on_npt_stop,
src);
/* FIXME: remove this once the rtpjitterbuffer is in -good */
if (g_signal_lookup ("on-npt-stop", G_OBJECT_TYPE (src->session)) != 0) {
g_signal_connect (src->session, "on-npt-stop", (GCallback) on_npt_stop,
src);
} else {
GST_INFO_OBJECT (src, "skipping on-npt-stop handling, not implemented");
}
}
/* we stream directly to the manager, get some pads. Each RTSP stream goes