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?
ср, 9 серп. 2023 р. о 10:58 Ross Finlayson <finlay...@live555.com> пише: > > > > On Aug 9, 2023, at 5:37 PM, Андрій Олексійович Радченко < > aoradchenko.fsh...@kubg.edu.ua> wrote: > > > > 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". > > 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 > > Questions like this arise often. See: > > http://lists.live555.com/pipermail/live-devel/2019-December/021441.html > > http://lists.live555.com/pipermail/live-devel/2020-January/021465.html > > http://lists.live555.com/pipermail/live-devel/2020-January/021467.html > > http://lists.live555.com/pipermail/live-devel/2020-July/021673.html > > http://lists.live555.com/pipermail/live-devel/2020-July/021675.html > > http://lists.live555.com/pipermail/live-devel/2020-July/021680.html > > > Ross Finlayson > Live Networks, Inc. > http://www.live555.com/ > > > _______________________________________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/mailman/listinfo/live-devel >
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
