<!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] DeviceSource.cpp impacts on
sockets</title></head><body>
<blockquote type="cite" cite>I'm adapting live555 to stream from a
live source and using testMPEG2TransportStreamer.cpp and <a
href="http://www.live555.com/liveMedia/faq.html#liveInput"
>http://www.live555.com/liveMedia/faq.html#liveInput</a> as
reference.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I got all necessary code to startup a RTP
server and start playing and put on my source code.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>As explained on the FAQ, i
substitue <i>ByteStreamFileSource
and MPEG2TransportStreamFramer</i><font face="Geneva"> layers by
the</font> DeviceSource<font face="Arial"> one.</font></blockquote>
<div><br></div>
<div>That's correct. However, it's also a good idea to deliver -
to the "RTPSink" object - a sufficiently large chunk of MPEG
Transport Stream data to make efficient use of each outgoing RTP
packet. (Packing just a single 188-byte Transport 'packet' into
each outgoing RTP packet will work, but is inefficient.) To
overcome this, either have your 'DeviceSource' accumulate a reasonable
number (usually 7) of Transport 'packets' before delivering them, or
else insert a "MPEG2TransportStreamAccumulator" object (see,
for example, the source code in "wis-streamer":
http://www.live555.com/wis-streamer/ )</div>
<div><br></div>
<div><br></div>
<blockquote type="cite" cite><font face="Arial">Using DDD to degub a
segmentation fault bug, i found thats is caused by a call to
socketErr() made by writeSocket() ( more precisely, "<b>if
(setsockopt(socket, IPPROTO_IP, IP_MULTICAST_TTL,(const
char*)&ttl, sizeof ttl) < 0)"</b>
line call).</font></blockquote>
<div><br></div>
<div>If this is correct, then it may be caused by a bad 'socket'
parameter (perhaps a socket that has already been closed.
However, I don't see what could be causing this...</div>
<div><br></div>
<div><br></div>
<blockquote type="cite" cite><font face="Arial">How could DeviceSource
changes impact on socket issues??</font></blockquote>
<div><br></div>
<div>Unfortunately I don't see how they could. Sorry.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>