Re: [mythtv-users] noticible interlace on myth-cvs, but not inmyth0.15.1 anyone else?
homepagez at lycos.com
Wed Aug 18 22:08:08 EDT 2004
Well - I seem to be having the same issue with bob.
I'm getting the same major interlace issues and when I run frontend with verbose playback I'm seeing the same error messages as posted here:
Using deinterlace method bobdeint
nVidiaVideoSync: VBlank ioctl did not work, unimplemented in this driver?
DRMVideoSync: Cound not open device /dev/dri/card0, No such file or direction
Using audio as timebase
Video timing method: SGI OpenGL
Why is Bob failing? The other deinterlace methods seem to work ok - but I've read Bob is the "one" to have. Maybe I'm wrong here.
Thanks - any help would be great. Would like to check out "bob"! :)
- 2.6.7 kernel
- P4 2.6G HT
- latest nvidia drivers
- latest Kennedy IVTV drivers
- latest CVS build (as of 8/18/04)
----- Original Message -----
From: Kevin Kuphal <kuphal at dls.net>
Date: Tue, 17 Aug 2004 23:08:34 -0500
To: Discussion about mythtv <mythtv-users at mythtv.org>
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.
> mythtv-users mailing list
> mythtv-users at mythtv.org
Find what you are looking for with the Lycos Yellow Pages
More information about the mythtv-users