<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><blockquote type="cite" class=""> - If vlc does not have access to rtcp/rtp packets, does it default<br class="">back to some other (lame-)scheme of measuring the time, say, the<br class="">arrival time of the packets/frames, etc.?<br class=""></blockquote><br class="">If RTCP is unavailable, I presume live555 falls back to RTP timestamps. </div></blockquote><div><br class=""></div>Yes.</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" class=""> - .. wouldn't it be cool if vlc would, in such a case, inform about<br class="">this behaviour (i.e. by printing "using xxx scheme for timing", etc.)?<br class=""></blockquote><br class="">I don't know how exactly live555 deals with this. But the lack of RTCP should have no bearing on intra-stream buffering.<br class=""></div></blockquote><div><br class=""></div>yes, Rémi is correct here.</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" class=""> - Do I need to specify the rtcp port in the .sdp file, say<br class="">"a=rtcp:50507", or is it calculated automagically as the media rtp<br class="">port + 1 ?<br class=""></blockquote><br class="">It should work either way, but this is really up to live555 implementation.<br class=""></div></blockquote><div><br class=""></div>Right now the LIVE555 library doesn’t recognize the “a=rtcp:” SDP attribute; instead it (if “a=rtcp-mux” is not present) assumes that RTP will use the even port, and RTCP will use the odd port (i.e., even port+1).</div><div><br class=""></div><div>But anyway, as Rémi noted, if you have only a single stream (e.g., video only), then RTCP is pretty much irrelevant to VLC, so focusing on it is a ‘red herring’. Your problem is simply that you have a crappy network. (You may, however, be able to compensate somewhat for this by increasing VLC’s buffering; there’s a configuration option somewhere for this.)</div><br class=""><div apple-content-edited="true" class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Ross Finlayson<br class="">Live Networks, Inc.<br class=""><a href="http://www.live555.com/" class="">http://www.live555.com/</a></span></span>
</div><div class=""><br class="webkit-block-placeholder"></div>
<br class=""></body></html>