Hi, We previously had some issues with receiving raw multicast M2T streams in testOnDemandRTSPServer, that were addressed in a fix in v2024.04.19. However, we are still seeing some similar problems with this.
They're very intermittent so have been quite hard to track down. However, it seems​ to be triggered when a client disconnects without properly terminating the RTSP transaction. If we wait for some time for the reception to be stopped in testOnDemandRTSPServer due to (presumably) a client socket being timed out, when we reattach a client we again get issues where the stream doesn't play correctly. Could there be some difference in the cleanup case between a 'clean' RTSP transaction being completed (the client sending a 'TEARDOWN' message) and the case where the client just disappears? As I say, it's been quite hard to recreate this reliably, so it's difficult to provide much more information than this. We have found that ffplay does seem to just exit without sending the 'TEARDOWN' (it just closes the RTSP connection on exit), which might help in recreating the issue. Thanks as ever Andy
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
