After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 763373 - GstRtpBin and RTPSession ssrc-related signals should have ::ssrc detail
GstRtpBin and RTPSession ssrc-related signals should have ::ssrc detail
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-03-09 14:04 UTC by Nirbheek Chauhan
Modified: 2018-11-03 15:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nirbheek Chauhan 2016-03-09 14:04:20 UTC
For signals such as on-ssrc-active, on-ssrc-sdes, on-timeout, and many more, a common pattern is to only check when a specific SSRC is active, has timed out, etc. It would be quite useful to be able to pre-filter by specifying the SSRC in the signal detail itself.

So, for instance, you'd do:

 void
 on_new_ssrc (GstElement * rtpbin, guint session, guint ssrc, ...)
 {
   gchar *detailed_signal = g_strdup_printf ("on-ssrc-active::%u", ssrc);
   g_signal_connect (rtpbin, detailed_signal, on_our_ssrc_active, NULL);
 }

 g_signal_connect (rtpbin, "on-new-ssrc", on_new_ssrc, NULL);

Instead of having a filter inside on_our_ssrc_active() which would have to check whether we're handling that specific SSRC.
Comment 1 GStreamer system administrator 2018-11-03 15:08:12 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/262.