Doesn't the watchVariable solution generally require you to setup some
sort of scheduled periodic event scheduleDelayedTask so that the event
loop is guarantied to wake up and check it every so often?
For consuming data from a separate thread I've always preferred skipping
the watch variable a
The card does not have a sockets interface.
OK, in this case I suggest using the "watchVariable" parameter to
"doEventLoop()". Have a separate thread that reads data from your
interface, and then - when sufficient data is available for a frame -
sets the "watchVariable" to some value non-zer
>-Original Message-
>From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
>Sent: Thursday, 10 September 2009 8:38 p.m.
>To: LIVE555 Streaming Media - development & use
>Subject: Re: [Live-devel] Streaming from a d
I'm trying to use mediaServer to stream from a encoder card, but not
sure how handle synchronization between the device source and the
live555 event loop.
First, is the encoder card accessible (readable) as a socket? Those
are the easiest kinds of input devices to handle.
--
Ross Finlayson
L
I'm trying to use mediaServer to stream from a encoder card, but not
sure how handle synchronization between the device source and the
live555 event loop. The device I'm using presents transport stream
packets in its own thread. I've created a subclass of DeviceSource, but
I don't believe I can jus