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

Hika van den Hoven hikavdh at gmail.com
Fri Jul 4 20:36:05 UTC 2014


Hoi Hika,

Sunday, June 22, 2014, 8:56:45 PM, you wrote:

> Hoi Jean-Yves,

> Saturday, June 21, 2014, 2:34:10 AM, you wrote:

>> when recording, the backend count the number of frames written to disk
>> and that information is written in the database along the position in
>> bytes for that frame.

>> While I'm getting to is that there are many thing that could cause
>> what you're seeing, and not necessarily a myth one. the first one is
>> that the PVR-500 may not produce the right amount of frames, leading
>> to an incorrect calculation size, and lead to inaccurate skips

> At the start of this thread you wrote the above. If indeed a wrong
> framecount is the cause, then I have a few questions.

> How come a rebuild of the seektables fixes this. Does this use a
> different mechanism?

> How can I check on a recording file if this is indeed the case?

> Could this be fixed with adjustments to the recording profile?


> Tot mails,
>   Hika                            mailto:hikavdh at gmail.com

I asked above questions some days ago and didn't get any answer.
What further confuses me is that the commflagging stays in place after
the rebuild and seem to be accurate only not covering the end of the
recording. To me this last seems to indicate that the framecount is
accurate only incomplete????


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens



More information about the mythtv-users mailing list