Cristiano Belloni wrote:
> [EMAIL PROTECTED] wrote:
>
>> 1. Are you inheriting from FramedSource, from DeviceSource, or
>> modifying DeviceSource?
>>
> Inheriting from FramedSource.
>
>> 2. Is "isAwaitingData()" function an abbreviation for
>> "isCurrentlyAwaitingData()", or are these
[EMAIL PROTECTED] wrote:
> 1. Are you inheriting from FramedSource, from DeviceSource, or
> modifying DeviceSource?
Inheriting from FramedSource.
> 2. Is "isAwaitingData()" function an abbreviation for
> "isCurrentlyAwaitingData()", or are these separate functions?
It's a separate function. Retur
> The problem is, deliverFrame returns the very first frame OK, then
> doGetNextFrame is called again before a new frame is captured, and I
> return immediately. Then, I don't know why, liveMedia never calls
> doGetNextFrame again. It just stays stuck and apparently does nothing.
>
> Why? What
Ross Finlayson wrote:
> If your
> capture device is a socket, then you can easily do this using
> "TaskScheduler::turnOnBackgroundReadHandling()". If, however, your
> capture device is not a socket, then you can instead signal the
> arrival of new data by writing a new event loop (e.g., by su
>The problem is, deliverFrame returns the very first frame OK, then
>doGetNextFrame is called again before a new frame is captured, and I
>return immediately. Then, I don't know why, liveMedia never calls
>doGetNextFrame again. It just stays stuck and apparently does nothing.
>
>Why?
Because you a
