<HTML><BODY>
Hi All,<br><br>I had a compatibility issue with rtmpdump 2.3 and fms 3.5/4.0, because of<br>metadata being inserted in the stream via NetStream::send("@setDataFrame", ...,<br>see <a href="http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html"></a><a href="http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html"><a href="http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html">http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html</a></a>.<br><br>As I figured out using wireshark the problem was the absence of "objectEncoding"<br>property in "connect" invocation. Without given property FMS silently closes the socket<br>during initial client-server conversation.<br><br>Here is the small patch, if anybody is interested:<br><br><br>Index: librtmp/rtmp.c<br>===================================================================<br>--- librtmp/rtmp.c&nbsp;&nbsp;&nbsp; (revision 551)<br>+++ librtmp/rtmp.c&nbsp;&nbsp;&nbsp; (w
 orking copy)<br>@@ -258,6 +258,13 @@<br>&nbsp;&nbsp; r-&gt;m_fVideoCodecs = 252.0;<br>&nbsp;&nbsp; r-&gt;Link.timeout = 30;<br>&nbsp;&nbsp; r-&gt;Link.swfAge = 30;<br>+<br>+&nbsp; /* Auriga - Ivanenko. We have to set the encoding("objectEncoding" in connect invocation) to make <br>+&nbsp;&nbsp;&nbsp;&nbsp; rtmpdump fully compatible with FMS 3.5/4.0, see<br>+&nbsp;&nbsp;&nbsp;&nbsp; <a href="http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html"></a><a href="http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html"></a><a href="http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html"></a><a href="http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html"><a href="http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html">http://lists.mplayerhq.hu/pipermail/rtmpdump/2011-February/001302.html</a></a> */<br>+&nbsp; r-&gt;m_fEncoding = 3.0;<br>+&nbsp; r-&gt;m_bSendEncoding = TRUE;<br>+<br>&nbsp;}<br>&nbsp;<br
 >&nbsp;void<br><br></BODY></HTML>