<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite">Just wanted to double check: it sounds like a server side upgrade is not necessary for the fix?</blockquote><div><br></div>It shouldn't have been. However, I see from your log that your server code is almost 1 year out of date, so I suggest upgrading it anyway.</div><div><br></div><div><br><blockquote type="cite"> I just tested the new release without upgrading the server and I still get the "response buffer truncated" error message in VLC, although it looks slightly different in that it seems to parse the RTSP 200 OK once the response has been successfully received (around line 2237). <br></blockquote><div><br></div>The actual problem is starting at line 692 of your log. The RTSP client's 'alternative byte handler' (which gets called by the TCP read handling code whenever it thinks that the received data should be part of a RTSP response (rather than an embedded RTP or RTCP packet)) is receiving weird binary (i.e., non-ASCII) data.</div><div><br></div><div>Apparently this weird binary data does not begin with a '$' (i.e., 0x24) character, otherwise our TCP read handling code would have recognized it as beginning an embedded RTP or RTCP packet.</div><div><br></div><div>Does this problem happen *always* whenever you stream from this particular server (in RTP/RTCP-over-TCP mode), or only *sometimes* from this server (e.g., only when the network is congested)?</div><div><br></div><div><br></div><div><blockquote type="cite">Please let me know if you want me to add any logging lines to the live555 code, if that should be of any help in tracking down the issue.<br></blockquote><div><br></div>If the problem still happens - even after you've upgraded your server - then please add the line</div><div>#define DEBUG_RECEIVE 1</div><div>to the start of "liveMedia/RTPInterface.cpp" (for your client), recompile your client, and send us another log (when you see the error happening again).</div><br><br><div apple-content-edited="true">
<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; font-size: medium; "><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; font-size: medium; ">Ross Finlayson<br>Live Networks, Inc.<br><a href="http://www.live555.com/">http://www.live555.com/</a></span></span>
</div>
<br></body></html>