Hi Felix, I am doing a similar project. My approach has been exactly as you described it.
The documentation notes that Live555 runs in a single a thread and library calls should not be done from multiple threads, so I have the BasicTaskScheduler running in its own thread and hogging it. Just like you, I will use a condition variable to extract the the newest decoded frame. As an additional point, I am doing the decoding within the Live555 framework by subclassing a MediaSink. This is in an interesting design question. I have a feeling that the expected way to do it though would be to subclass the TaskScheduler per your application needs instead of using the BasicTaskScheduler. Constantin On Thu, May 31, 2012 at 6:24 AM, Felix Radensky <fe...@embedded-sol.com>wrote: > Hi, > > I have to integrate live555 RTSP client into an existing application > that decodes H.264 video and sends it to display. The application > is multithreaded, with separate threads for decoding and display > tasks. > > I was thinking of using testRTSPClient code as a base, putting > it into separate thread, and notifying decoding thread when next > frame is ready. My idea was to use condition variable embedded into > DummySink object and waiting on condvar in another thread. Does that > sound reasonable ? > > Thanks a lot. > > Felix. > > > > > ______________________________**_________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/**mailman/listinfo/live-devel<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
