In message <[EMAIL PROTECTED]>
Brad Templeton <[EMAIL PROTECTED]> wrote:
> b) The remote frontend was poor at fast forwarding compared to the local
> frontend. I was not using NFS mount since I have been experiencing
> NFS problems and the Myth protocol streaming generally works fine. FF was
> very jerky. We mostly used 10x, 20x and sometimes 30x speed. I think
> even the most recent CVS has some improvements on this.
I think fast forward has got significantly worse in the last week
or so, even when content is coming from a local drive. It seems to
be much jerkier or something and is very hard to follow the action
and hit play in the right place.
> i) The minor bug that causes the OSD to display the program as much longer
> than it is after it has finished recording during semi-live watching (ie.
> watching a show that is not finished recording) was noticed by the
> partygoers, that's about the only one that was noticed, along with jerky FF
> over ethernet.
That sounds like a reverse version of the DVB bug that I fixed - in
that case the length would jump backwards when the recording finished.
The cause was that the DVB recorder hadn't set the frame rate to 25fps
so it was defaulting to 29.97fps so when the frame count was divided by
the rate to get the time the answer was too small.
It sounds like you might have the opposite problem though - is the
disparity in length equal to 29.97/25 perhaps? Is your global TVFormat
setting NTSC or some version of PAL?
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
