<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.277344); -webkit-composition-fill-color: rgba(175, 192, 227, 0.214844); -webkit-composition-frame-color: rgba(77, 128, 180, 0.214844);"><br></span></div><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.289062); -webkit-composition-fill-color: rgba(175, 192, 227, 0.222656); -webkit-composition-frame-color: rgba(77, 128, 180, 0.222656); ">Bruce</span></div><div><br></div></div><div><br>On Oct 16, 2013, at 6:52, James Board <jpboard2@yahoo.<br></div><blockquote type="cite"><div><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div style="RIGHT: auto">Does my question make sense to anyone?
Or am I doing something very wrong</div>
<div style="RIGHT: auto">with libav and seeking? Has anyone seen this behavior before when you seek to</div>
<div style="RIGHT: auto">position N in a file, but the first few frames that get decoded are lower than N?</div>
<div style="RIGHT: auto">Is there a better way?<br style="RIGHT: auto"></div>
</div></div></blockquote><div><br></div><div>Yes, this is known and basically unavoidable with most codecs. Each frame is dependent on one or more frames that came before. Even if a system made this seem to not happen, from your point of view, it still would be happening in the background. </div><div><br></div><div>I mentioned this problem when discussing multi threading. </div><div><br></div><div>The only workaround is to use intra-frame only compression, so all frames are independent. Some codecs you listed always work that way. </div><div><br></div><div>Bruce</div><div><br></div><br><blockquote type="cite"><div><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div style="BACKGROUND-COLOR: transparent; FONT-STYLE: normal; FONT-FAMILY: times new roman, new york, times, serif; COLOR: rgb(0,0,0); FONT-SIZE: 16px; RIGHT: auto">Does this have anything to do with cached frames, or is that another issue?</div>
<div style="RIGHT: auto"><var id="yui-ie-cursor"></var> </div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Libav-user mailing list</span><br><span><a href="mailto:Libav-user@ffmpeg.org">Libav-user@ffmpeg.org</a></span><br><span><a href="http://ffmpeg.org/mailman/listinfo/libav-user">http://ffmpeg.org/mailman/listinfo/libav-user</a></span><br></div></blockquote></body></html>