As Rune Torgesen explained, multicast packets are routed on the network based on the IP multicast address; the port number is used only once an IP (actually UDP/IP) multicast packet reaches each recipient. So, each stream (or at least each PC) should use a separate multicast address.
Also: > On Jan 18, 2023, at 5:02 AM, g.jaegy <g.ja...@imagine3d.fr> wrote: > > We have a system streaming 54 channels, using a different RTSP server for > each channel, using 18 PCs in total (so about 3 streams per PC). Note that you don’t have to run a separate RTSP server application/process for each stream served by a PC. You can, instead, have a single RTSP server application per PC, each with multiple “ServerMediaSession” objects. This is perhaps a little more efficient than running one RTSP server application per stream, even if your PC is a multiprocessor (because RTSP is usually I/O bound, rather than CPU bound). The only possible benefit of running one RTSP server per stream is that it’s more fault tolerant if a RTSP server should crash (but that’s something that shouldn’t really happen with our code). Finally, if you have a problem/question, there’s usually little value in diving into the arcane details of the LIVE555 code. That’s my job, not yours. Just describe your symptoms; leave the diagnosis for the doctor :-) 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
