[mythtv-users] .28

[John Pilkington]

On 02/05/14 13:53, George Nassas wrote:
> On May 2, 2014, at 8:06 AM, Jean-Yves Avenard <jyavenard at gmail.com> wrote:
>
>> Could you go back to the previous version and try again?
>> I'm fairly certain you'll experience exactly the same issue.
>
> I did and no, I don't have the problem with my March build. After each attempt with current head I fall back to the March one because I use editing a lot. I run a few local patches, basically everything I have an outstanding ticket for, so I also thought maybe using a bog standard master build might help but it didn't. I don't remember if I tried stock master + new recording but I doubt it would make any difference.
>
> Initially I figured a straight bisect would be enough but if you're suspecting the seek table I could rerun the bisect with a rebuild for a particular recording after each build. Would a "mythcommflag --rebuild --file" clear and recreate the seek table to your liking? I thought there was a mythutil option that clears it more thoroughly but I'm hazy.
>
> I'm heading into a busy period so I might not be able to do this for a few days or even a week. I'm hoping other people trip over the same problem so I can hang back and watch.
>
> - George

I posted the query about the seektable patch because it seemed possible 
that HP-mini was using it and JYA not.  TTBOMK it would only affect h264 
recordings, and then only if they were being 're-used.'
In that case, experiences of seeking etc performance might differ.

John