On 6/7/2011 4:48 PM, Ross Finlayson wrote:
I don't know what these "typical fixes for Axis" are, because I don't think anyone on this mailing list has ever mentioned them before,
I'm not sure if it's what the OP meant, but Axis has a very strange idea of what "multicast" means.
Instead of just sending packets out blindly for anyone to receive who wants, letting the switching fabric take care of pruning off network segments where no one wants to listen, Axis makes the first client send an RTSP request to start the stream. Then, instead of some interleaved A/V format, you get audio and video elementaries on different ports.
I guess this allows a client to negotiate certain parameters of the stream, but how is that helpful in a multicast scenario, where presumably you have later clients who will just come along and "listen in" on the stream? If they're expected to know /a priori/ what format the A/V stream is in, why allow the first client to negotiate anything?
Too much brännvin consumption going on there, I think. (http://en.wikipedia.org/wiki/Alcoholic_beverages_in_Sweden) (http://www.axis.com/corporate/contact.htm) _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
