Re: [Live-devel] RTSPClient using the synchronous interface spinning on the processor

2011-06-30 Thread Matt Schuckmannn
Yes it works fine. Thanks, Matt S. On 6/29/2011 11:17 PM, Ross Finlayson wrote: The first time BasicTaskScheduler::SingeStep is called the fReadSet, fWriteSet, and fExceptionSet are all empty and select() returns an error (WSAINVAL) and the code starting on line 86 of BasicTaskScheduler.cpp

Re: [Live-devel] RTSPClient using the synchronous interface spinning on the processor

2011-06-29 Thread Ross Finlayson
The first time BasicTaskScheduler::SingeStep is called the fReadSet, fWriteSet, and fExceptionSet are all empty and select() returns an error (WSAINVAL) and the code starting on line 86 of BasicTaskScheduler.cpp (did I mention I'm on Windows) gets invoked to create a dummySocket so that the err

Re: [Live-devel] RTSPClient using the synchronous interface spinning on the processor

2011-06-29 Thread Matt Schuckmannn
Ok here's what it looks like is happening. I'm initializing the TaskScheduler, the usageEnvironment, and my RTSPClient instance and then calling TaskSchedular::doEvenLoop() without having initiated any RTSP connection (I've been doing that later after the fact via an outside signal). The firs