Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Wondercow

macrumors 6502a
Original poster
Aug 27, 2008
559
365
Toronto, Canada
I'm using a Mac Mini (2010 model, 2.4 GHz, 4 GB) and EyeTV software—with a Silicone Dust HD HomeRun for my PVR—connected to an LG LX9500 LCD TV. My video source is OTA DTV and so far (I've just set it up two days ago) it seems to working fairly well. Now, in the EyeTV preferences there are a few choices for de-interlacing HD programs, topping out with processor-intensive progressive scan. So, my question is this: does it matter if I de-interlace at all (through EyeTV)?

I'm recording from 1080i source, the Mac Mini itself outputs (thanks to Apple's new options) at 1080p, and the TV is locked to progressive thanks to the Mini's output. Is it worth it to take the processor hit for progressive? Is it worth it to even change the setting from "no deinterlacing" considering the source?
 
I'd assume that the quality of the picture that ultimately arrives on your tv screen is only going to be as good as the weakest link in the chain, which sounds like it would be the eyetv software if it is set to "no de-interlace". It may only be minor but I suspect the picture quality will take a hit there and the mini can only output what it's given regardless out what it is actually capable of. Not sure what version of eyetv software you're using but there should be a setting for motion-adaptive which supposedly offers the best trade-off between PQ and processor hit.
 
I think what he wants to know is whether the motion processing within EyeTV will make any difference when you watch it on a TV that also has motion processing. It doesn't make sense to reduce motion blur twice. Has anyone tried this? I am also interested in the results.

I've only seen progressive scan on EyeTV on an Apple Display and it looks to me about the same as the 100Hz correction on LCD TVs.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.