<br><div class="gmail_quote">On Mon, Nov 10, 2008 at 8:22 PM, Johnny Russ <span dir="ltr"><<a href="mailto:jruss@mit.edu">jruss@mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, Nov 10, 2008 at 8:12 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On 11/10/2008 08:03 PM, Al McIntosh wrote:<br>
> The card does not support XVMC, so we can rule that out.<br>
><br>
> I have the following in my frontend output:<br>
><br>
> 2008-11-10 19:15:58.470 TV: Changing from None to WatchingPreRecorded<br>
> Initialize Yadif Deinterlacer. In-Pixformat = 1 Out-Pixformat=1<br>
> yadifdeint: size changed from 0 x 0 -> 720 x 480<br>
<br>
</div>Yadif = chew up CPU<br>
<br>
Set your playback profile group to the default configuration of Slim and<br>
you'll get a more realistic comparison (although chances are MPlayer is<br>
not doing any deinterlacing at all, so really to compare, you'd have to<br>
enable a similar-quality deinterlacer).<br>
<br>
</blockquote></div><br></div>I totally agree if you are only interested in making a comparison with mplayer. However, since your CPU can handle it (you indicated 50% utilization), you may find it is worth the extra CPU cycles to use one of the better deinterlacers. Whether it is worth it or not would depend on your setup and your personal preferences. <br>
</blockquote></div><br><br>I was really just curious as to what the difference was. Deinterlacing did not cross my mind to be the culprit. <br><br>Thanks this has been helpful.<br><br><br><br> <br><br><br> <br>