<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Hi Jeremy:</DIV>
<DIV> </DIV>
<DIV> Thanks for your advice. When i set correct SPS/PPS,then i can streaming H264 file now.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> Thanks<BR>Best Regards<BR><BR>--- <B>09/9/11 (五)，Jeremy Noring <I><kidjan@gmail.com></I></B> 寫道：<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>寄件者: Jeremy Noring <kidjan@gmail.com><BR>主旨: Re: [Live-devel] H264 multicast streaming question<BR>收件者: "LIVE555 Streaming Media - development & use" <live-devel@ns.live555.com><BR>日期: 2009年9月11日,五,上午7:14<BR><BR>
<DIV id=yiv1485562729>2009/9/10 <SPAN dir=ltr><<A href="http://tw.mc723.mail.yahoo.com/mc/compose?to=spopo316@yahoo.com.tw" target=_blank rel=nofollow ymailto="mailto:spopo316@yahoo.com.tw">spopo316@yahoo.com.tw</A>></SPAN><BR>
<DIV class=gmail_quote>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<TABLE cellSpacing=0 cellPadding=0 border=0>
<TBODY>
<TR>
<TD style="FONT-FAMILY: inherit; font-size-adjust: inherit; font-stretch: inherit" vAlign=top><BR><BR>But when I streamed the H.264 file by unicsat method successfully , the sprop-parameter-sets has been set “h264”. Therefore i think the sprop-parameter-sets=h264 does't influence the stream when using multicast method. Is it right?<BR><BR></TD></TR></TBODY></TABLE></BLOCKQUOTE></DIV><BR>No, that's not right. For the decoder to understand your H.264 stream, it is crucial that the SPS/PPS info is communicated over a reliable protocol. If you are not sending in in the sprop-parameter-sets argument, how are you conveying it? Note that sending it in the actual stream is not recommended (see section 8.4 of RFC3984). Some people mistakenly think their Live555/H264 implementation "works," but really they're just conveying SPS/PPS info through the lossy RTP channel, which is strongly discouraged by the RFC:<BR><BR><PRE>The picture and
sequence parameter set NALUs SHOULD NOT be<BR> transmitted in the RTP payload unless reliable transport is provided<BR> for RTP, as a loss of a parameter set of either type will likely<BR> prevent decoding of a considerable portion of the corresponding RTP<BR>
stream. Thus, the transmission of parameter sets using a reliable<BR> session control protocol (i.e., usage of principle A or B above) is<BR> RECOMMENDED.<BR></PRE>Botton line: correctly populate sprop-parameter-sets; you are wasting your time by not doing this.<BR></DIV><BR>-----內含下列夾帶檔案-----<BR><BR>
<DIV class=plainMail>_______________________________________________<BR>live-devel mailing list<BR><A href="http://tw.mc723.mail.yahoo.com/mc/compose?to=live-devel@lists.live555.com" ymailto="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</A><BR><A href="http://lists.live555.com/mailman/listinfo/live-devel" target=_blank>http://lists.live555.com/mailman/listinfo/live-devel</A><BR></DIV></BLOCKQUOTE></td></tr></table><br>___________________________________________________ <br> 您的生活即時通 － 溝通、娛樂、生活、工作一次搞定！ <br> http://messenger.yahoo.com.tw/