Hi Ross,
I've successfully implemented the flow described. Thanks
for your
help.
I have and additional, let's say "architecture oriented"
question.
I have a video source (remote IP camera).
I need to implement the next functionality:
1. The remotely installed camera should be connected
only once
(only one stream should be fetched from it).
2. I need to implement on demand recording. (I suppose
to do it
from relayed stream to local network, using openRTSP +
videoStreamer
like client)
3. I also need to have a possibility to access this
(relayed stream
from number of hosts, running Darwin).
Camera -------> relaying module -------------> recording
module (on
demand)
------?-----> Darwin
(on demand?)
------?-----> Darwin
I'd like to simplify "packet duplicator" module,
described in the
forum number of times, and to use "relayed" to local
network stream
for that, using openRTSP+videoStreamer.
(the performance is not an issue, it's just a POC).
My question is: what is the right way to implement the
interaction
with Darwin?
Do I need to use a number of DarwinInjectors to stream
to different
Darwin nodes?
Camera -------> relaying module --------> injector
----------->
Darwin
injector
-----------> Darwin
injector
-----------> Darwin
Are there some different ways using sdp/darwin/relaying
mechanism?
(smth like "sdp=/path_to_movies_dir_of_darwin/stream.sdp"
option in
VLC, is it similar implementation to DarwinInjector)
Is this the right way to use multicast in local network
as a
relaying module, or it's better to use unicast like, in
case of large
number of darwin nodes fetching and relaying the stream?
Thanks a lot.
I really enjoy the LIVE. :)
Vadim
Basically, you are combining RTSP client code (e.g.,
from
"playCommon.cpp") with multicast streaming (server) code
(e.g., from
"testMPEG4VideoStreamer), in a single event loop.
The "RTPSource" objects are created with the RTSP client
code (they
are present after "initiate()" is called on each
"MediaSubsession").
The "PassiveServerMediaSession" and "RTPSink" objects are
created
with the multicast streaming server code.
Once you understand how those two applications work
separately, it
should be clear how to combine them in the way you want.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
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
