Repairing the Seektable
(Difference between revisions)
| Line 3: | Line 3: | ||
- Recordings reporting the incorrect length. | - Recordings reporting the incorrect length. | ||
| − | + | mythcommflag and mythtranscode are two of the tools that can be used to rebuild the seektable. | |
| + | |||
| + | [[Image:Important.png]] '''Note:''' After rebuilding the seektable, any cutlist you have created for a recording will no longer be properly synced and should be recreated. | ||
| + | |||
| + | == Preparation== | ||
| + | |||
| + | == Using mythtranscode== | ||
| + | If you have trouble rebuilding a seektable with mythcommflag, try using mythtranscode as follows: | ||
| + | mythtranscode --mpeg2 --showprogress --infile <path-to-file> | ||
| + | (where path-to-file represents a file listed in mythtv recordings) | ||
| + | |||
| + | == Using mythcommflag== | ||
| + | Use the <code>--rebuild</code> option. | ||
| + | |||
| + | == Possible Causes of a Corrupt Seektable== | ||
| + | * Editing a recording outside of the MythTV Frontend. | ||
| + | * Excessive disk IO during recording could prevent invalid SQL updates to the [[Seektable]] (I think). | ||
Revision as of 11:53, 9 January 2008
It is possible to corrupt your seektable for one or more recordings, which can result in: - Being unable to skip forward and backward correctly, and - Recordings reporting the incorrect length.
mythcommflag and mythtranscode are two of the tools that can be used to rebuild the seektable.
Note: After rebuilding the seektable, any cutlist you have created for a recording will no longer be properly synced and should be recreated.
Contents |
Preparation
Using mythtranscode
If you have trouble rebuilding a seektable with mythcommflag, try using mythtranscode as follows:
mythtranscode --mpeg2 --showprogress --infile <path-to-file>
(where path-to-file represents a file listed in mythtv recordings)
Using mythcommflag
Use the --rebuild option.
Possible Causes of a Corrupt Seektable
- Editing a recording outside of the MythTV Frontend.
- Excessive disk IO during recording could prevent invalid SQL updates to the Seektable (I think).
