Re: [mythtv-users] noticible interlace on myth-cvs, but not inmyth0.15.1 anyone else?

john roberts homepagez at
Wed Aug 18 22:14:27 EDT 2004

Ah - here is something odd.

I've noticed even with Bob not turned on and I'm using something else (Kernel in this example) I'm still getting the DRMVideoSync error:

nVidiaVideoSync: VBlank ioctl did not work, unimplemented in this driver?
DRMVideoSync: Could not open device /dev/dri/card0, No such file or directory

But - the video quality is much better (interlace issues are mostly gone).  (Unlike Bob - which doesn't seem to be doing anything to help).

Any thoughts on the error msg and why Bob isn't doing his job?


----- Original Message -----
From: Kevin Kuphal <kuphal at>
Date: Tue, 17 Aug 2004 23:08:34 -0500
To: Discussion about mythtv <mythtv-users at>
Subject: Re: [mythtv-users] noticible interlace on myth-cvs,	but not inmyth0.15.1 anyone else?

> Hamish Moffatt wrote:
> >On Tue, Aug 17, 2004 at 07:41:10AM -0400, Doug Larrick wrote:
> >  
> >
> >>As far as more interlacing, double-check that your deinterlacer settings 
> >>are proper.  If your output is progressive, try the new 'bob' deinterlacer.
> >>    
> >>
> >
> >Is bob only useful on progressive displays? I'm using it on regular
> >composite out and it seems to make a world of difference. On the other
> >hand I didn't have experimental A/V sync enabled before either.
> >  
> >
> I tried it on my regular TV system and it looked as good as kernel 
> deinterlacing but it made the OSD studder.  Latest CVS as of tonight.
> Kevin
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at

Find what you are looking for with the Lycos Yellow Pages

More information about the mythtv-users mailing list