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

[Tom Dexter]

On Thu, Nov 14, 2013 at 9: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.
>
> Jim
>

I just finished upgrading from 0.25.3 to 0.27.  Out of curiosity I
just played one of the NBC shows that was behaving this way.  After
the upgrade, the behavior changed in that it actually thinks the
recording is in fact 52 minutes rather than an hour, even if I rebuild
the seektable.

>From what you describe above however, it sounds like this would be
expected and that, if anything, I'll likely see this sort of thing
stop on new NBC recordings.  Is that correct, that the new timecode
data you describe would only be available for new recordings?

By the way...my 0.27 upgrade seems to have gone flawlessly!...very
cool.  May thanks to all the devs!

Tom