[Live-devel] setting rtpTime return by the RTSP PLAY

PROMONET Michel michel.promonet at thalesgroup.com
Wed Feb 27 04:05:40 PST 2013


                Ross,

Perhaps I missed some pieces.
The purpose is to get from the client end the presentation time that was sent by the server.
By now the client presentation time start from gettimeofday and will be synchronized by the first RTSP Sender report.

I try to find a way to have a different initialization of the presentation time (in my case have no relation with the frame timestamp).
What I guess is that the rtpTime in the RTP-Info embedded in the PLAY response could help to reach this aim, but it seems you answer no !

I don't need to use RTP time, what I would like to have is the NTP time that is in RCTP (I always ask myself why this time is not in the RTP header !)

Do you have some suggestions to initialize the presentation time at the client end that is not based on client gettimeofday ?

Best Regards,

                Michel.

[@@ THALES GROUP INTERNAL @@]

De : live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] De la part de Ross Finlayson
Envoyé : mardi 26 février 2013 16:04
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] setting rtpTime return by the RTSP PLAY

I am trying to see how to propagate a timestamp between an RTSP server and a RTSP client.

Your question makes no sense, because the things that get 'propagated' from servers to clients are *presentation times*.  (RTP timestamps are used only internally, by the RTP/RTCP protocol, as a mechanism for conveying presentation times from servers to clients.  Our software automatically converts presentation times to RTP timestamps (at the server end) and RTP timestamps to presentation times (at the client end); application code (server or client) never needs to set or see RTP timestamp values.)

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130227/ed2661c2/attachment.html>


More information about the live-devel mailing list