GNOME Bugzilla – Bug 746542
rtpsession: Add property to set minimum time between regular RTCP and early RTCP
Last modified: 2018-11-03 14:59:07 UTC
Currently we allow to send an early RTCP packet immediately after the previous regular RTCP packet. This will be suboptimal if we have reasons to send another early RTCP packet soon afterwards... as that one would now have to wait until the next regular RTCP packet could be sent (and the next regular RTCP packet is now also delayed in the future because of the early one we just sent). It would be better in some situations if we set some minimum delay from the previous regular RTCP packet. That way we would allow for other feedback to be accumulated into the same early feedback RTCP packet more likely. The delay could either be specified in milliseconds, or as a relative value relative to the regular RTCP scheduling interval we currently decided to use. Not sure which one is better.
Is that different from the "rtcp-min-interval" property ?
Yes, rtcp-min-interval is for the minimum time between two regular RTCP packets.
-- 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/173.