rtpsession: The stats min_interval is in seconds, not nanoseconds
authorSebastian Dröge <sebastian@centricular.com>
Mon, 4 May 2015 11:50:31 +0000 (13:50 +0200)
committerSebastian Dröge <sebastian@centricular.com>
Mon, 4 May 2015 12:12:07 +0000 (14:12 +0200)
We have to scale it to compare it against our clock times.

gst/rtpmanager/rtpsession.c

index 754837e..0acac15 100644 (file)
@@ -3562,7 +3562,7 @@ early:
     /* Apply the rules from RFC 4585 section 3.5.3 */
     if (stats->min_interval != 0 && !sess->first_rtcp) {
       GstClockTime T_rr_current_interval =
-          g_random_double_range (0.5, 1.5) * stats->min_interval;
+          g_random_double_range (0.5, 1.5) * stats->min_interval * GST_SECOND;
 
       /* This will caused the RTCP to be suppressed if no FB packets are added */
       if (sess->last_rtcp_send_time + T_rr_current_interval > new_send_time) {