Hmm, for me kernel deint is just rubbish, I don't know how anybody could watch it! News tickers are so jumpy it's hard to track the text moving, and frequently someone can say a word and I not even see their lips move. I don't think this is normal though, can anyone confirm this?
<br><br><div><span class="gmail_quote">On 13/01/07, <b class="gmail_sendername">Daniel Kristjansson</b> <<a href="mailto:danielk@cuymedia.net">danielk@cuymedia.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sat, 2007-01-13 at 12:32 +0000, James Buckley wrote:<br>><br>> TV<br>> Type: LCD<br>> Model: LG 37LP1D<br>> Inputs: DVI (PC), DVI (TV), Componet, HDMI<br>> Working Modelines: 1280x720p, at 50Hz with a little overscan
<br>><br>> People have told me that you can get perfect TV using Kernel<br>> deinterlacing, with a framerate that's as good as standard TV<br>> (and doesn't have any flicker), however for me this method
<br>> just doesn't have enough FPS.<br>><br>> I don't know whether my problems are related to an incorrect<br>> setup (using Gentoo), buggy hardware, or just my incompetence,<br>> but could someone tell me what I *should* get from each of the
<br>> deinterlacing methods, as I've never had anything to compare<br>> too!<br><br>You will never get a perfect picture with a progressive display..<br><br>The Freeview STB is probably not doing any deinterlacing, it
<br>just sends an interlaced frames to the monitor and the monitor<br>does the deinterlacing. And apparently the monitor does a good<br>job.<br><br>So your best option would probably be to feed the monitor a<br>PAL signal without any deinterlacing instead of 1280x720p.
<br>MythTV allows you to use different video modes for the GUI<br>and video playback, so you can get the both of both worlds.<br><br>If you can't feed the monitor a PAL signal for some reason,<br>then bob will give you the closest approximation to the
<br>deinterlacing the LCD is doing. It is however prone to<br>"bobbing" as it's name would indicate. The smaller your<br>video resolution, the more pronounced is the bobbing.<br>The vertical resolution needs to be a multiple of 2 of the
<br>video source vertical resolution for the bobbing to<br>completely disappear. Bob deint also requires the frame<br>rate of the display to be twice that of the source video<br>(true in your case). Flicker also happens with bobdeint
<br>when you have a single pixel high horizontal line, this<br>is because it is only present in every other frame shown.<br>Dimming the lights in the viewing room will make the<br>flicker less pronounced. (It is more pronounced with PAL
<br>than NTSC, which is one reason bob is much more liked here).<br><br>Kernel deint is prone to ghosting, but gives a decent picture<br>with PAL sized frames. It also uses a lot of CPU, but your<br>processor should be able to handle it.
<br><br>Linear blend deint is also prone to ghosting, but not as<br>much as kernel deint. But it also considerably more likely<br>to fail to deinterlace a frame. It only uses a little more<br>CPU than bobdeint.<br><br>oneline deint just throws away half the vertical resolution,
<br>it never fails to deinterlace but it is inappropriate for<br>low resolution material like PAL.<br><br>For your video card I would make sure to disable all the auto<br>vsync in nvidia-settings, and then enable MythTV's OpenGL
<br>vsync method. If this doesn't work, re-enable the vsync in<br>nvidia-settings, and then enable RTC vsync by running this<br>as root:<br> echo 1024 > /proc/sys/dev/rtc/max-user-freq<br><br>Good luck!<br><br>-- Daniel
<br><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div><br>