<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Here is a situation:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The streamer is a black box that’s connected to audio and
video source. The streamer sends TS with AVC and AAC because the client can
only accept TS. The client knows the exact format of the video and audio streams
inside TS and wants to connect to the live transmission at any time.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The client knows nothing about session establishment protocols
(e.g. RTSP). <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
live-devel-bounces@ns.live555.com [mailto:live-devel-bounces@ns.live555.com] <b>On
Behalf Of </b>Jeremy Noring<br>
<b>Sent:</b> Thursday, September 24, 2009 8:17 PM<br>
<b>To:</b> LIVE555 Streaming Media - development & use<br>
<b>Subject:</b> Re: [Live-devel] H264 multicast streaming question<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>On Thu, Sep 24, 2009 at 12:46 AM, Stas Desyatnlkov <<a
href="mailto:stas@tech-mer.com">stas@tech-mer.com</a>> wrote:<o:p></o:p></p>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Hi,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Its obvious that loss of the SPS or PPS
results in a lot of grief in the h264 land. The question is what choice do we
have in case of no other means of communication besides RTP?</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>What if the h264 stream is packed inside
TS and receiver is not aware of anything else?</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>I guess in case of LAN streaming where
packet loss is rare sending SPS/PPS inband is not that bad of an option would
you agree?</span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=MsoNormal><br>
It depends. If you're doing multicast, then sending it in-stream is a bad
idea; clients may miss the first sending, which means you'd have to do
something weird like insert it when a client connects, or periodically insert
it. If you're doing unicast, it would probably work to send it once
in-stream. In my experience, some clients expect correct sprop-parameter-set
and profile-level-id fields (e.g. quicktime), so not populating them is
possibly a deal-breaker.<br>
<br>
In any event, if you're on a LAN, why would you _ever_ consider not using the
associated RTSP session to communicate this information? And what sort of
scenario do you have where there is "no other means of communication
besides RTP?" Quite frankly, I can't possibly think of a situation
where either of these statements would be true.<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>