> I’m pretty sure changing the clock isn’t the solution but maybe it can give a 
> clue on where the issue lies. 

Don't worry; I know where the issue lies (it's a bug/deficiency in the LIVE555 
RTSP proxying code; see below).


> After investigating this second point, I found an issue with my timestamps.  
> My camera’s date is somewhere in 2003 making synchronized timestamps way back 
> in the past.  If I correct the camera’s date and time it fixes the issue I 
> observed making my module and the proxy server working.  This raises a new 
> question: Is it possible to overcome the case where the sender has an 
> incorrect date and time?

Note that the sender's date and time are not really 'incorrect'.  It's 
perfectly OK for them to be way in the past - or way in the future - as long as 
the audio and video timestamps are synchronized between themselves.  However, 
there is a bug in our RTSP proxying code that prevents our proxy server from 
*sending* correct RTP timestamps (and correct RTCP "SR" packets) in this case.


> For now I can fix the camera’s date and time but I can’t take this for 
> granted when the system will be released.

Yes - I'll need to fix the bug in the LIVE555 code.  Stay tuned...

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

_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to