[mythtv-users] Jump ahead problem w/ .19

[Michael T. Dean]

On 02/22/2006 11:42 PM, Cindy Marasco wrote:

>I've recently upgraded to .19 and since the upgrade I'm having
>problems when I try to jump ahead in my recordings.   My recordings
>since the upgrade all show up as being longer than they actually are,
>and  when I am trying to jump and I get errors in my frontend log
>like:
>
>2006-02-23 04:37:27.213 AFD: positionMap[ 67 ] == 22576334.
>2006-02-23 04:37:27.642 AFD: DoFastForward(1909 (1030), do discard frames)
>2006-02-23 04:37:27.643 Dec: DoFastForward(1909 (1030), do discard frames)
>2006-02-23 04:37:27.643 Dec: DoFastForward: Not enough info in positionMap,
>                        we need frame 1909 but highest we have is 1005.
>2006-02-23 04:37:27.643 Resyncing position map. posmapStarted = 0
>livetv(0) watchingRec(0)
>2006-02-23 04:37:27.712 SyncPositionMap prerecorded, from DB: 11 entries
>2006-02-23 04:37:27.712 Dec: DoFastForward: Still not enough info in
>positionMap after sync,
>                        we need frame 1909 but highest we have is
>1005. Will seek frame-by-frame
>
>
>I seem to eventually get to the point I am skipping to, but it takes a
>long time.  I've attached the entire frontend log.
>  
>

Sounds like a corrupt recordedmarkup.  Try:

mysqlcheck -r -umythtv -pmythtv mythconverg

Then, after it fixes the mysql table, you'll need to rebuild the 
seektable for any recordings that have seeking problems using something 
like:

mythcommflag --rebuild -f <filename>

To re-run the commercial flagging, after rebuilding the seektable, run:

mythcommflag -f <filename>

See, also, "mythcommflag --help" for more options.

Mike