[Live-devel] RTP/H264 low latency streaming + source, change

Ross Finlayson finlayson at live555.com
Fri Jun 25 08:05:20 PDT 2010


>>I suspect that your problem is caused by the fact that each sending
>>camera (server) necessarily uses a different RTP timestamp base, and
>>so when you switch to receiving from a new camera, the received
>>data's presentation time will briefly be inaccurate, until you
>>receive a new RTCP "SR" packet from the new source.  (I'm assuming
>>that your servers send RTCP as well as RTP; because you're using our
>>software, that should be the case.)
>>
>>One way to reduce this problem is to increase the average RTCP
>>sending frequency, which you can do by increasing the "totSessionBW"
>>parameter that you pass to "RTCPInstance::createNew()".  (This
>>parameter is intended to represent the stream's bitrate in kbps.  It
>>is used - by the RTCP code - to figure out how often to send RTCP
>>packets.)
>
>Oups...
>I have not set up a RTCP flow. Just RTP.
>The fact is that in my case the streaming client cannot reach the 
>streaming server (simplex communication). So I guessed RTCP should 
>not be used.
>
>Thank-you for your advice, I am going to try playing with RTCP (even 
>in simplex session) and timestamps.

Please, everyone - stop trying to 'second guess' the RTP/RTCP 
standard.  RTCP is *not* optional.
-- 

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/


More information about the live-devel mailing list