[mythtv-users] New nVidia 169.07 and interlace changes?

Tom Dexter digitalaudiorock at gmail.com
Fri Dec 21 16:52:30 UTC 2007


On Dec 21, 2007 10:37 AM, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> On 12/21/2007 10:26 AM, Tom Dexter wrote:
> > Speaking of that patch, I'd still love to know why the frontend
> > reports 60Hz output as 30Hz when the output is interlaced....which is
> > what that patch changes.  I posted a question to the dev list about it
> > some time ago and got no response:
> >
> > http://www.gossamer-threads.com/lists/mythtv/dev/302387
> >
>
> 1080i60 is 1920x1080 pixel frames shown at 30 frames per second.  Each
> frame is composed of 2 fields--each having half the number of lines of a
> frame.
>
> 720p60 is 1280x720 pixel frames shown at 60 frames per second.
>
> There is no such thing as 1080i120 or 1080p60 in the ATSC
> specification.  There is, however, 1080p30 and 1080p24, as well as
> 720p30 and 720p24.
>
> http://www.hdtvprimer.com/ISSUES/what_is_ATSC.html
>
> Mike
>

Maybe I'm missing something...you're talking about frame rates
correct?  I was talking about the refresh rate.

The frontend reports a frame rate of 30 for 1080i60, which is correct,
and the patch we were referring to doesn't change that.  However it
also reports a refresh rate of 30 rather than 60.  Isn't supposed to
be 60, as in the 60 fields per second?

In any case, that reported refresh rate causes the frontend to
disallow bob de-interlacing when running at 1080i, which works
perfectly otherwise, and produces the best display of 1080i content I
can get by far.  Seth will concur.

Tom


More information about the mythtv-users mailing list