rtpjitterbuffer: Considers packets too late due to wraparound

Submitted by Sebastian Dröge @slomo

Link to original bug (#768715)

Description

https://cgit.freedesktop.org/gstreamer/gst-plugins-good/tree/gst/rtpmanager/gstrtpjitterbuffer.c?id=5328378132c7c100b8a17818862a3124affef1f8#n2829

This check will also trigger if more than 2**15 packets are queued up in the jitterbuffer, as the latest packet we received will then be considered as a wraparound close to the latest packet we popped.

The check will have to be made more correct somehow, or removed completely (why is it there at all?). It was added in commit eaa23fd4 in 2008 :)

We could probably just add the number of queued up packets to the last popped sequence number, and use that for comparison. It's not going to be 100% correct (there might be missing packets), but it should be far less than 2**15 (otherwise we would've reset already).

Any better ideas?

Version: 1.4.5