<div dir="ltr"><div>Dear Mr. Ross Finlayson!</div>
<div>I'm very glad for your detail explanation, but RTP timestamp is really changed.</div>
<div>I print timestamp value into MultiFramedRTPSink::setTimestamp() after call of convertToRTPTimestamp().</div>
<div>Saw that printed value "jumped" once after the second instance of VLC player connected to same RTP stream. <br>Watch of stream into WireShark get me same result.</div>
<div>I use live555 version from 2007 year, distributed by Appro Technology(c) with wis-streamer.</div>
<div>Thank you very much again.</div>
<div> </div>
<div> <br><br></div>
<div class="gmail_quote">On Tue, Nov 9, 2010 at 10:28 AM, Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com">finlayson@live555.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">The conversion from presentation time to RTP timestamp (in the server code), and from RTP timestamp to presentation time (in the client code) happens automatically, and is not something that you should concern yourself with. As a (server or client) developer, you need concern yourself only with presentation times.
<div class="im"><br><br><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">When secondary client connected to same stream I saw "jump" into RTP timestamp in first stream.<br>
</blockquote><br></div>No, that doesn't happen. What can happen, however, is that presentation times - as seen by clients - may change abruptly shortly after a stream starts to be received. This is explained in the FAQ (which you were asked to read before posting to the mailing list :-)
<div class="im"><br><br><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">What is reason for base timestamp use randomaly value and not real time stamp, created by gettimeofday()???<br>
</blockquote><br></div>Because the RTP timestamp field is only 32 bits, which does not - by itself - have enough resolution. Instead, servers and clients use 64-bit "presentation times" (seconds+microseconds), which are aligned with the 'wall clock' time generated by "gettimeofday()".<br>
<br>This is explained in the RTP/RTCP specification (RFC 3550).
<div class="im"><br>-- <br><br>Ross Finlayson<br>Live Networks, Inc.<br><a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a><br></div>_______________________________________________<br>live-devel mailing list
<div class="im"><br><a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br></div>
<div>
<div></div>
<div class="h5"><a href="http://lists.live555.com/mailman/listinfo/live-devel" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br></div></div></blockquote></div><br></div>