rtpjitterbuffer: remove the concept of "already-lost"
authorHavard Graff <havard.graff@gmail.com>
Thu, 19 Mar 2020 22:37:26 +0000 (23:37 +0100)
committerGStreamer Merge Bot <gitlab-merge-bot@gstreamer-foundation.org>
Fri, 20 Mar 2020 13:17:20 +0000 (13:17 +0000)
commitf1ff80ced0d14639beb3835970b62770e1eb74d1
tree9674b2400ee71bd15f9bae925002b2e710956ce9
parent5dacf366c078fdddc6bbb03f6c9ab9c6c946156f
rtpjitterbuffer: remove the concept of "already-lost"

This is a concept that only applies when a buffer arrives in the chain
function, and it has already been scheduled as part of a "multi"-lost
timer.

However, "multi"-lost timers are now a thing of the past, making this
whole concept superflous, and this buffer is now simply counted as "late",
having already been pushed out (albeit as a lost-event).
gst/rtpmanager/gstrtpjitterbuffer.c
tests/check/elements/rtpjitterbuffer.c