doctor at mcc.ac.uk
Tue Jan 17 09:01:29 UTC 2006
On Mon, Jan 16, 2006 at 10:21:53PM +0000, Nick Craig-Wood wrote:
> On Mon, Jan 16, 2006 at 06:53:59PM +0000, Mike Richardson wrote:
> > I'm using the MVP box as a front end to Mythtv. When I use NFS the playback
> > quality if perfect. When I use the myth protocol it becomes jerky and
> > pixelated in places. I get these messages in the mythtv log:
> > MainServer::HandleVersion - Client speaks protocol version 8 but we speak 15!
> I think this error is normal.
Good to know.
> > at the start of the watching session and
> > WriteBlock zerocnt timeout
> Doesn't sound so good though!
No. Curiously it is channel dependent. Recordings from channels such as BBC1
don't suffer from the problem but C4, five, E4, E4+1 all suffer very badly.
> > each time the picture jerks. Is this a mythtv or MVPMC issue? Any
> > suggestions on how I can cure it in 'myth protocol' mode?
> Did you try upping the TCP buffers for the MythTV protocol? (See the
> config screens in MVPMC itself)
Yeah, I upped them to 65K and no difference unfortunately.
> > (The on-screen graphics are quite useful).
> Do you use -r /nfs/path/to/mythtv/recordings or use the filebrowser to
> play the recordings. The former (which I use) gives the program info
> on the screen which is what I presume you mean by the on-screen
> graphics, but plays the files via NFS. Its works well here!
The on-screen graphics I mean are the ones shown whilst fast forwarding and
pausing (percentage through program, program length, recording time, program
details etc). Using the mythtv protocol they are there, using NFS they
aren't - which makes sense.
> BTW You'll probably get a better answer on the mvpmc mailing list!
I'll try there later, if we come to an impasse.
IT Services, University of Manchester
Email: doctor at mcc.ac.uk
*Plain text only please - attachments stripped on arrival*
More information about the mythtv-users