[Live-devel] Behavior of DeviceSource::doGetNextFrame()t, Vol 34, Issue 9

[David Arnold]

>From: Ross Finlayson <finlayson at live555.com>
>Subject: Re: [Live-devel] Behavior of DeviceSource::doGetNextFrame()
>	when no data available
>To: LIVE555 Streaming Media - development & use
>	<live-devel at ns.live555.com>
>Message-ID: <f06230900c10120c29cad@[66.80.62.44]>
>Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>[...]
>Do you have any way to be 'notified' when a new frame is available?
>(E.g., is your frame grabber device a readable socket, or can it set
>global variable when a new frame is available?)  If not, then (from
>your description above), it looks like you'll have to schedule a
>periodic handler function to read frames - using
>"scheduleDelayedTask()".

No, the frame grabber device is not a readable socket.  It's a windoze
interface and only provides a unblocking "GetNextFrame" function.  Since the
interface to the frame grabber we are using provide no mechanism for being
notified when a frame becomes available I am going to assume it is not
possible to use the event-driven approach you mentioned.

Dave Arnold
Future Concepts

The information contained in this electronic mail transmission is intended only for the use of the individual or entity named above and is privileged and confidential. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Any dissemination, distribution or copying of this communication other than to the person or entity named above is strictly prohibited. If you have received this communication in error, please immediately delete it from your system.