<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><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; ">Ralf,<div><br></div><div>I've now installed a new version (2012.10.18) of the "LIVE555 Streaming Media" code that incorporates (the equivalent of) your proposed fix. Please test it (in your VLC client) to make sure that it works OK for you.</div><div><br></div><div>BTW, I now understand why you saw this situation occur, but I never did. It's because I used "openRTSP" as my client (when testing), and "openRTSP" starts reading from its input source(s) after receiving the "SETUP" response, before sending "PLAY". Because it's the act of reading from an input source that causes the 'read handler' function to get registered (in the "RTPInterface" code), I never encountered your situation.</div><div><br></div><div>You, however, are using VLC for your client, and VLC apparently does not start reading from its input source(s) until sometime after sending the RTSP "PLAY" command. This explains why it could sometimes receive an embedded RTP or RTCP packet before a 'read handler' had been registered.</div><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; ">Ross Finlayson<br>Live Networks, Inc.<br><a href="http://www.live555.com/">http://www.live555.com/</a></span>
</div>
<br></body></html>