<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="">FYI, I have just run a test using the LIVE555 RTSP client library - both with VLC, and our own RTSP client application - against our RTSP server, and have concluded that the problem that you describe does not seem to be a problem with the LIVE555 library.<div class=""><br class=""></div><div class="">It’s possible that the problem lies with VLC’s LIVE555 interface code (“live555.cpp”), but (given that I also tested VLC as a client) it’s much more likely, IMHO, that the problem is with your own RTSP server - in particular, the way in which it implements the RTSP “PAUSE” command.</div><div class=""><br class=""></div><div class="">Based on the RTSP protocol trace that you included in your message, it seems that after your server gets (and responds to) the “PAUSE” command, it does not handle the subsequent “GET_PARAMETER” commands. Instead, these commands get pipelined (somewhere), and your server does not end up handling them until after it receives the subsequent “PLAY” command.</div><div class=""><br class=""></div><div class="">It wasn’t clear from your message whether your stream was RTP-over-UDP, or RTP-over-TCP, but if it was RTP-over-TCP, then I could easily imagine how your server could have a bug that causes it to have problems handling RTSP commands that follow a “PAUSE”. (FYI, when I did my own testing with the LIVE555 RTSP client code to try (unsuccessfully) to reproduce this problem, I tested with both RTP-over-UDP and RTP-over-TCP.)</div><div class=""><br class=""></div><div class="">If you’re still unsure whether the problem is with your own server, then I encourage you to test also against the “LIVE555 Media Server”</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="http://www.live555.com/mediaServer/" class="">http://www.live555.com/mediaServer/</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">TL;DR: Right now, this appears to be most likely a problem with your server, not with VLC (or LIVE555).</div><br class=""><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>
<br class=""></body></html>