Hi,<br>thank you for the tips, it works!!<br>But now I've a second question related to your answer: is there a way (a plugin or some cap) to know when a mpeg4 frame is a keyframe?<br>I've searched without success with gst-inspect.
<br><br>Thank's again.<br><br><div><span class="gmail_quote">2007/6/21, Sjoerd Simons <<a href="mailto:sjoerd@spring.luon.net">sjoerd@spring.luon.net</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, Jun 20, 2007 at 06:57:19PM +0200, Riccardo Corona wrote:<br>> Hi,<br>> I've an mpeg4 live src, I get the mpeg4 packet into a fekesrc and then put<br>> into a gstbuffer and decode&show them.<br>> My problem is this: the images are much more degraded until the new
<br>> keyframe.I know that's the way in which the mpeg4 works (send a keyframe and<br>> then difference and estimation, and so on...) but is there some properties<br>> that would be set to avoid degradeds images between a keyframe and the next
<br>> one?<br><br>What i did when writing a custom demuxer for a mpeg4 livestream was to just<br>drop all packets untill it saw the first keyframe. Which nicely avoids the<br>issue.<br><br> Sjoerd<br>--<br>This is the theory that Jack built.
<br>This is the flaw that lay in the theory that Jack built.<br>This is the palpable verbal haze that hid the flaw that lay in...<br></blockquote></div><br><br clear="all"><br>-- <br>Riccardo Corona