<div dir="ltr">On Thu, Nov 14, 2013 at 4:13 PM, Gabe Rubin <span dir="ltr"><<a href="mailto:gaberubin@gmail.com" target="_blank">gaberubin@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Does this mean recordings affected by this in versions < .27 will be fixed once upgraded to .27 or that seek tables need to be rebuilt?</div>
</blockquote><div><br></div><div>Seektables will need to be rebuilt as needed, using "mythcommflag --rebuild". Pre-0.27 seektables map frame numbers to file offsets for keyframes to enable relatively accurate seeking to a specific frame number, but do nothing to help with accurate position and duration information, nor to help map timecodes to frame numbers for accurate time-based seeking. 0.27 adds a mapping from keyframe frame numbers to timecodes (using linear interpolation for non-keyframes), which is used for accurate seeking and position/duration display.</div>
<div><br></div><div>One caveat is that seeking/position/duration aren't yet working properly for audio-only recordings, since there are essentially no video frames to sync to.</div><div><br></div><div>Jim</div></div></div>
</div>