mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-05-02 22:44:47 +00:00
rtpsession: Deprecate rtcp-immediate-feedback-threshold property
It had no effect since quite some time and also is not needed in general, especially not to switch between immediate feedback mode and early feedback mode. The latest understanding of the RFC is that from the endpoint point of view, both modes are exactly the same. RTCP is only allowed to use the bandwidth as given by the RFC constraints, as such it is only ever possible to schedule a RTCP packet early but it's against the RFC to schedule more RTCP packets. The difference between immediate feedback mode and early feedback mode is that the former guarantees that an RTCP packet can be sent for every event "immediately", which means that the bandwidth calculations from the RFC have resulted in an RTCP scheduling interval that is small enough. Early feedback mode on the other hand means that we can schedule some packets early to make that happen, but it's not guaranteed at all that it's possible to schedule an RTCP packet per event (i.e. they need to be accumulated or dropped).
This commit is contained in:
parent
b07b7736b3
commit
e4ed852041
1 changed files with 2 additions and 2 deletions
|
@ -450,9 +450,9 @@ rtp_session_class_init (RTPSessionClass * klass)
|
|||
g_param_spec_uint ("rtcp-immediate-feedback-threshold",
|
||||
"RTCP Immediate Feedback threshold",
|
||||
"The maximum number of members of a RTP session for which immediate"
|
||||
" feedback is used",
|
||||
" feedback is used (DEPRECATED: has no effect and is not needed)",
|
||||
0, G_MAXUINT, DEFAULT_RTCP_IMMEDIATE_FEEDBACK_THRESHOLD,
|
||||
G_PARAM_READWRITE | G_PARAM_STATIC_STRINGS));
|
||||
G_PARAM_READWRITE | G_PARAM_STATIC_STRINGS | G_PARAM_DEPRECATED));
|
||||
|
||||
g_object_class_install_property (gobject_class, PROP_PROBATION,
|
||||
g_param_spec_uint ("probation", "Number of probations",
|
||||
|
|
Loading…
Reference in a new issue