Any updates on the 12 streams limit per client bug? From my own testing, the bug is for both broadcasted and played back streams. Even after the stream has been deleted ( from client side by using ns.close ), and the deleteStreamById() function was called, the stream will still "count" towards the 12 stream limit. So it is not a 12 concurrent stream limit per Client.
When I tried to set the max_streams variable beyond 12 in the RTMPConnection file, it simply crashes the server when I go beyond 12 streams. Any workarounds to this ( other than initiating a new connection every time I want to broadcast a stream which is very ugly ). This feature is really broken and prevents me from using red5 for the kind of voice chat application that I'm working on, back to FMS. _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
