[mythtv-users] run time wrong after upgrade

David Engel david at istwok.net
Tue Sep 18 21:26:18 UTC 2012

On Tue, Sep 18, 2012 at 01:20:54PM -0700, Yeechang Lee wrote:
> David Engel <david at istwok.net> says:
> > Yes, I am looking into probably related issues, but don't expect any
> > real fixes for some time.  It's a tricky issue.  I do have a small
> > change I should probably commit to master.  It's not a fix, but
> > merely lessens the evilness of one problem I've been seeing.
> David, could this issue be the one that caused broken seektable
> displays on a whole bunch of my recordings after upgrading to 0.25?
> They display "2:01:49 of 2:01:49" (the length of the recording) no
> matter the actual position. Seeking and skips do work; the display
> just doesn't get updated. mythtranscode --buildindex doesn't fix the
> issue (otherwise I wouldn't be writing this), and neither does
> mythcommflag --rebuild.

It might be the same or a closely relate issue.  

Basically, the current position and total recording length are
sometimes calculated using completely different methods.  Because of
bad logic, the current position is calculated to be greater than the
recording length.  The values are sanity checked before being
displayed in the OSD and the current position is capped so it isn't
greater than the recording length.  That's why you see "2:01:49 of

The change I have pending sets one of the ways the current position is
calculated back to an older method.  According to Taylor Ralph, the
new method wasn't supposed to be used yet.

David Engel
david at istwok.net

More information about the mythtv-users mailing list