<br><br><div class="gmail_quote">On Mon, Aug 30, 2010 at 10:38 AM, Greg Oliver <span dir="ltr"><<a href="mailto:oliver.greg@gmail.com">oliver.greg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
My *only* gripe about ION thus far is de-interlacing.. If these cards<br>
help, I will definitely slap them into the FEs and stop using the IONs<br>
in them.. Other than that (they will already go into the Revos I have<br>
deployed) - I am unsure of what benefit this device has over the<br>
existing Revos (other than dual core) which seems to be un-needed in<br>
this case..<br>
<br>
Thanks<br>
<br>
-Greg<br></blockquote><div><br></div><div> Hi Greg,</div><div><br></div><div>My understanding about the CrystalHD cards is that they do offer some deinterlacing method (though I'm fairly certain we are not yet using it), but on the upside, you can use any software or OpenGL deinterlacer you like with the return since you can use any renderer you like-- so if you liked, you could do CrystalHD decode, OpenGL display and deinterlace, or CHD decode, VDPAU render and deinterlace, etc. I am not sure that anything will be gained or lost deinterlace-wise with the CrystalHD board, though-- I think that deinterlace is largely a matter of taste so you'll have to see if you like it.</div>
<div><br></div><div>Robert</div></div>