Still can't find the problem. Everything seems to be set correctly and Live555 event loop is running on a separate thread.
Quick debug showed me that everything works perfectly for one session until another client joined concurrent media session. At this point the trigger event handler for first FrameSource stopped being triggered, when triggerEvent() called, instead second FrameSource trigger event handler start being triggered. Could it be a result of using Live555 static libraties? -- Best Regards, Konstantin On 27 Oct 2014, at 22:31, Ross Finlayson <finlay...@live555.com<mailto:finlay...@live555.com>> wrote: I tried your suggestion today and result is the same. I can only stream data to one session at the time. Could it be some pre-processor definition that I am missing? Also some times when I try to play to streams at the same time I get following exception: “RTCPInstance:: RTCPInstance error: totSessionBW parameter should not be zero!” This suggests that, somehow, “fEstimatedKbps” is getting set to zero. You might try running a debugger (such as “gdb”) to test whether that member variable ever gets overwritten. You might have a ‘memory smash’ (e.g., buffer overflow bug) somewhere in your code that’s causing this to happen. Also, you should make sure that you never have more than one thread calling LIVE555 library code (except for the thread that calls “triggerEvent()” - the only LIVE555 function that you may call from a separate thread). Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com<mailto:live-devel@lists.live555.com> http://lists.live555.com/mailman/listinfo/live-devel
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
