[Bug 723554] New: request for "stats" property of "payX" pipeline element may raise GLib warning

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=723554
  GStreamer | gst-rtsp-server | git

           Summary: request for "stats" property of "payX" pipeline
                    element may raise GLib warning
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-rtsp-server
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: me at andrey-utkin.pp.ua
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


In gst_rtsp_stream_get_rtpinfo () at rtsp-stream.c:1890 there is a request
g_object_get (..., "stats", ...).
The object on which this request is done is a GstElement in a pipeline given to
gst_rtsp_media_factory_set_launch (), named payX and intended for pulling data
from it to send to RTSP client. But there's no requirement declared that payX
must be derived from GstRtpBasePayload class, which implements "stats"
property. For example, in my application a pipeline provided to
gst_rtsp_media_factory_set_launch () looks like this

( appsrc name=%s ! capsfilter name=capsfilter_%s ! identity name=pay%d )

When it is constructed, i save references to appsrc and capsfilter objects to
be able to push data there and set actual caps. And this request for "stats"
property makes app stop when G_DEBUG=all is set, which i use for debug
purposes, with such message:

GLib-GObject-WARNING **: g_object_get_valist: object class 'GstIdentity' has no
property named 'stats'

So could this be somehow enhanced so that property is not requested when it is
not present? Or to make it so that ...get_rtpinfo () is not executed at all?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.