<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thank you for your patience :)<br>
</p>
<div class="moz-cite-prefix">On 9/6/17 5:33 PM, Ross Finlayson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4DE474B7-F254-4C5D-8648-C13700B8CD6F@live555.com">
<blockquote type="cite">
<pre wrap="">As a side note, this live555 mod was comitted/sent back as "minilive" around 2007/2009 according to my colleagues.
</pre>
</blockquote>
<pre wrap="">
I have no idea what you’re referring to here. What “live555 mod”? And the term “minilive" means nothing to me.
</pre>
</blockquote>
It was a stripped down version of live555 only containing
RTSP/RTCP/RTP. It modified the library code, and someone told me it
was sent upstream, because of LGPL i assume. <br>
<blockquote type="cite"
cite="mid:4DE474B7-F254-4C5D-8648-C13700B8CD6F@live555.com">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">A pastebin with the output from live555ProxyServer if it is interesting: <a class="moz-txt-link-freetext" href="https://pastebin.com/2XXHTpU8">https://pastebin.com/2XXHTpU8</a>
</pre>
</blockquote>
<pre wrap="">
Sorry, but this output shows that:
- You are *not* using the latest version of the “LIVE555 Streaming Media” code (the only version that we support), and
- You have modified the supplied code (to add extra debugging output, at least)
I’m interested only in output from “live555ProxyServer -V” using the latest, unmodified version of the code.</pre>
</blockquote>
<p><a class="moz-txt-link-freetext" href="https://pastebin.com/vJwVGZsg">https://pastebin.com/vJwVGZsg</a></p>
<p>The latest version works the same way as mentioned in the
previous mail.<br>
</p>
<blockquote type="cite"
cite="mid:4DE474B7-F254-4C5D-8648-C13700B8CD6F@live555.com">
<pre wrap="">
Also, you should explain specifically what you mean by “slow setup” of streams. Note that when you play a stream using RTSP, three separate commands are involved:
- DESCRIBE
- SETUP (one for each media track)
- PLAY
Where specifically is the delay (that you’re concerned about) occurring?
</pre>
</blockquote>
<p>It happens after PLAY, when the H264or5VideoRTPSink tries to read
the input frames in doGetNextFrame(). According to the comments it
is looking for a valid NAL frame. I was thinking that maybe the
old proxy had a more naive approach to proxying the data, however
I don't know if that is the case. The old version works almost as
fast as connecting to the video stream directly.<br>
</p>
<blockquote type="cite"
cite="mid:4DE474B7-F254-4C5D-8648-C13700B8CD6F@live555.com">
<pre wrap="">
Ross Finlayson
Live Networks, Inc.
<a class="moz-txt-link-freetext" href="http://www.live555.com/">http://www.live555.com/</a>
_______________________________________________
live-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a>
<a class="moz-txt-link-freetext" href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a>
</pre>
</blockquote>
<p>-Anders<br>
</p>
</body>
</html>