[mythtv-users] 0.27.1 stores wrong length in SD mpeg2 recordings

[Stephen Worthington]

On Sun, 22 Jun 2014 03:35:23 +0200, you wrote:

>Hoi Jean-Yves,
>
>Sunday, June 22, 2014, 3:25:34 AM, you wrote:
>
>> On 22 June 2014 11:06, Stephen Worthington <stephen_agent at jsw.gen.nz> wrote:
>
>>> If you get an error at the end of a mythcommflag run (with --rebuild
>>> anyway), you can just ignore it.  The problem happens after all the
>>> valid data has been stored in recordedseek and does not affect
>>> anything.  I do not always get that error, but I have had it fairly
>>> frequently.
>
>> what is puzzling is that mythcommflag should be automatically run
>> after a recording has completed..
>
>> would need to investigate on why this doesn't occur..
>> _______________________________________________
>
>Not by definition. You can set it to start just after the recording
>starts. Which is nice, for it means it's finished soon after the
>recording finishes. But since somehow my seektables get corrupted I
>can not use that anymore. I first have to rebuild them.

If you run mythcommflag without the --rebuild option, then you are
doing the same thing as running it automatically at the time of the
recording.  Without --rebuild, it does rebuild the recordedseek data,
but also adds the commercial flagging data.  So it should cause the
same problems as when it is run at the time of recording.  The only
real difference I can see is that with the recording still running,
mythcommflag is having to wait for its next data all the time, instead
of just reading it continuously from disk.  So maybe there is a
problem with that.  It would be worth trying changing your
mythcommflag settings so that it is only automatically run after the
recording finishes.