<div>I see what you mean about the muxer givving the time stemps ( when it builds the container file)</div>
<div>but , when I test the bitstream that comes out from the x264 encoder ( not muxed ) threw a player</div>
<div>(I use moonlight codec packedge with the media player) It plays with the correct fps , I assume</div>
<div>that it calculates the the time to display each from , by the fps. Is that so? <br><br> </div>
<div><span class="gmail_quote">On 1/12/06, <b class="gmail_sendername">Måns Rullgård</b> <<a href="mailto:mru@inprovide.com">mru@inprovide.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><a href="mailto:shauli.rozen@gmail.com">shauli.rozen@gmail.com</a> said:<br>> I see that i_pts is totally ignored.
<br><br>Not quite. It is passed back to the caller along with the encoded frames.<br><br>> so what field tells the decoder the time to present each frame?<br><br>Timestamps are stored in the container file (think mp4, mpeg-ts).
<br><br>> is the fps written in the sps?<br><br>Yes.<br><br>> and then the decoder just uses fps along with the frame count?<br><br>No. The demuxer should supply timestamps along with each frame.<br><br>--<br>Måns Rullgård
<br><a href="mailto:mru@inprovide.com">mru@inprovide.com</a><br><br>--<br>This is the x264-devel mailing-list<br>To unsubscribe, go to: <a href="http://developers.videolan.org/lists.html">http://developers.videolan.org/lists.html
</a><br><br></blockquote></div><br>