[mythtvnz] Seek issues on currently-recording file

[Walter Somerville]

Hi all,
I've been using mythtv in Wellington for about a year, thanks to great work
by some of the members of this list. Thanks.
I have a myth-backend server (Athlon X2 5200+) with a Nova T 500, an
HVR-3000, and a PVR150. The first two do DVB-T (for three Freeview|HD
tuners), and the PVR150 is no longer used, due to prime being on freeview.
My frontend is also my primary desktop, and is an Athlon X2 6400+, with an
8400gs doing vdpau, which works fine, in almost all cases. Both machines are
running ubuntu 9.04, but have also used 8.04 and 8.10.
My myth version is currently trunk from avenard.org, but this problem has
been persisting since paul kendall first released his patches.
Also, the nvidia drivers have been various versions over the past year.


My problem is something I've seen referred to on this list once, I think,
and perhaps somewhere else, but no solution ever suggested.
When I am watching a file that is still being recorded (including LiveTV), I
am unable to seek properly in it. This means I can pause playback, but am
unable to catch up. If I try, then while the time changes correctly, the
actual point in the video is wrong, often seeking *back* several minutes.
Likewise, seeking back the default 5s, actually ends up seeking many
minutes. The problem comes when seeking forward, as the frontend thinks it
is current (eg 8:59 of 9:05 etc), so I cannot go further forward, when in
fact I might be half an hour from the end.
If I quit the recording, and re-enter (eg by setting a bookmark), it is able
to seek properly for a small period about where I started, but soon returns
to the previous behaviour. This is annoying, especially on the rare
occasions when I watch LiveTV.
As soon as the recording ends, then it behaves perfectly. This means that if
I watch the news delayed, I need to wait until it is over before I start.

Does anyone have a fix for this?
Or, I am happy to try fix this myself. But I'm not sure where to look. I
assume frontend? Further, perhaps this is linked to various problems people
have had with double-length reported recording times?
It may be worth mentioning that it happens on all dvb-t channels. It didn't
happen on analogue prime. I don't have a satellite dish, so can't comment on
that, but I assume it's a problem with h264 somewhere.

Thanks for any help,

Walter Somerville
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ourshack.com/pipermail/mythtvnz/attachments/20090827/b41361e1/attachment.htm