[Live-devel] QuickTime Streaming
Dixon Siu
dixonsiu at mediaglue.co.jp
Thu Jun 10 12:07:35 PDT 2004
Ross,
You were right. The issue is not in OnExpire(), it gets the bandwidth
correctly. The issue is in rtcp_from_spec.c. This interval is set like this:
double const RTCP_MIN_TIME = 5.;
...
t = avg_rtcp_size * n / rtcp_bw;
if (t < rtcp_min_time) t = rtcp_min_time;
So if I REALLY want to have a faster interval for my application. Lets say
0.1 seconds. Then can I change the RTCP_MIN_TIME to 0.1? The reason is that
I need to estimate the network bandwidth using RTTs and dynamically adjust
the sending bitrate. Therefore, I don't want to lose my data within that 5
seconds interval.
Dixon
> -----Original Message-----
> From: live-devel-bounces at ns.live.com
> [mailto:live-devel-bounces at ns.live.com]On Behalf Of Ross Finlayson
> Sent: Thursday, June 10, 2004 10:32 AM
> To: LIVE.COM Streaming Media - development & use
> Subject: RE: [Live-devel] QuickTime Streaming
>
>
>
> >It is not relevant to this issue. But when I use QuickTime as
> the client, it
> >always return negative number for the RTT.
>
> This issue was resolved in release 2004.04.27; you should have upgraded
> since then! In more recent releases, the delay reported by
> "RTPTransmissionStats::roundTripDelay()" will never be negative.
>
> >Another question is that I tried to manipulate the session bandwidth when
> >creating an RTCP instance. It seems that the interval of the SR
> or RR does
> >not change according to the session bandwidth.
>
> It should. Note the use of the "rtcp_bw" parameter in the "OnExpire()"
> function in "rtcp_from_spec.c" (and how this parameter is set in
> "RTCPInstance::onExpire1()").
>
>
> Ross Finlayson
> LIVE.COM
> <http://www.live.com/>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live.com
> http://lists.live.com/mailman/listinfo/live-devel
>
>
> __________ NOD32 1.782 (20040608) Information __________
>
> This message was checked by NOD32 Antivirus System.
> http://www.nod32.com
>
>
More information about the live-devel
mailing list