<div dir="ltr">Yes, but there is no answer why live555 has to close the stream when it can't send it over TCP. Other servers, as I understand, don't do it. And clients can recover from inconsistent data. So, maybe I misunderstood something, but I see no reason for such behaviour. Can you please explain it to me?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">ср, 9 серп. 2023 р. о 10:58 Ross Finlayson <<a href="mailto:finlayson@live555.com">finlayson@live555.com</a>> пише:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
> On Aug 9, 2023, at 5:37 PM, Андрій Олексійович Радченко <<a href="mailto:aoradchenko.fshn22@kubg.edu.ua" target="_blank">aoradchenko.fshn22@kubg.edu.ua</a>> wrote:<br>
> <br>
> Hi. I use live555 to create server and client that stream and get video and audio respectively. I use RTP over TCP due to possible bad network. If use UDP instead of TCP then in some situations can't get I-frames of H264 stream and nothing is decoding, showing etc, I can't afford this in my system. I can afford some lags, gaps and so on but not "nothing". <br>
> If the callback from my MediaSink on the client side is working fast then everything is OK. However if it hangs for example for 1-2 seconds it is possible that some internal socket buffer becomes overwhelmed<br>
<br>
Questions like this arise often.  See:<br>
        <a href="http://lists.live555.com/pipermail/live-devel/2019-December/021441.html" rel="noreferrer" target="_blank">http://lists.live555.com/pipermail/live-devel/2019-December/021441.html</a><br>
        <a href="http://lists.live555.com/pipermail/live-devel/2020-January/021465.html" rel="noreferrer" target="_blank">http://lists.live555.com/pipermail/live-devel/2020-January/021465.html</a><br>
        <a href="http://lists.live555.com/pipermail/live-devel/2020-January/021467.html" rel="noreferrer" target="_blank">http://lists.live555.com/pipermail/live-devel/2020-January/021467.html</a><br>
        <a href="http://lists.live555.com/pipermail/live-devel/2020-July/021673.html" rel="noreferrer" target="_blank">http://lists.live555.com/pipermail/live-devel/2020-July/021673.html</a><br>
        <a href="http://lists.live555.com/pipermail/live-devel/2020-July/021675.html" rel="noreferrer" target="_blank">http://lists.live555.com/pipermail/live-devel/2020-July/021675.html</a><br>
        <a href="http://lists.live555.com/pipermail/live-devel/2020-July/021680.html" rel="noreferrer" target="_blank">http://lists.live555.com/pipermail/live-devel/2020-July/021680.html</a><br>
<br>
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" rel="noreferrer" target="_blank">http://www.live555.com/</a><br>
<br>
<br>
_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" rel="noreferrer" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
</blockquote></div>