, Stanley Biggs wrote:
> Hi Ross
>
> I have found what I believe to a bug in the latest live555 code and I also
> have a fix for the problem. We have tested this fix in our implementation
> and I would like to submit this fix for inclusion in your project.
>
> *PROBLEM D
{
//The following IF-statement was added by me (Stanley). As in the
case of the Sink Node above, we first check the value of EnableRTCPReports
before we do addRR().
*if (!fSource->**constAccessibleEnableRTCPReports()) return false;*
addRR();
}
return True;
}
...
Kind
Hi Ross
I have upgraded to the very latest Live555 server code and the new
Asynchronous Client Handler. We are using RTP-over-TCP. My server and
client work fine over a regular, low-latency connection, however, the
moment that latency increases somewhat, I am unable to get streaming
working. I get
Ross Finlayson writes:
>
> >Or perhaps the client code shouldn't be allowed to send RTCP
> >messages until after the PLAY command has been issued.
>
> You're right - it shouldn't. You've discovered a bug.
>
> >PS. I should probably note my code isn't like openRTSP in that it
> >doesn't do D
It seems that it may not be RR packets. It is some other RTCP or RTP packet
that the client sends.
On Tue, May 28, 2013 at 10:36 AM, Stanley Biggs wrote:
> Hi
>
> I am experiencing the same problem as described in this thread:
> http://lists.live555.com/pipermail/live-devel/2012-A
Hi
I am experiencing the same problem as described in this thread:
http://lists.live555.com/pipermail/live-devel/2012-August/015750.html and
answered here
http://lists.live555.com/pipermail/live-devel/2012-August/015755.html
Basically, we are implementing an RTSP client and server. However, when
