[mythtv-users] Strange time counter issue with recent NBC OTA recordings

Gabe Rubin gaberubin at gmail.com
Fri Nov 15 03:05:19 UTC 2013


On Thu, Nov 14, 2013 at 6:39 PM, Jim Stichnoth <stichnot at gmail.com> wrote:

> On Thu, Nov 14, 2013 at 4:13 PM, Gabe Rubin <gaberubin at gmail.com> wrote:
>
>> 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?
>>
>
> 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.
>
> 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.
>
>
Sounds like, based on the new way of doing things, it is probably best to
just rebuild all seektables.  Should I just go into my recordings directory
and do "mythcommflag --rebuild *"?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20131114/12702966/attachment.html>


More information about the mythtv-users mailing list