GNOME Bugzilla – Bug 720371
rtpbin: Impossible to set jitterbuffer rtx-* properties when using rtpbin
Last modified: 2013-12-30 15:54:13 UTC
It's currently not possible to set the rtx-* properties of a jitterbuffer when it's used inside rtpbin. This is trickier than the "latency" as these could be different for each session I believe. Maybe we need an API to g_signal_emit_by_name(rtpbin, "set-jitterbuffer-property", guint session_id, char * property_name, gint value) with the associated g_signal_emit_by_name(rtpbin, "get-jitterbuffer-property", guint session_id, gchar * property_name, gint *value); We could also replace the gint by a GValue, but then it gets uglier to use because of GValue.
Or API to get the session instances? Or set-rtx-* (session_id, value)?
The problem with that approach is that the jitterbuffer is not in the session object and there are multiple jitterbuffer instances per session, one per received ssrc.
How about a signal when a new jitterbuffer is made so that you can configure it? It's a bit tedious to keep on proxying those properties and it doesn't solve the issue when you want different values per jitterbuffer.
commit 5a2bc1405eff43493682721ceb8cb8bf94806242 Author: Wim Taymans <wtaymans@redhat.com> Date: Mon Dec 30 16:52:28 2013 +0100 rtpbin: add signal for new jitterbuffer Emit a signal when a new jitterbuffer is created so that the app can have a chance to configure it.