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
..
check	rtpjitterbuffer: Don't request rtx if 'now' is past retry period	2016-09-14 19:37:50 -04:00
examples	tests/examples: #define GDK_DISABLE_DEPRECATION_WARNINGS	2016-09-01 10:59:51 +03:00
files	tests: add unit test for JPEG-2000 rtp payloader leak	2016-05-27 12:58:37 +01:00
icles	gstreamer: good: tests: Fix memory leaks when context parse fails.	2015-10-02 17:35:10 +03:00
Makefile.am	tests: don't build examples if --disable-examples was passed to configure	2009-05-05 13:23:45 +01:00
meson.build	Add support for Meson as alternative/parallel build system	2016-08-20 11:21:12 +01:00