I'm starting think that the problem is even more insidious than just RTSP replys don't get recognized by the client. I think the current implementation prevents multiple streams in the same session from being received using RTP over TCP, I think I experienced this the first time I tried it. Does this sound correct?
No, that's not correct. There is no problem having multiple streams (e.g., audio + video) in a single RTP-over-TCP connection. (The data format includes a tag which identifies each sub-stream, and our receiving software handles this OK.)
Is the problem that the RTPSource that is created for the first stream now owns the TCP socket and it has no way to forward data that's not for it on to the other interested parties (other RTPSources and the RTSPClient)?
Basically, yes. -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
