Stian Selnes 2eb7383816 rtpjitterbuffer: Don't request rtx if 'now' is past retry period ... There is no need to schedule another EXPECTED timer if we're already past the retry period. Under normal operation this won't happen, but if there are more timers than the jitterbuffer is able to process in real-time, scheduling more timers will just make the situation worse. Instead, consider this packet as lost and move on. This scenario can occur with high loss rate, low rtt and high configured latency. https://bugzilla.gnome.org/show_bug.cgi?id=769768		2016-09-14 19:37:50 -04:00
..
elements	rtpjitterbuffer: Don't request rtx if 'now' is past retry period	2016-09-14 19:37:50 -04:00
generic	check: Rename states unit test	2015-08-14 11:13:01 +02:00
pipelines	tests: fix bus leaks	2016-07-18 10:53:19 +01:00
.gitignore	tests: ignore sub-directory with orc tests	2010-06-17 16:41:56 +01:00
gst-plugins-good.supp	suppressions: ignore an apparent bug in strtod	2015-04-15 18:00:00 +01:00
Makefile.am	tests: use GST_NET_LIBS instead of hardcoded -lgstnet	2016-08-26 21:22:16 +02:00
meson.build	Add support for Meson as alternative/parallel build system	2016-08-20 11:21:12 +01:00