<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:11.0pt;
font-family:"Calibri","sans-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;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<style type="text/css">"body { font-family:'DejaVu Sans Mono'; font-size:12px"}</style>
</head>
<body lang="EN-US" link="blue" vlink="purple"><div>Well, it's really simple, the av_parser_parse2 method is being called on input buffers, and it will eventually update a variable when sufficient data has been received to identify a complete frame.</div><div>It works like a charm for me, when receiving videos streamed by live555 servers.</div><div><br></div><div>Glad you found out another trick, anyway :)</div><div><br></div><div>Regards,</div><div>Guillaume.</div><div><br></div><div>Le Fri, 13 Jan 2012 19:42:22 +0100, Menne, Neil <nmenne@dcscorp.com> a écrit:<br></div><br><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div class="WordSection1"><p class="MsoNormal"><span style="color:#1F497D">I am in fact talking about the libraries for the underlying parts. In what way was the parser context useful? I’m working on the SPS and PPS stuff, but if that’s useful for anything, it’d be a worthwhile addition.</span></p><p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:#1F497D">-Neil</span></p><p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p><div><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>Guillaume Ferry<br><b>Sent:</b> Thursday, January 12, 2012 2:48 AM<br><b>To:</b> LIVE555 Streaming Media - development & use<br><b>Subject:</b> Re: [Live-devel] "no frame!"</span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><div><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">When you mention ffmpeg, do you mean the application, or the underlying<br>library (libav) ?<br>I had the same problematic few years ago, and I found it can be handled<br>nicely with a reduced amount of code around avcodec_decode_video.<br>I suggest you to have a look on AVCodecParserContext for this matter.<br>If you're still stuck, I can even provide you a code sample.</span></p></div><div><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">Regards,<br>Guillaume.</span></p></div><div><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">Le Wed, 11 Jan 2012 23:53:40 +0100, Menne, Neil <nmenne@dcscorp.com> a écrit:</span></p></div><blockquote style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 6.0pt;margin-left:0in;margin-right:0in;margin-bottom:4.8pt"><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p><p class="MsoNormal">I’m working on my Live555/FFmpeg video player, and I ran into an interesting problem that has kept me stumped for several days. I am taking the buffer that is delivered to my MediaSink (like the example in testRTSPClient), and I am passing the buffer and the size to FFmpeg to decode. It says that there is “no frame!” I’m stumped as to why that is the case when I’m taking the buffer after the “afterGettingFrame” function is called. I was wondering if there was something else that must be done to that buffer for it to be a true frame that can be decoded.</p><p class="MsoNormal"> </p><p class="MsoNormal">My first guess is that the decoder needs more information which brings me to my next question: the SDP description that I’m pulling down doesn’t contain the width/height, so I’m guessing I need to pull that out of the sprop_parameter_sets; is this the case?</p><p class="MsoNormal"> </p><p class="MsoNormal">My second guess is that there is no frame separator; I noticed that in one particular file: H264VideoFileSink they prepend a 0x00000001 along with the sprop_parameters. Is this a potential problem?</p><p class="MsoNormal"> </p><p class="MsoNormal">Video is not my expertise, so I’m spending most days reading anything/everything on these problems, but this one’s got me stuck.</p><p class="MsoNormal"> </p><p class="MsoNormal">-Neil</p><p class="MsoNormal"> </p><p class="MsoNormal">P.S. My video is an H.264 video stream</p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p></blockquote><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br><br></span></p><div id="M2Signature"><div><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">-- </span></p></div><div><div><table class="MsoNormalTable" border="0" cellpadding="0"><tbody><tr><td style="padding:.75pt .75pt .75pt .75pt"><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><img id="_x0000_i1025" src="http://images.bertin.fr/Barettes.png"></span></p></td><td style="padding:.75pt 11.25pt .75pt 11.25pt"><p class="MsoNormal" style="line-height:15.0pt"><span style="font-size:12.0pt;font-family:"Arial","sans-serif"">Guillaume FERRY <br>Ingénieur <br>Traitement de l'Information et du Contenu <br>Tel : 01 39 30 62 09 <br>Fax : 01 39 30 62 45 <br>ferry@bertin.fr <br><a href="http://www.bertin.fr">http://www.bertin.fr</a> </span></p></td><td style="padding:.75pt .75pt .75pt .75pt"><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><img border="0" id="_x0000_i1026" src="http://images.bertin.fr/Bertin.png"></span></p></td></tr></tbody></table><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><a href="http://www.opera.com/mail/"><br><br></a></span></p></div></div></div></div></blockquote><br><br><br><div id="M2Signature"><div>-- </div><div><div><table>
<tbody><tr>
<td>
<img src="http://images.bertin.fr/Barettes.png" style="margin-left:-3px;" moz-do-not-send="true">
</td>
<td style="font-family:arial;vertical-align:middle;padding-left:15px;padding-right:15px;line-height:20px;">
<label id="prenom" style="font-weight:bold;font-size:14px;color:#263F6A;">
Guillaume
</label>
<label id="nom" style="font-weight:bold;font-size:14px;color:#263F6A;">
FERRY
</label>
<br>
<label id="fonction" style="font-size:13px;color:#263F6A;">
Ingénieur
</label>
<br>
<label id="Departement" style="font-size:12px;color:#8996A0;">
Traitement de l'Information et du Contenu
</label>
<br>
<label style="font-size:12px;color:#8996A0;">
Tel :
</label>
<label id="tel" style="font-size:12px;color:#8996A0;">
01 39 30 62 09
</label>
<br>
<label style="font-size:12px;color:#8996A0;">
Fax :
</label>
<label id="fax" style="font-size:12px;color:#8996A0;">
01 39 30 62 45
</label>
<br>
<label id="mail" style="font-size:12px;">
ferry@bertin.fr
</label>
<br>
<label id="lien1" style="font-size:12px;">
<a href="http://www.bertin.fr">http://www.bertin.fr</a>
</label>
<br>
</td>
<td>
<img src="http://images.bertin.fr/Bertin.png" moz-do-not-send="true">
</td>
</tr>
</tbody></table></div></div></div></body></html>