rtpsession: Send as many nack seqnum as possible
authorNicolas Dufresne <nicolas.dufresne@collabora.com>
Mon, 25 Mar 2019 17:42:25 +0000 (13:42 -0400)
committerNicolas Dufresne <nicolas@ndufresne.ca>
Fri, 5 Apr 2019 14:53:09 +0000 (14:53 +0000)
commit6bb53e75fb36637131bec823d950ca690e666b9e
tree0af1097abb420bda7972e1dda4f149b28f6f3da3
parent74a74bfc997543069527642e4805d9e45a3098df
rtpsession: Send as many nack seqnum as possible

In order to do that, we now split the nacks registration from the actual
FB nack packet construction. We then try and add as many FB Nacks as
possible into the active packets and leave the remaining seqnums in the
RTPSource. In order to avoid sending outdated NACK later on, we save the
seqnum calculated deadline and cleanup the outdated seqnums before the
next RTCP send.

Fixes #583
gst/rtpmanager/rtpsession.c
gst/rtpmanager/rtpsource.c
gst/rtpmanager/rtpsource.h