<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Live-devel] RTSP server/client
application</title></head><body>
<blockquote type="cite" cite><font face="Arial" size="-1">Is it
possible to use the</font> <a
href="http://www.live555.com/liveMedia/"><font face="Times New Roman"
size="-1">LIVE555 Streaming Media</font></a><font face="Arial"
size="-1"> libraries for the following two
applications:</font></blockquote>
<blockquote type="cite" cite><font face="Arial" size="-1">1) Software
RTSP server / Hardware RTP streamer:</font></blockquote>
<blockquote type="cite" cite><font face="Arial" size="-1">There is a
host handling all RTSP/RTCP related issues like connection setup,
session control, RTP streaming control of dedicated hardware,
.... The hardware can generate multiple streams at high bitrates
and can be controlled by the host with a dedicated interface. So
the RTP stream is directly send by the hardware. The data doesn't
pass at all through the host. Basically the host is the RTSP server
and the RTP server is done in hardware. Can only the RTSP
server part of the library be used without having the real stream
available at the host? And can a dedicated interface to the hardware
be added for setting parameters like (RTP payload type, port number,
IP number, ....)?</font></blockquote>
<blockquote type="cite" cite> </blockquote>
<blockquote type="cite" cite><font face="Arial"
size="-1">2)</font> <font face="Arial" size="-1">Software
RTSP client / Hardware RTP receiver:</font></blockquote>
<blockquote type="cite" cite><font face="Arial" size="-1">Similar as
the server but then the host runs only a RTSP client and the hardware
can receive multiple streams at high bitrates.</font></blockquote>
<div><br></div>
<div>This is probably possible, if you write new subclasses of
"RTPSink" (for the server) and "RTPSource" (for
the client) that encapsulate your hardware on each end.</div>
<div><br></div>
<div>Then, at the server end, you will need to write a new subclass of
"OnDemandServerMediaSubsession" (to redefine the
"createNewRTPSink()" virtual function to create a new
instance of your "RTPSink" subclass).</div>
<div><br></div>
<div>Similarly, at the client end, you will need to modify the
"MediaSession::initiate()" function (unfortunately, you
can't do this by subclassing) to create a new instance of your
"RTPSource" subclass.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>